The RGAA is the French government's General Accessibility Reference for Administrations. It is meant to provide a way to check compliance against WCAG 2.0.
Filters
Table of Contents
How to use the RGAA
The RGAA applies to any HTML content (HTML4, XHTML1, HTML5). For some tests, a reference baseline is used. This baseline takes into account a set of assistive technologies, browsers and operating systems, on which the accessibility of JavaScript-based interface components must be tested, among others. A detailed description is provided here: Baseline.
Important notice regarding HTML content prior to HTML5 specification
When the HTML code of the page is not HTML5, the HTML5 elements (tags and attributes) required by a criterion or test, are not applicable. Every other criteria or tests remain applicable, including those related to ARIA attributes, states or properties. The following criteria and tests are not applicable:
criterion 1.10;
criterion 9.2;
test 10.13.3;
test 11.10.1 (condition 2, relative to the HTML5 attribute required).
Validation process
For each criterion, compliance is defined as follows:
Compliant (C): all applicable tests are passed
Non Compliant (NC): at least one applicable test is failed
Not Applicable (NA): there is no content targeted by the criterion.
The RGAA proposes two additional compliance statuses:
Derogated (D): some contents targeted by the criterion will meet compliance by derogation
Not tested (NT): the criterion has not been tested.
Test 1.2.1: Does each decorative image (img tag), without caption and with an alt attribute, meet the following conditions:
The alt attribute has an empty value (alt="")
The decorative image does not have a title attribute
The img tag does not have ARIA role, properties or state, that aims at labeling the image (for example : aria-label, aria-describedby, aria-labelledby).
Test 1.2.2: Does each non clickable area (area tag with no href attribute), not conveying any information, and with an alt attribute, meet the following conditions:
The alt attribute has an empty value (alt="")
The non clickable area does not have a title attribute
The area tag does not have ARIA role, properties or state, that aims at labeling the image (for example : aria-label, aria-describedby, aria-labelledby).
Test 1.2.3: For each image object without caption (object tag with the attribute type="image/"), not conveying any information, meet the following conditions:
The object tag has an attribut aria-hidden="true" ;
The text alternative between object and /object is empty ;
The object tag or one of its children has no title attribute.
The object tag or one of its children do not have ARIA role, properties or state, that aims at labeling the image (for example : aria-label, aria-describedby, aria-labelledby).
Test 1.2.4: Does each decorative vector image (svg tag), not conveying any information, meet the following conditions:
The svg tag has an aria-hidden="true";
The title and desc tags are missing, or empty
The svg tag, or one of its children, has no title attribute
The svg tag, or one of its children, has no ARIA role, property or state, that aims at labeling the vector image (aria-label, aria-describedby, or aria-labelledby, for example).
Test 1.2.5: For each decorative bitmap image (canvas tag), without caption, meet the following conditions:
The canvas tag has an aria-hidden="true";
The text content between canvas and /canvas is empty;
The canvas tag or one of its children has no title attribute;
The canvas tag, or one of its children, has no ARIA role, property or state, that aims at labeling the canvas image (aria-label, aria-describedby, or aria-labelledby, for example).
Test 1.2.6: Does each decorative embedded image (embed tag with attribute type="image/..."), not conveying any information, meet the following conditions:
The embed tag has an aria-hidden="true";
The object tag or one of its children has no title attribute;
The embed tag, or one of its children, has no ARIA role, property or state, that aims at labeling the embed image (aria-label, aria-describedby, or aria-labelledby, for example).
Test 1.3.1: Does each image (img tag), with an alt attribute, conveying information, with an alt attribute, meet the following conditions (except in particular cases)?
The alt attribute has a relevant value
If present, the value of the title attribute matches the value of the alt attribute
If present, the value of the aria-label attribute matches the value of the alt attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the alt attribute.
Test 1.3.2: Does each area (area tag), conveying information, and with an alt attribute, meet the following conditions (except in particular cases)?
The alt attribute has a relevant value
If present, the value of the title attribute matches the value of the alt attribute
If present, the value of the aria-label attribute matches the value of the alt attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the alt attribute;
Test 1.3.3: Does each image button (input tag with the attribute type="image"), and with an alt attribute, meet the following conditions (except in particular cases)?
The alt attribute value is relevant;
If present, the value of the title attribute matches the value of the alt attribute;
If present, the value of the aria-label attribute matches the value of the alt attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the alt attribute;
The image object is immediately followed by an adjacent link giving access to a page or a chunk of text containing a relevant alternative
The user can replace the image object by a relevant text alternative, via a provided mechanism
The user can replace the image object by an image with a relevant alternative, via a provided mechanism
Test 1.3.5: Does each object image (object tag with the attribute type="image/"), conveying information, that uses aria-label, aria-labelledby or title attribute, meet one of the following conditions (except in particular cases)?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute/li>
Test 1.3.6: Does each vector image (svg tag), conveying information, and with an alternative, meet one of the following conditions (except in particular cases)?
The svg tag has a role="img"
The svg tag has an aria-label property with a relevant value, matching the title attribute of the svg tag, if present
The svg tag has a desc tag with a relevant content, equal to the title attribute of the svg tag, if present
An adjacent link gives access to an alternative with relevant content, equal to the title attribute of the svg tag, if present
Test 1.3.7: Does each embedded image (embed tag with the attribute type=\"image/\"), conveying information, that use aria-label, aria-labelledby or title attribute, meet one of the following conditions (except in particular cases)?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute.
Test 1.3.8: Does each vector image (svg tag), conveying information, and with an alternative, meet one of the following conditions (except in particular cases)?
The svg tag has a role=\"img\";
The svg tag has an aria-label property with a relevant value, matching the title attribute of the svg tag, if present;
The svg tag has a desc tag with a relevant content, equal to the aria-label.
Test 1.3.9: For each vector image (svg tag), conveying information, and with an alternative, is this alternative correctly rendered by assistive technologies?
Test 1.3.10: For each bitmap image (canvas tag), conveying information, meet one of the following conditions (except in particular cases)?
The alternative content (content between canvas and /canvas) is relevant;
The bitmap image is immediately followed by an adjacent link giving access to a page or a chunk of text containing a relevant alternative;
The user can replace the bitmap image by a relevant text alternative, via a provided mechanism;
The user can replace the bitmap image by an image with a relevant alternative, via a provided mechanism.
Test 1.3.11: For each bitmap image (canvas tag tag), conveying information, that use aria-label, aria-labelledby or title attribute, meet one of the following conditions (except in particular cases)?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute.
Test 1.3.12: For each bitmap image (canvas tag), conveying information, and with an alternative (content between canvas and /canvas), is this alternative correctly rendered by assistive technologies?
Criterion 1.4 [A] For each image used as CAPTCHA or as
test image, with a text alternative, does this alternative describe the nature and the purpose of the image?
Test 1.4.1: Does each image (img tag) used as a CAPTCHA or test image, with an alt attribute, meet the following conditions:
The content of the alt attribute describes the nature and purpose of the image
If present, the value of the title attribute matches the value of the alt attribute
If present, the value of the aria-label attribute matches the value of the alt attribute;
If present, the content text associate with the aria-labelledby attribute matches the value of the alt attribute.
Test 1.4.2: Does each area (area tag) of an image map used as a CAPTCHA or test image, with an alt attribute, meet the following conditions:
The content of the alt attribute describes the nature and purpose of the image
If present, the value of the title attribute
matches the value of the alt attribute
Test 1.4.3: For each button associated with an image (input tag with the attribute type="image"), used as a CAPTCHA or test image, with an alt attribute, meet the following conditions:
The content of the alt attribute describes the nature and purpose of the image
If present, the value of the title attribute matches the value of the alt attribute
If present, the value of the aria-label attribute matches the value of the alt attribute;
If present, the content text associate with the aria-labelledby attribute matches the value of the alt attribute.
Test 1.4.4: Does each image object (object tag with the attribute type="image/"), conveying information, meet one of the following conditions?
The image object is immediately followed by an adjacent link giving access to a page or a chunk of text describes the nature and purpose of the image;
The user can replace the image object by text alternative, via a provided mechanism, describes the nature and purpose of the image;
The user can replace the image object by an image, via a provided mechanism, describes the nature and purpose of the image.
Test 1.4.5: For each image object (object tag with the attribute type=\"image/\"), used as a CAPTCHA or test image, that use aria-label, aria-labelledby or title attribute, meet one of the following conditions (except in particular cases)?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute.
Test 1.4.6: For each embedded image (embed tag with the attribute type=\"image/\"), used as a CAPTCHA or test image, with a text alternative, meet one of the following conditions?
The image embedded is immediately followed by an adjacent link giving access to a page or a chunk of text describes the nature and purpose of the image;
The user can replace the image embedded by text alternative, via a provided mechanism, describes the nature and purpose of the image;
The user can replace the image embedded by an image, via a provided mechanism, describes the nature and purpose of the image.
Test 1.4.7: For each embedded image (embed tag with the attribute type=\"image/\"), used as a CAPTCHA or test image, that use aria-label, aria-labelledby or title attribute, meet one of the following conditions?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute.
Test 1.4.8: Does each vector image (svg tag), used as a CAPTCHA or test image, with a text alternative, meet the following conditions:
The svg tag has a role=\"img\";
The text alternative provided via the aria-label describes the nature and purpose of the image;
The text alternative provided via the desc tag describes the nature and purpose of the image;
There is adjacent linkthat allows access to an alternative, where the content allows to understand the image nature and operation ,and identical to the aria-label property.
Test 1.4.9: For each vector image (svg tag), used as a CAPTCHA or test image, with a text alternative, is this alternative correctly rendered by assistive technologies?
Test 1.4.10: Does each bitmap image (canvas tag), used as a CAPTCHA or test image, meet the following conditions:
The alternative content (content between canvas and /canvas) describes the nature and purpose of the image;
A content text contain an alternative describes the nature and purpose of the image;
The user can replace the bitmap image by text alternative, via a provided mechanism, describes the nature and purpose of the image;
The user can replace the bitmap image by an image alternative, via a provided mechanism, describes the nature and purpose of the image.
Test 1.4.11: Does each bitmap image (canvas tag), used as a CAPTCHA or test image, that use aria-label, aria-labelledby or title attribute, meet one of the following conditions (except in particular cases)?
If present, the value of the title attribute matches the value of the aria-label attribute;
If present, the value of the text associate with the aria-labelledby attribute matches the value of the title attribute.
Test 1.4.12: For each bitmap image (canvas tag), used as a CAPTCHA or test image, with an alternative (content between ),, is this alternative correctly rendered by assistive technologies?
Criterion 1.5 [A] For each image used as CAPTCHA, is a solution for alternative access to the content or to the purpose of the CAPTCHA available?
Test 1.5.1: Does each image (img, area, object, embed, svg, canvas tags) used as CAPTCHA meet one of the following conditions?
Another non graphic form of CAPTCHA is available, at least;
Another solution to access the functionality protected by the CAPTCHA is available.
Test 1.5.2: Does each button associated with an image (input tag with the attribute type="image") used as CAPTCHA meet one of the following conditions?
Another non graphic form of CAPTCHA is available, at least;
Another solution to access the functionality protected by the CAPTCHA is available.
Test 1.6.3: Does each embedded image (embed tag with an attribute type="image/") conveying information needing a detailed description, meet one of the following conditions?
An aria-describedby attribute containing the reference to a content text acting detailed description.
Test 1.6.5: Does each image button (input tag with the attribute type=\"image\") with a reference to a detailed description provided via an aria-describedby property, meet one of the following conditions?
A content text is identified via an id attribute;
The value of the id attribut is unique;
The value of the aria-describedby attribute matches the value of the id attribute.
Test 1.6.6: Does each vector image (svg tag) conveying information needing a detailed description, meet one of the following conditions?
There is an aria-label property referencing a detailed description adjacent to the vector image;
The title tag contain a detailed description;
There is a desc tag containing a detailed description;
There is an adjacent link (URL or anchor) giving access to the detailed description.
Test 1.6.7: For each vector image (svg tag), with a reference to a detailed description provided via an aria-label property or a desc tag, is this reference correctly rendered by assistive technologies?
Test 1.6.8: Does each bitmap image (canvas tag) conveying information needing a detailed description, meet one of the following conditions?
There is a chunk of text between canvas and /canvas referencing a detailed description adjacent to the bitmap image;
There is a text content between canvas and /canvas serving as a detailed description;
There is an adjacent link (URL or anchor) giving access to the detailed description.
Test 1.6.9: For each bitmap image (canvas tag), with a reference to an adjacent detailed description, is this reference correctly rendered by assistive technologies?
Test 1.6.10: Does each image (img, area, object, embed, svg, canvas tag), with a reference to a detailed description provided via an aria-describedby property, the aria-describedby property does reference the detailed description ?
Test 1.7.2: Does each image button (input tag with the attribute type=\""image/\"") with a detailed description meet the following conditions?
The detailed description in the page and reported in the alt attribute is relevant;
The detailed description available via an adjacent link is relevant;
The content text referenced via the aria-describedby attribute.
Test 1.7.3: Does each image object (object tag with the attribute type="image/") with a detailed description meet the following conditions?
The detailed description adjacent to the embedded image is relevant;
The detailed description available via an adjacent link is relevant.
Test 1.7.4: Does each embedded image (embed tag with the attribute type="image/") with a detailed description meet the following conditions?
The detailed description adjacent to the embedded image is relevant;
The detailed description available via an adjacent link is relevant.
Test 1.7.5: Does each vector image (svg tag) with a detailed description meet the following conditions?
The detailed description adjacent to the vector image available via an aria-label attribut or a desc tag is relevant;
The detailed description adjacent to the vector image is relevant;
The detailed description available via an adjacent link is relevant.
Test 1.7.6 : For each vector image (svg tag) with a detailed description, is this detailed description correctly rendered by assistive technologies?
Test 1.7.7: Does each bitmap image (canvas tag) with a detailed description meet the following conditions?
The detailed description adjacent to the bitmap image is relevant;
The detailed description available between canvas and /canvas is relevant;
The detailed description available via an adjacent link is relevant.
Test 1.7.8 : For each bitmap image (canvas tag) with a detailed description between canvas and /canvas, is this detailed description correctly rendered by assistive technologies?
Test 1.8.2: For each form tag, when an alternate mechanism is missing, each button "image of text" (input tag with the attribute type="image") conveying information must be replaced with styled text, if possible. Has this rule been followed (except in particular cases)?
Test 1.9.2: For each form tag, each button "image of text" (input tag with the attribute type="image") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
Test 1.9.3: Each text image object (object tag with the attribute type="image/") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
Test 1.9.4: Each embedded image of text (embed tag with the attribute type="image/") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
Test 1.9.5: Each bitmap image of text (canvas tag) must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
Criterion 1.10 [A] Is each image caption correctly associated with the corresponding image, if necessary?
Test 1.10.1: Does each image with a caption (img tag or input tag with the attribute type="image", associated with an adjacent caption) meet, if necessary, the following conditions?
The image (img tag) and its caption are contained in a figure tag;
The figure tag has an attribute role="group";
The content of the alt attribute contains a reference to the adjacent caption.
Test 1.10.2: Does each image object with a caption (object tag with the attribute type=\"image/\", associated with an adjacent caption) meet, if necessary, the following conditions?
The image (object tag) and its caption are contained in a figure tag;
The figure tag has an attribute role="group".
Test 1.10.3: Does each embedded image with a caption (embed tag with the attribute type="image/", associated with an adjacent caption) meet, if necessary, the following conditions?
The embedded image (embed tag) and its caption are contained in a figure tag;
The figure tag has an attribute role="group";
The content of the alt attribute contains a reference to the adjacent caption.
Test 1.10.4: Does each vector image with a caption (svg tag associated with an adjacent caption) meet, if necessary, the following conditions?
The vector image (svg tag) and its caption are contained in a figure tag;
The figure tag has an attribute role="group";
The content of the aria-label property or the desc tag of the vector image contains a reference to the adjacent caption;
The value of the title attribute of the vector image (svg tag), if present, is strictly equal to the content of the aria-label property or the desc tag used as an alternative.
Test 1.10.5: Does each bitmap image with a caption (canvas tag associated with an adjacent caption) meet, if necessary, the following conditions?
The bitmap image (canvas tag) and its caption are contained in a figure tag;
The figure tag has an attribute role="group";
The content between canvas and /canvas contains a reference to the adjacent caption.
Do not provide information
through color only, and use sufficient color contrasts.
Criterion 3.1 [A] On each web page, information must not be conveyed only through color. Has this rule been followed?
Test 3.1.1: For each word or for each group of words where color is used to convey information, information must not be conveyed only through color. Has this rule been followed?
Test 3.1.2: For each color indication provided by a text, information must not be conveyed only through color. Has this rule been followed?
Test 3.1.3: For each image conveying information, information must not be conveyed only through color. Has this rule been followed?
Test 3.1.5: For each time-based media conveying information, information must not be conveyed only through color. Has this rule been followed?
Test 3.1.6: For each non-time-based media conveying information, information must not be conveyed only through color. Has this rule been followed?
Criterion 3.2 [A] On each web page, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
Test 3.2.1: For each word or a group of words, whose color conveys information, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
Test 3.2.2: For each information conveyed through color and specified by a word or a group of words, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
Test 3.2.4: For each CSS element background property conveying information, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
Test 3.2.5: For each time-based media conveying information, information
must not be conveyed only through color. Has this rule been implemented in a relevant way?
Test 3.2.6: For each non time-based media conveying information, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
Criterion 3.3 [AA] On each web page, is the contrast between the text and background colors sufficient (except in particular cases)?
Test 3.3.1: On each web page, do non-bold texts and images of non-bold text with font sizes smaller than or equal to 150% of the default font size (or 1.5em) meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 4.5:1
The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
Test 3.3.2: On each web page, do bold texts and images of bold text with font sizes smaller than or equal to 120% of the default font size (or 1.2em) meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 4.5:1
The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
Test 3.3.3: On each web page, do non-bold texts and images of non-bold text with font sizes larger than 150% of the default font size (or 1.5em), meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 3:1
The user can display the text with a contrast ratio of at least 3:1, via a provided mechanism
Test 3.3.4: On each web page, do bold texts and images of bold text with font sizes larger than 120% of the default font size (or 1.2em), meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 3:1
The user can display the text with a contrast ratio of at least 3:1, via a provided mechanism
Test 3.3.5 : Does each mechanism, to display the text with a compliant contrast ratio, has a contrast ratio of at least 4.5:1 ?
Criterion 3.4 [AAA] On each web page, is the contrast between the text and background colors enhanced (except
in particular cases)?
Test 3.4.1: On each web page, do non-bold texts and images of non-bold text with font sizes smaller than or equal to 150% of the default font size (or 1.5em) meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 7:1
The user can display the text with a contrast ratio of at least 7:1, via a provided mechanism
Test 3.4.2: On each web page, do bold texts and images of bold text with font sizes smaller than or equal to 120% of the default font size (or 1.2em) meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 7:1
The user can display the text with a contrast ratio of at least 7:1, via a provided mechanism
Test 3.4.3: On each web page, do non-bold texts and images of non-bold text with font sizes larger than 150% of the default font size (or 1.5em), meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 4.5:1
The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
Test 3.4.4: On each web page, do bold texts and images of bold text with font sizes larger than 120% of the default font size (or 1.2em), meet one of the following conditions (except in particular cases)?
The contrast ratio between text and its background is at least 4.5:1
The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
Test 3.4.5 : Does each mechanism, to display the text with a compliant contrast ratio, has a contrast ratio of at least 7:1 ?
Test 4.3.2: For each prerecorded synchronized time-based media with synchronized captions provided through a track tag, does the track tag have an attribute kind="captions"?
Criterion 4.9 [AAA] Does each prerecorded
time-based media have a sign language interpretation (except
in particular cases) if necessary?
Test 4.9.1: Does each prerecorded audio-only time-based media have a sign language interpretation if necessary, that is adapted to the media language (except in particular cases)?
Test 4.9.2: Does each prerecorded synchronized time-based media have a sign language interpretation, if necessary, that is adapted to the media language (except in particular cases)?
Criterion 4.10 [AAA] For each prerecorded
time-based media with a sign language interpretation is this
interpretation relevant?
Test 4.10.1: For each prerecorded audio-only time-based media with a sign language interpretation, is this interpretation relevant?
Test 4.10.2: For each prerecorded synchronized time-based media with a sign language interpretation, is this interpretation relevant?
Test 4.15.1: For each audio-only, video-only or synchronized time-based media , does the adjacent textual content help to clearly identify the time-based media (except in particular cases)?
Test 4.15.2: For each live audio-only, live video-only or live synchronized time-based media , does the adjacent textual content help to clearly identify the time-based media (except in particular cases)?
The page to which the adjacent link refers is accessible
The alternative in the page to which the adjacent link refers is accessible.
Criterion 4.17 [A] For each non time-based media with an alternative, is this alternative relevant?
Test 4.17.1: For each non time-based media with an alternative, does this alternative provide access to the same content, and to similar functionalities?
Test 4.18.1: Does each audio sequence played automatically via an object, video, audio, embed tag, a JavaScript code or bgsound property meet one of the following conditions?
The audio sequence lasts 3 seconds or less
The audio sequence can be stopped by an action initiated by the user
The volume of the audio sequence can be controlled by the user independently from the system volume control.
Criterion 4.19 [AAA] For each prerecorded audio-only time-based media, are the dialogues audible enough (except in particular cases)?
Test 4.19.1: Does each prerecorded audio time-based media, played via an object, video, audio, embed tag, or provided for download, meet one of the following conditions (except in particular cases)?
The background sounds can be turned off
The volume of the dialogue track(s) is 20 decibels higher than the volume of the background sounds.
An alternative version, for which the background sounds can be turned off, is available
An alternative version in which the volume of the dialogue track(s) is 20 decibels higher than the volume of the background sounds, is available.
Provide each complex data table, with a relevant summary and a title, clearly identify header cells use a relevant mechanism to associate data cells with header cells Ensure that each layout table is correctly linearized.
Test 5.6.2: For each data table (table tag), does each row header have a th tag?
Criterion 5.7 [A] For each table, is each cell associated with its header using the appropriate technique?
Test 5.7.1: Does each header cell (th tag) applied to the whole row or to the whole column have a unique id attribute or a scope attribute?
Test 5.7.2: Does each header cell (th tag) applied to the whole row or the whole column and having a scope attribute meet one of the following conditions?
The header has a scope attribute with the value "row" for row headers
The header has a scope attribute with the value "col" for column headers
Test 5.7.3: Does each header cell (th tag) that is not applied to the whole column meet the following conditions?
The header does not have a scope attribute
The header has a unique id attribute
Test 5.7.4: Does each cell (td or th tag) associated with one or several headers with an id attribute meet the following conditions:
The cell has a headers attribute
The headers attribute contains a list of values matching the id attributes of the headers associated with the cell.
Criterion 5.8 [A] Each layout table must not use elements intended for data tables. Has this rule been followed?
Test 5.8.1: Does each layout table (table tag) meet the following conditions:
The layout table (table tag) does not have any caption, th, thead, tfoot, tfoot tags
The cells of the layout table (td tag) have no scope, headers, colgroup, axis attributes.
Provide explicit link text, in particular, with context information, and use the link title as sparsely as possible. Add links or a
navigation form to the areas of a server-side image map.
Test 7.1.3: Does each script generating or controlling an interface component, having roles, states or properties matching with an ARIA API Design Pattern, meet one of the following conditions?
The interface component complies with theDesign Pattern defined by the ARIA API
An interface component, available in the page, providing access to the same functionalities, complies with theDesign Pattern defined by the ARIA API
The interface component adapts aDesign Pattern defined by the ARIA API
An accessible interface component providing access to the same functionalities is available in the page
Test 7.1.4: Does each change of native role of an HTML element respect the rules and recommendations of the HTML5 specifications, and the associated technical notes?
Test 7.1.5: Does each script generating or controlling an interface component, meet one of the following conditions?
Test 7.2.1: Does each script beginning with the script tag, and having an alternative, meet one of the following conditions?
The alternative between noscript and /noscript provides access to similar content and functionalities
When JavaScript is disabled, the displayed page provides access to similar content and functionalities
The alternative page provides access to similar content and functionalities
The server-side script language provides access to similar content and functionalities
The alternative available in the same page provides access to similar content and functionalities
Test 7.2.2: Does each non text element that is updated by a script (in the page or an iframe) and that has an alternative meet the following conditions:
The alternative of the non text element is updated
Test 7.3.2: script must not remove focus from an element that receives it. Has this rule been followed (except in particular cases)?
Test 7.3.3: Does each interface component implemented via a role defined by the ARIA API, and matching a Design Pattern, meet one of the following conditions?
The keyboard interactions comply with the Design Pattern for the Esc, Space bar, Tab, and arrow keys, at least
An interface component available in the page, performing the same action, has keyboard interactions complying with theDesign Pattern for the Esc, Space bar, Tab, and arrow keys, at least
An alternative providing access to the same functionalities can be controlled by the keyboard and the mouse.
Check that each web page has a valid source code according to the document type, a relevant title and a default human language identification. Check that tags are not used for presentation only, that changes in human language and changes in the direction of reading order are specified.
Criterion 8.1 [A] Is each web page defined by a document type?
Test 8.1.1: For each web page, is the document type (doctype tag) available?
Test 8.1.2: For each web page is the document type (doctype tag) valid?
Test 8.1.3: For each web page with a document type declaration, is this declaration located before the HTML tag in the source code?
Test 8.2.1: For each document type declaration, does the page source code meet the following conditions (except in particular cases)?
Tags follow the writing rules
Tag nesting is conform
Tag opening and closing are conform
Attributes follow the writing rules
The attribute values follow the writing rules
Test 8.2.2: For each document type declaration, the page source code must not contain obsolete elements. Has this rule been followed (except in particular cases)?
Criterion 8.5 [A] Does each web page have a page title?
Test 8.5.1: Does each web page have a page title (title tag)?
Criterion 8.6 [A] For each web page with a page title, is this title relevant?
Test 8.6.1: For each web page with a page title (title tag), is the content of this tag relevant?
Criterion 8.7 [AA] On each web page, is each change in the human language identified via the source code (except in particular cases)?
Test 8.7.1: On each web page, does each text written in a language differing from the default human language meet one of the following
conditions (except in particular cases)?
The human language identification is provided via the element containing the text
The human language identification is provided via one of the parent elements
Criterion 8.8 [AA] On each web page, is each change in human language relevant?
Test8.8.1: On each web page, is each change in human language identification (lang and/or xml:lang attribute) technically valid?
Test 8.8.2: On each web page, is each change in human language identification (lang and/or xml:lang attribute) relevant?
Criterion 8.9 [A] On each web page, tags must not be used only for layout. Has this rule been followed?
Test 8.9.1: On each web page, tags must not be used (except div, span and table) only for layout. Has this rule been followed?
Criterion 8.10 [A] On each web page, are changes in reading direction identified?
Test 8.10.1: On each web page, does each text for which the reading direction is different from the default reading direction is contained in an tag with a dir attribute ?
Test 8.10.2 : On each Web page, does each change reading direction (dir attribute) meet the following conditions:
The value of the dir attribute is valid (rtl or ltr);
Use headings, landmarks, lists, abbreviations and quotes to structure information.
Criterion 9.1 [A] On each web page, is information structured by the appropriate use of headings?
Test 9.1.1: Is there a level 1 heading (h1 tag or a tag with an ARIA role="heading" associated to an aria-level="1" property) on each web page?
Test 9.1.2: On each web page, is the hierarchy between the headings (h1 to h6 tags or tags with an ARIA role="heading" associated to an aria-level property) relevant?
Test 9.1.3: On each web page, when a heading (h1 to h6 tag or a tag with an ARIA role="heading" associated to an aria-level property), is necessary to structure information, is this heading available?
Test 9.1.4: On each web page, is each heading (h1 to h6 tag or a tag with an ARIA role="heading" associated to an aria-level property) relevant?
Use style sheets to control information presentation. Check for the effect of font size increasing on readability. Ensure that links can be correctly identified, that focus is specified, that line spacing is suffiscient, and give the user the ability to control text justification. Ensure that hidden texts are rendered properly and that information is not conveyed only by an element's shape, size or location.
Criterion 10.4 [AA] On each web page, is text still readable when character size is increased until at least 200% (except in particular cases)?
Test 10.4.1: In the style sheets of the website, non relative units (pt, pc, mm, cm, in) must not be used for the media types screen, tv, handheld, projection. Has this rule been followed (except in particular cases)?
Test 10.4.2: In the style sheets of the website, for the media types screen, tv, handheld, projection, do font sizes use relative units only (except in particular cases)?
Test 10.4.3: On each web page, increasing the character size up to 200% must not cause loss of information. Has this rule been followed?
Criterion 10.5 [AA] On each web page, are CSS declarations for background and foreground colors appropriate?
Test 10.5.1: On each web page, for each element that may contain text, is the CSS declaration for foreground color accompanied by a background color declaration at least, inherited from a parent element?
Test 10.5.2: On each web page, for each element that may contain text, is the CSS declaration for background color accompanied by a foreground color declaration at least, inherited from a parent element?
Test 10.5.3: On each web page, for each element that may contain text, if an image is used to provide a background color via CSS, is there a corresponding background color declaration, at least, inherited from a parent element?
Test 10.6.1: On each web page, does each text link indicated through color alone, and whose nature is not obvious, have a contrast ratio of 3:1 or greater with the surrounding text?
Criterion 10.7 [A] On each web page, is the focus visible for each element that receives focus?
Test 10.7.1: For each element receiving focus, the browser default visual cue must not be removed (CSS property outline, outline-color, outline-width, outline-style). Has this rule been followed?
Test 10.7.2: For each element receiving focus, the browser default visual cue must not be degraded (CSS property outline-color). Has this rule been followed?
Test 10.7.3: Does each link inside a text, indicated through color alone, meet the conditions below?
An additional visual cue, other than color, is provided when the user tabs to the link with the keyboard
An additional visual cue, other than color, is provided when the user points to the link (hovers) with the mouse
Criterion 10.8 [AAA] On each web page, can the user specify the background and foreground colors?
Test 10.8.1: For each block of text inside an HTML element, can the background color be specified by the user?
Test 10.8.2: For each block of text inside an HTML element, can the foreground color be specified by the user?
Test 10.8.3: For each block of text inside an object, embed, svg or canvas tag, can the background color be specified by the user?
Test 10.8.4: For each block of text inside an object, embed, svg or canvas tag, can the foreground color be specified by the user?
Criterion 10.9 [AAA] for each web page, text must not be fully justified. Has this rule been followed?
Test 10.9.1: Does each web page meet one of the following conditions?
The text is not fully justified
The user can remove the full justification of text, via a provided mechanism
Criterion 10.10 [AAA] For each web page, on a full-screen window and with a font size of 200%, is each block of text still readable without the use of horizontal scrolling?
Test 10.10.1: On each web page, does increasing the text size up to 200% meet one of the following conditions?
In a full-screen window, the use of horizontal scrolling is not required to read a block of text
The user can display, via a provided mechanism, a version of the content where the use of horizontal scrolling is not required to read a block of text, in a full-screen window
Criterion 10.11 [AAA] For each web page, is the length of lines of text equal to 80 characters or less (except in particular cases)?
Test 10.11.1: For each web page, does each line of text meet one of the following conditions (except in particular cases)?
The length of each line of text is equal to 80 characters or less
The user can reduce the length of each line of text, down to 80 characters or less, when resizing the browser window
Criterion 10.12 [AAA] For each web page, is line and paragraph spacing sufficient?
Test 10.12.1: For each web page, does each block of text meet one of the following conditions?
The line spacing is 1.5 times the text size, or more
The user can increase the line spacing to at least 1.5 times the text size, via a provided mechanism
Test 10.12.2: For each web page, does each block of text meet one of the following conditions?
The spacing between two paragraphs is 1.5 times he line spacing, or more
The user can increase the spacing between two paragraphs to at least 1.5 times the line spacing, via a provided mechanism
Criterion 10.13 [A] For each web page, are hidden texts rendered properly by assistive technologies?
Test 10.13.1: On each web page, does each hidden text meet one of the following conditions?
The text is not intended to be rendered by assistive technologies
The text is made visible on user action on the element itself or on an element before the hidden text
The hidden text is part of a user interface component ruled by the ARIA API, which manages the displayed or hidden status of the content
Test 10.13.2: On each web page, does each hidden text using an ARIA property aria-hidden meet one of the following conditions?
The text is not intended to be rendered by assistive technologies
The value of the ARIA property aria-hidden matches the visible or hidden status of the text
Test 10.13.3: On each web page, does each hidden text using the hidden attribute meet one of the
following conditions?
The text is not intended to be rendered by assistive technologies
The text is made visible on user action on the element itself or on an element before the hidden text
The hidden text is part of a user interface component ruled by the ARIA API, which manages the displayed or hidden status of the content
Test 10.14.1: On each web page, for each text or set of text, information must not be conveyed by shape, size or location alone. Has this rule been followed?
Test 10.14.2: On each web page, for each image or set of images, information must not be conveyed by shape, size or location alone. Has this rule been followed?
Criterion 10.15 [A] On each web page, information must not be conveyed by shape, size or location alone. Has this rule been implemented in a relevant way?
Test 10.15.1: On each web page, for each text or set of text, information must not be conveyed by shape, size or location alone. Has this rule been implemented in a relevant way?
Test 10.15.2: On each web page, for each image or set of images, information must not be conveyed by shape, size or location alone. Has this rule been implemented in a relevant way?
For each form, associate each control with its label, group controls in similar blocks of information, structure selection lists in a consistent way, give each button an explicit label. Check that input help is available, ensure that the input control is accessible and that the user can control financial, legal or personal data.
The value of the for attribute matches the value of the corresponding form field id attribute
Test 11.1.3: Does each form field associated with a label, via the ARIA aria-labelledby property, meet the following conditions?
The label has an id attribute
The value of the id attribute is unique
The value of the ARIA aria-labelledby property matches the value of the label id attribute
Test 11.1.4: Does each form field that uses a property ARIA aria-label or aria-labelledby, if necessary, is accompanied by a visible text passage and attached to the field to understand the nature of the expected input ?
Test 11.1.4: Does each form field that uses a title attribute, meet the following conditions:
The placeholder is missing;
The placeholder matches the value of the title attribute.
Criterion 11.2 [A] Is each label that is associated with a form field relevant?
Test 11.2.1: Does each label (label tag) describe the exact function of the associated form field?
Test 11.2.2: Does each title attribute describe the exact function of the associated form field?
Test 11.2.3: Does each label implemented via the ARIA aria-label property describe the exact function of the associated form field?
Test 11.2.4: Does each label implemented via the ARIA aria-labelledby property describe the exact function of the associated form field?
Criterion 11.3 [AA] On a given page, or
set of pages, all form fields with similar functions must have consistent labels. Has this rule been followed?
Test 11.3.1: On a given page, all form fields with similar functions must have consistent labels. Has this rule been followed?
Test 11.3.2: On a given set of pages, all form fields with similar functions must have consistent labels. Has this rule been followed?
Criterion 11.4 [A] In each form, are each label and its related control positioned next to each other?
Test 11.4.1: In each form, are each label and its related control positioned next to each other?
Criterion 11.6 [A] In each form, does each form field grouping have a legend?
Test 11.6.1: Is each form field grouping have a legend?
Criterion 11.7 [A] In each form, is each legend, related to a form field grouping, relevant?
Test 11.7.1: In each form, is each legend, related to a form field grouping, relevant?
Criterion 11.8 [A] In each form, is each selection list structured in a relevant way?
Test 11.8.1: In each form, are for selection list (select tag) items grouped together with an optgroup tag, if necessary?
Test 11.8.2: In each selection list (select tag), does each list item grouping (optgroup tag) have a label attribute?
Test 11.8.3: For each list item grouping (optgroup tag) with a label attribute, is the content of the label attribute relevant?
Criterion 11.9 [A] In each form, is the text of each button relevant?
Test 11.9.1: In each form, does the text of each button meet the following conditions?
The content of the value attribute of the form buttons of type submit, reset or button is relevant
The content of the button tag is relevant
The content of the title attribute is relevant
The content of the ARIA property aria-label is relevant
A content text is associate with the button via an ARIA property aria-labelledby.
Test 11.9.2: In each form, does the text of each button implemented via an ARIA property aria-labelledby meet the following conditions?
The referenced chunk of text has an id attribute
The value of the id attribute is unique
The value of the ARIA property aria-labelledby matches the value of the id attribute of the chunk of text
The chunk of text is relevant
Criterion 11.10 [A] In each form, is the input control used in a relevant way?
Test 11.10.1: For each form, do mandatory fields indications meet one of the following conditions?
The mandatory field indication is provided via a chunk of text before the form field
The mandatory field indication is provided via a "required" attribute
The mandatory field indication is provided via an aria-required ARIA property
The mandatory field indication is provided via the label of the form field
The mandatory field indication is provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
Test 11.10.2: Each mandatory field indication based on the ARIA properties aria-label, aria-required, or the "required" attribute, must have an explicit visual cue in its label or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
Test 11.10.3: Does each mandatory field indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
The referenced chunk of text has an id attribute
The value of the id attribute is unique
The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute
Test 11.10.4: For each form, do the input errors meet one of the following conditions?
The input error message is provided via the label of the form field
The input error message is provided via a chunk of text before the form field
The form field has a type that automatically generates an input error message
The input error message is provided via a chunk of text tied to the form field via the ARIA property aria-describedby
The input error is signaled via the ARIA property aria-invalid
Test 11.10.5: Each input error indication based on the ARIA properties aria-label or aria-invalid must have an explicit visual cue in the label (label tag) or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
Test 11.10.6: Does each input error indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
The referenced chunk of text has an id attribute
The value of the id attribute is unique
The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute
Test 11.10.7: For each form, does each mandatory field meet one of the following conditions?
The data type and/or format is provided, if necessary, via the field label
The data type and/or format is provided, if necessary, via a chunk of text before the form field
The data type and/or format is provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
Test 11.10.8: Each data type and/or format indication based on the ARIA properties aria-label must have an explicit visual cue in its label or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
Test 11.10.9: Does each data type and/or format indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
The referenced chunk of text has an id attribute
The value of the id attribute is unique
The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute
Test 11.10.10: Does each form field that uses a title attribute as input help, meet the following conditions:
The placeholder is missing;
The placeholder matches the value of the title attribute.
Criterion 11.11 [AA] In each form, is input control accompanied, if necessary, by suggestions helping with the correction of input errors?
Test 11.11.1: For each form, for each input error, are each data types and formats suggested, if necessary?
Test 11.11.2: For each form, for each input error, are examples for expected values suggested, if necessary?
Facilitate navigation in a set of pages through at least two different navigation systems (navigation menu, site map or search engine), breadcrumb trail and the indication of the active page in the navigation menu. Identify groups of important links and the main content area, and provide the ability to avoid them through internal navigation links. Ensure that tabbing order is consistent and that the page does not contain keyboard traps.
Criterion 12.8 [AAA] On each web page, is a breadcrumb trail available (except in particular cases)?
Test 12.8.1: On each web page, is a breadcrumb trail available (except in particular cases)?
Criterion 12.9 [AAA] On each web page, is the breadcrumb trail relevant?
Test 12.9.1: On each web page, does the breadcrumb trail represents the page position in the site structure?
Criterion 12.10 [A] On each web page, are groups of important links (menu, navigation bar) and the main content area identified (except in particular cases)?
Test 12.10.1: On each web page, does the document outline meet the following conditions:
Test 12.13.1: On each web page, is the tabbing order through the content consistent?
Test 12.13.2: For each script that updates or inserts content, does tabbing order remain consistent
Criterion 12.14 [A] On each web page, navigation must not contain keyboard trap. Has this rule been followed?
Test 12.14.1: On each web page, does each element that receives focus meet one of the following conditions?
It is possible to reach the next or previous element that can receive focus with the tab key
The user is informed about the existence of a functional mechanism, allowing to reach the next or previous element that can receive focus with the keyboard
Check that the user can control the refresh processes, sudden changes in luminosity, openings of new windows and moving or blinking content. Specify when a content opens in a new window and provide information regarding viewing of files to download. Do not make the completion of a task rely upon a time limit except if it is essential and ensure that entered data is retrieved after an authenticated session has expired. Ensure that unusual phrases and jargon are made explicit. Provide accessible versions or make downloadable documents accessible.
Criterion 13.1 [A] For each web page, can the user control each time limit that modifies content (except in particular cases)?
The user can increase the time limit between two refresh processes by at least a factor of ten
The user is warned about the imminence of the refresh, and has at least 20 seconds to increase the time limit before the next refresh
The time limit between two refresh processes is at least twenty hours
Test 13.1.2: For each web page, is each redirection initiated via the meta tag immediate (except in particular cases)?
Test 13.1.3: For each web page, does each redirect process initiated via a script meet one of the following conditions (except in particular cases)?
The user can stop or restart the redirect
The user can increase the time limit to at least ten times before redirection
The user is warned about the imminence of the redirection and has at least twenty seconds to increase the time limit before the next redirection
The time limit before the redirection is at least twenty hours
Test 13.1.4: For each web page, does each server-side redirect process meet one of the following conditions (except in particular cases)?
The user can stop or restart the redirection
The user can increase the time limit before the redirection to at least ten times
The user is warned about the imminence of the redirection and has at least twenty seconds to increase the time limit before the next redirection
Time limit before redirection is at least twenty hours
Test 13.1.5: For each web page, does each process restricting a session time meet one of the following conditions (except in particular cases)?
The user can suppress time limit
The user can increase time limit
Time limit before the session expires is at least twenty hours.
Criterion 13.2 [A] On each web page, is the user warned each time a new window opens?
Test 13.2.1: On each web page, for each new window opening launched via a link (target="_blank"attribute) or a JavaScript command, is the user warned?
Test 13.2.2: On each web page, for each window opening launched via an object, applet or embed tag, is the user warned?
Test 13.2.3: On each web page, for each window opening launched via a form control, is the user warned?
Criterion 13.3 [A] On each web page, the opening of a new window must not happen without user action. Has this rule been followed?
Test 13.3.1: On each web page, the opening of a new window must not be launched without user action. Has this rule been followed?
Criterion 13.4 [AAA] On each web page, a task must not require a time limit to be completed, except if it occurs in real time or if this time limit is essential. Has this rule been followed?
Test 13.4.1: On each web page, does each task with a time limit meet one of the following conditions?
The task occurs in real time
The task requires a time limit that is essential for the task to occur successfully
Criterion 13.5 [AAA] On each web page, when an authenticated session is interrupted, is the data entered by the user retrieved after re-authenticating?
Test 13.5.1: On each web page, when an authenticated session is interrupted, is the data entered by the user retrieved after re-authenticating?
Criterion 13.6 [A] On each web page, for each file that can be downloaded, is there sufficient information provided (except in particular cases)?
Test 13.6.1: On each web page, does each file that can be downloaded via a link or a form have information about its format (except in particular cases)?
Test 13.6.2: On each web page, does each file that can be downloaded via a link or a form have information about its weight (except in particular cases)?
Test 13.6.3: On each web page, does each file that can be downloaded via a link or a form have information about its human language if necessary (except in particular cases)?
Criterion 13.7 [A] On each web page, does each electronic document that can be downloaded have an accessible version if necessary?
Test 13.7.1: On each web page, does each downloading functionality for an electronic document meet one of the following conditions.
Criterion 13.8 [A] For each electronic document with an accessible version, does this version provide the same information?
Test 13.8.1: Does each electronic document with an accessible version meet one of the following conditions?
The accessibility-supported version provides the same information
The alternative version in HTML format is relevant and provides the same information
Criterion 13.9 [AAA] On each web page, are unusual phrases, idioms or jargon made explicit?
Test 13.9.1: On each web page, does each phrase used in an unusual or restricted way, each idiom or jargon meet one of the following conditions?
A definition is available in the context right next to the phrase and is specified by the dfn tag
A definition is available via a definition list
A definition is available in the page
The phrase is contained in a link giving to access to the definition.
Criterion 13.10 [AAA] On each web page, for each phrase used in an unusual or restricted way, each idiom or jargon with a definition, is this definition relevant?
Test 13.10.1: On each web page, for each phrase used in an unusual or restricted way, idiom or jargon with a definition, does this definition meet one of the following conditions?
The content of the associated definition is relevant
The content of the dd tag of the definition list is relevant
The definition provided by the adjacent context is relevant.
Criterion 13.11 [A] On each web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) have an alternative?
Test 13.11.1: On each web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) meet one of the following conditions?
A title attribute is available
A definition is provided by the adjacent context
Criterion 13.12 [A] On each web page, for each cryptical content (ASCII art, emoticon, cryptical syntax) with an alternative, is this alternative relevant?
Test 13.12.1: On each web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) meet one of the following conditions?
The content of the title attribute is relevant
The definition provided by the adjacent context is relevant
Criterion 13.13 [AAA] On each web page, for each word whose meaning cannot be understood without knowing the pronunciation, is this pronunciation specified?
Test 13.13.1: On each web page, does each word whose meaning cannot be understood without knowing the pronunciation, meet one of the following conditions?
The phonetic pronunciation is available in the adjacent context
The phonetic pronunciation is accessible via a link
Criterion 13.14 [AAA] On each web page, does each text that requires a reading ability more advanced than the lower secondary education level have an alternative version?
Test 13.14.1: On each web page, does each text that requires a reading ability more advanced than the lower secondary education level (except for proper names and title) meet one of the following conditions?
An illustration or graphic symbols adapted to the reading level of the lower secondary education level are available
A version in sign language (adapted to the human language of the content) is available
A spoken version of the text is available
A summary adapted to the reading level of the lower secondary education level is available.
Test 13.15.1: On each web page, does each image (img tag, svg tag, or object tag) causing a suddent change in luminosity or a flashing effect meet one of the following conditions?
The effect's frequency is lower than 3 per second
The cumulated area of effects is smaller than or equal to 21,824 pixels
Test 13.15.2: On each web page, does each script causing a sudden change in luminosity or a flashing effect meet one of the following conditions?
The effect's frequency is lower than 3 per second
The cumulated area of the effects is less than or equal to 21,824 pixels
Test 13.15.3: On each web page, does each CSS layout causing a sudden change in luminosity or a flashing effect meet one of the following conditions?
The effect's frequency is lower than 3 per second
The cumulated area of the effects is less than or equal to 21,824 pixels
Test 13.15.4: On each web page, does each Java applet causing a sudden change in luminosity or a flashing effect meet one of the following conditions?
The effect's frequency is lower than 3 per second
The cumulated area of the effects is less than or equal to 21,824 pixels
Test 13.16.1: On each web page, does each sudden change in luminosity or a flashing effect caused by an image (img tag, svg tag, embed tag, canvas tag, or object tag) have a frequency lower than or equal to 3 per second?
Test 13.16.2: On each web page, does each sudden change in luminosity or a flashing effect caused by a script have a frequency lower than or equal to 3 per second?
Test 13.16.3: On each web page, does each sudden change in luminosity or a flashing effect caused by CSS layout have a frequency lower than or equal to 3 per second?
Criterion 13.17 [A] On each web page, can each moving or blinking content be controlled by the user?
Test 13.17.1: On each web page, does each moving content that starts moving automatically, meet one of the following conditions?
The motion stops within 5 seconds
The user can stop and restart the motion
The user can display or hide the moving content
The user can display the same information without moving content.
Test 13.17.2: On each web page, does each blinking content that starts blinking automatically, meet one of the following conditions?
The blinking stops within 5 seconds
The user can stop and restart the blinking
The user can display and hide the blinking content
The user can display the whole information without blinking content.
RGAA