Criteria for simplified control

1. Find in the document the images implemented using an <img> element or an element with the WAI-ARIA role="img" attribute.
2. For each image, determine whether the image conveys information.
3. If it is an <img> element, check that the image has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute;
   • value of the alt attribute;
   • value of the title attribute.
4. In the case of an element with the WAI-ARIA role="img" attribute, check that the image has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute.
5. If at least one text alternative is found, the test is validated.

1. Find in the document the <area> elements.
2. For each <area> element, determine whether the image map area carries information.
3. Check that the image map area has at least one of the following text alternatives:
   • value of the WAI-ARIA aria-label attribute;
   • value of the alt attribute;
4. If at least one text alternative is found, the test is validated.

1. Find in the document the <input> elements with the type="image" attribute.
2. For each <input> element with the attribute type="image", determine whether the image used conveys information.
3. Check that the <input> element has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute;
   • value of the alt attribute;
   • value of the title attribute.
4. If at least one text alternative is found, the test is validated.

1. Find in the document the <img> elements with the ismap attribute.
2. For each <img> element with the ismap attribute, check for the presence of a link or set of links (or another type of user interface component which plays a similar role, such as a combobox, for example) providing access to the same resources as when the image is clicked.
3. If this is the case, the test is validated.

1. Find in the document the <svg> elements.
2. For each <svg> element, determine whether the image conveys information.
3. Check that the <svg> element has a WAI-ARIA role="img" attribute.
4. If this is not the case, the test is invalidated.
5. If necessary, check that the <svg> element has at least one of the following text alternatives:
   • value of the <title> element;
   • passage of text linked by the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute;
6. If at least one text alternative is found, the test is validated.

1. Find in the document the opening <object> tags with the type="image/..." attribute.
2. For each opening <object> tag with the type="image/..." attribute, determine whether the image used is conveying information.
3. Check that the <object> element has a WAI-ARIA role="img" attribute.
4. Check that the <object> element has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute;
   • value of the title attribute.
5. If at least one text alternative is found, the test is validated.
6. Otherwise, check that:
   • either the <object> element is immediately followed by an adjacent link or button providing access to alternative content;
   • or a mechanism allows the user to replace the <object> element with alternative content.
7. If this is the case, the test is validated.

1. For each <embed> element with the type="image/..." attribute, determine whether the image used is conveying information.
2. Check that the <embed> element has a WAI-ARIA role="img" attribute.
3. Check that the <embed> element has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute;
   • value of the title attribute.
4. If at least one text alternative is found, the test is validated.
5. Otherwise, check that:
   • either the <object> element is immediately followed by an adjacent link or button providing access to alternative content;
   • or a mechanism allows the user to replace the <object> element with alternative content.
6. If this is the case, the test is validated.

1. Find <canvas> elements in the document.
2. For each <canvas> element, determine whether the image used conveys information.
3. Check that the <canvas> element has a WAI-ARIA role="img" attribute.
4. Check that the opening <canvas> tag has at least one of the following text alternatives:
   • passage of text associated via the WAI-ARIA aria-labelledby attribute;
   • value of the WAI-ARIA aria-label attribute.
5. If at least one text alternative is found, the test is validated.
6. If steps 3 and 4 are not satisfied, check that:
   • either the <canvas> element has alternative content between the <canvas> and </canvas> tags;
   • or the <canvas> element is immediately followed by an adjacent link or button providing access to alternative content;
   • or a mechanism allows the user to replace the <canvas> element with alternative content.
7. If this is the case, the test is validated.

Note: if the <canvas> element has an img role, its alternative can only be provided by the techniques listed in step 4.

1. Find in the document the decorative images without a legend implemented using an <img> element.
2. For each image, check that the image has no aria-labelledby, aria-label or title attributes and that it has
   • an empty alt attribute (alt="");
   • or a WAI-ARIA aria-hidden="true" or role="presentation" attribute.
3. If this is the case for each image, the test is validated.

1. Find in the document the decorative images implemented using an <area> element (without a href attribute).
2. For each image, check that the <area> element has no aria-labelledby, aria-label or title attributes and that it has
   • an empty alt attribute (alt="");
   • or a WAI-ARIA aria-hidden="true" or role="presentation" attribute.
3. If this is the case for each image, the test is validated.

1. Find in the document the decorative images implemented without an image caption using an <object> element (with a type="image/..." attribute).
2. For each image, check that the opening <object> tag does not have aria-labelledby, aria-label or title attributes and that it
   • has a WAI-ARIA aria-hidden="true" attribute;
   • and has no text alternative;
   • and has no alternative content between the <object> and </object> tags.
3. If this is the case for each image, the test is validated.

1. Find in the document the decorative images without an image caption, implemented using a <svg> element.
2. For each image, check that the <svg> element has no aria-labelledby or aria-label attributes and that it
   • has a WAI-ARIA aria-hidden="true" attribute;
   • and has no text alternative (including its child elements);
   • and does not contain <title> and <desc> elements unless empty of content;
   • and has no title attribute (and its child elements).
3. If this is the case for each image, the test is validated.

1. Find in the document the decorative images without an image caption implemented using a <canvas> element.
2. For each image, check that the <canvas> element has no aria-labelledby, aria-label or title attributes and that it
   • has a WAI-ARIA aria-hidden="true" attribute;
   • and has no text alternative;
   • and has no alternative content between the <canvas> and </canvas> tags.
3. If this is the case for each image, the test is validated.

1. Find in the document the decorative images without an image caption using an <embed> element (with a type="image/..." attribute).
2. For each image, check that the <embed> element does not have aria-labelledby, aria-label or title attributes and that it
   • has a WAI-ARIA aria-hidden="true" attribute;
   • and has no text alternative;
3. If this is the case for each image, the test is validated.

1. Find in the document the images implemented using an <img> element (or an element with the WAI-ARIA role="img" attribute) with a text alternative (image).
2. For each image, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <area> elements with a text alternative.
2. For each <area> element, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <input> elements with the type="image" attribute and a text alternative (image).
2. For each <input> element with the type="image" attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <object> elements with the type="image/..." attribute and a text alternative.
2. For each <object> element with the type="image/..." attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <embed> elements with the type="image/..." attribute and a text alternative.
2. For each <embed> element with the type="image/..." attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <svg> elements with a text alternative.
2. For each <svg> element, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <canvas> elements that have an alternative text.
2. For each <canvas> element, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <canvas> elements with alternative content between the <canvas> and </canvas> tags.
2. For each <canvas> element, check that the alternative content is correctly rendered (by assistive technologies).
3. If this is the case for each image, the test is validated.

1. Find in the document the images with a text alternative.
2. For each image, check that the text alternative is short and concise.
3. If this is the case for each image, the test is validated.

1. Find in the document the images that are implemented by means of an <img> element with a text alternative and used as a CAPTCHA or as a test image.
2. For each image, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <area> elements with a text alternative and used as a CAPTCHA or as a test image.
2. For each <area> element, check that the alternative text is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <input> elements with the type="image" attribute and a text alternative, and used as a CAPTCHA or as a test image.
2. For each <input> element with the type="image" attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <object> elements with the type="image/..." attribute and a text alternative, and used as a CAPTCHA or as a test image.
2. For each <object> element with the type="image/..." attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <embed> elements with the type="image/..." attribute and a text alternative, and used as a CAPTCHA or as a test image.
2. For each <embed> element with the type="image/..." attribute, check that the text alternative is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <svg> elements with a text alternative and used as a CAPTCHA or as a test image.
2. For each <svg> element, check that the alternative text is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <canvas> elements with a text alternative and used as a CAPTCHA or as a test image.
2. For each <canvas> element, check that the alternative text is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the images (<img>, <area>, <object>, <embed>, <svg>, <canvas> elements or elements with a WAI-ARIA role="img" attribute) used as CAPTCHA or test image.
2. For each image, check that there is
   • either another form of non-graphical CAPTCHA, at least;
   • or another solution for accessing the functionality that is secured by the CAPTCHA.
3. If this is the case for each image, the test is validated.

1. Find in the document the buttons associated with an image (<input> elements with the type="image" attribute) used as a CAPTCHA or as a test image.
2. For each button associated with an image, check that there is
   • either another form of non-graphical CAPTCHA, at least;
   • or another solution for accessing the functionality that is secured by the CAPTCHA.
3. If this is the case for each image, the test is validated.

1. Find in the document the images that are implemented using an <img> element (or an element with the WAI-ARIA role="img" attribute) and conveying information that requires a detailed description.
2. For each image, check that there is
   • Either a text alternative containing a reference to a detailed description adjacent to the image;
   • Or a link or adjacent button giving access to the detailed description.
3. If this is the case for each image, the test is validated.

1. Find in the document the <object> elements with the type="image/..." attribute, which contain information requiring a detailed description.
2. For each <object> element with the type="image/..." attribute, check that there is
   • either a text alternative containing a reference to a detailed description adjacent to the image;
   • or an adjacent link or button giving access to the detailed description.
3. If this is the case for each <object> element with the type="image/..." attribute, the test is validated.

1. Find in the document the <embed> elements with the type="image/..." attribute, which contain information requiring a detailed description.
2. For each <embed> element with the type="image/..." attribute, check that there is
   • either a text alternative containing a reference to a detailed description adjacent to the image;
   • or an adjacent link or button giving access to the detailed description.
3. If this is the case for each <embed> element with the type="image/..." attribute, the test is validated.

1. Find in the document the <input> elements with the type="image" attribute, which contain information requiring a detailed description.
2. For each <input> element with the type="image" attribute, check that there is
   • either a text alternative containing a reference to a detailed description adjacent to the image;
   • a link or adjacent button giving access to the detailed description;
   • or a WAI-ARIA attribute aria-describedby associating a passage of text acting as a detailed description.
3. If this is the case for each <input> element with the type="image" attribute, the test is validated.

1. Find in the document the <svg> elements conveying information that require a detailed description.
2. For each <svg> element, check that there is
   • either a WAI-ARIA aria-label attribute containing the text alternative and a reference to an adjacent detailed description;
   • or a WAI-ARIA aria-labelledby attribute associating a passage of text acting as a text alternative and another acting as a detailed description;
   • or a WAI-ARIA aria-describedby attribute associating a passage of text acting as a detailed description;
   • or a link or an adjacent button giving access to the detailed description.
3. If this is the case for each <svg> element, the test is validated.

1. Find in the document the <svg> elements conveying information for which a detailed description is provided using an aria-label, aria-labelledby or aria-describedby attribute.
2. For each <svg> element, check that the content of the detailed description is correctly rendered (by assistive technologies).
3. If this is the case for each <svg> element, the test is validated.

1. Find in the document the <canvas> elements conveying information that require a detailed description.
2. For each <canvas> element, check that there is
   • either a WAI-ARIA aria-label attribute containing the text alternative and a reference to an adjacent detailed description;
   • or a WAI-ARIA aria-labelledby attribute associating a passage of text acting as a text alternative and another acting as a detailed description;
   • or a text content between <canvas> and </canvas> referring to a detailed description adjacent to the bitmap image;
   • or a text content between <canvas> and </canvas> acting as a detailed description;
   • or an adjacent link or button giving access to the detailed description.
3. If this is the case for each <canvas> element, the test is validated.

1. Find in the document the <canvas> elements conveying information whose detailed description is provided by means of an aria-label, aria-labelledby or aria-describedby attribute.
2. For each <canvas> element, check that the content of the detailed description is correctly rendered (by assistive technologies).
3. If this is the case for each <canvas> element, the test is validated.

1. Find in the document the images (<img>, <input> elements with the type="image" attribute, <area>, <object>, <embed>, <svg>, <canvas> elements, or elements possessing a WAI-ARIA role="img" attribute) conveying information whose detailed description uses a WAI-ARIA aria-describedby attribute.
2. For each image, check that the content of the detailed description is correctly rendered (by assistive technologies).
3. If this is the case for each image, the test is validated.

1. Find in the document the elements with a WAI-ARIA role="img" attribute that contain information requiring a detailed description.
2. For each role="img" element, check that there is
   • either a WAI-ARIA aria-label attribute containing the text alternative and a reference to an adjacent detailed description;
   • or a WAI-ARIA aria-labelledby attribute associating a passage of text acting as a text alternative and another acting as a detailed description;
   • or a WAI-ARIA aria-describedby attribute associating a passage of text acting as a detailed description;
   • or a link or an adjacent button giving access to the detailed description.
3. If this is the case for each role="img" element, the test is validated.

1. Find in the document the images that are implemented using an <img> element and have a detailed description.
2. For each image, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <input> elements with the type="image" attribute which have a detailed description.
2. For each <input> element with the type="image" attribute, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <object> elements with the type="image/..." attribute which have a detailed description.
2. For each <object> element with the type="image/..." attribute, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <embed> elements with the type="image/..." attribute which have a detailed description.
2. For each <embed> element with the type="image/..." attribute, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <svg> elements that have a detailed description.
2. For each <svg> element, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find in the document the <canvas> elements that have a detailed description.
2. For each <canvas> element, check that the detailed description is relevant.
3. If this is the case for each image, the test is validated.

1. Find the frames in the document (<iframe> or <frame> element).
2. For each frame, check that it has a title attribute.
3. If this is the case for each frame, the test is validated.

1. Find in the document the information provided by the colour in a word or set of words.
2. For each of these pieces of information, check that there is another way of retrieving this information (presence of a title attribute, an icon or a graphic effect in terms of shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find the information (provided by colour) in a text in the document.
2. For each of these items of information, check that there is another way of retrieving the information (presence of a title attribute, an icon or a graphic effect in terms of shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find the information provided by the colour in an image in the document.
2. For each of these items of information, check that there is another way of retrieving this information (presence of a title attribute, an icon or a graphic effect based on shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find the information provided by the colour in a CSS property in the document.
2. For each of these pieces of information, check that there is another way of retrieving this information (presence of a title attribute, an icon or a graphic effect based on shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find the information provided by the colour in the document in a time-based medium.
2. For each of these pieces of information, check that there is another way of retrieving this information (presence of a title attribute, an icon or a graphic effect of shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find the information provided by colour in non-time-based media in the document.
2. For each of these items of information, check that there is another way of retrieving this information (presence of a title attribute, an icon or a graphic effect based on shape or position, a typographic effect, etc.).
3. If this is the case for each piece of information, the test is validated.

1. Find in the document texts and images of texts with no bold effect and a rendered size of less than 24px that could cause contrast problems.
2. For each of these texts, check that
   • either the contrast ratio between the text and its background is 4.5:1, at least;
   • or a mechanism allows the user to display the text with a contrast ratio of at least 4.5:1.
3. If this is the case for each text, the test is validated.

1. Find in the document bold texts and bold images of texts with a rendered size of less than 18.5px that could cause contrast problems.
2. For each of these texts, check that
   • either the contrast ratio between the text and its background is 4.5:1, at least;
   • or a mechanism allows the user to display the text with a contrast ratio of at least 4.5:1.
3. If this is the case for each text, the test is validated.

1. Find in the document texts and images of texts without bold effect with a rendered size greater than or equal to 24px that could cause contrast problems.
2. For each of these texts, check that
   • either the contrast ratio between the text and its background is at least 3:1;
   • or a mechanism allows the user to display the text with a contrast ratio of at least 3:1.
3. If this is the case for each text, the test is validated.

1. Find in the document bold texts and bold images of texts with a rendered size greater than or equal to 18.5px that could cause contrast problems.
2. For each of these texts, check that
   • either the contrast ratio between the text and its background is at least 3:1;
   • or a mechanism allows the user to display the text with a contrast ratio of at least 3:1.
3. If this is the case for each text, the test is validated.

1. Find the mechanisms used to display a compliant contrast ratio in the document.
2. For each of these mechanisms, check that the contrast ratio between the text and the background colour is sufficiently high.
3. If this is the case for each mechanism, the test is validated.

1. Find in the document the time-based media (<audio>, <video> or <object> elements) that require a transcript.
2. For each audio-only time-based media item, check for the presence of a transcript:
   • either accessible via a button or an adjacent link (a URL or an anchor);
   • or clearly identifiable adjacent.
3. If this is the case for each time-based media, the test is validated.

1. Find in the document the time-based media (<video> or <object> elements) that require a transcript.
2. For each video-only time-based media, check for the presence of:
   • an alternative audio-only version accessible via an adjacent link or button (a URL or an anchor); or
   • an adjacent alternative audio-only version; or
   • a transcript accessible via an adjacent link or button (a URL or an anchor);
   • a clearly identifiable adjacent transcript; or
   • a synchronised audio description; or
   • an alternative version with an audio description accessible by means of an adjacent link or button (a URL or an anchor).
3. If this is the case for each time-based media, the test is validated.

1. Find synchronised the time-based media (<video> or <object> elements) in the document that require a transcript.
2. For each synchronised time-based media, check for the presence of:
   • a transcript accessible via an adjacent link or button (a URL or an anchor); or
   • or a clearly identifiable adjacent transcript; or
   • a synchronised audio description; or
   • an alternative version with an audio description accessible by means of an adjacent link or button (a URL or an anchor).
3. If this is the case for each time-based media, the test is validated.

1. Find in the document the pre-recorded audio-only time-based media that have a transcript.
2. For each audio-only time-based media, check that the transcript is relevant.
3. If this is the case for each time-based media, the test is validated.

1. Find the pre-recorded video-only time-based media in the document that have a transcript.
2. For each video-only time-based media, check the relevance of:
   • the transcript; or
   • the synchronised audio description; or
   • the synchronised audio description of the alternative version; or
   • the alternative audio version only.
3. If this is the case for each time-based media, the test is validated.

1. Find the synchronised pre-recorded time-based media in the document.
2. For each synchronised time-based media, check the relevance of:
   • the transcript; or
   • the synchronised audio description; or
   • the synchronised audio description of the alternative version.
3. If this is the case for each time-based media, the test is validated.

1. Find the synchronised pre-recorded time-based media in the document.
2. For each synchronised time-based media, check for the presence of
   • either captions;
   • or an alternative version with captions accessible via a link or adjacent button.
3. If this is the case for each time-based media, the test is validated.

1. Find the synchronised time-based media with captions in the document using a <track> element.
2. For each synchronised time-stream, check that the <track> tag has a kind="captions" attribute.
3. If this is the case for each synchronised time-based media, the test is validated.

1. Find the synchronised time-based media with captions in the document.
2. For each synchronised time-based media, check that the captions are:
   • in the language of the video (if the spoken content is in English, the captions must be in English);
   • relevant (all important audio information is present, particularly dialogue);
   • correctly synchronised. If there is no delay between the spoken content and the appearance of the captions, the captions are correctly synchronised. The reference standard specifies that captions should appear within 100 ms of the caption time stamp.
3. If this is the case for each synchronised time-based media, the test is validated.

1. Find all non-time-based media in the document.
2. For each non-time-based media, check that a clearly identifiable adjacent link or button
   • either contains the address (url) of a page containing an alternative;
   • or provides access to an alternative on the page.
3. If this is the case for each non-time-based media, the test is validated.

1. Find the non-time-based media associated with an alternative in the document.
2. For each non-time-based media, check that
   • the page referenced by the adjacent link or button is accessible;
   • the alternative on the page, referenced by the adjacent link or button, is accessible.
3. If this is the case for each non-time-based media, the test is validated.

1. Find in the document the non-time-based media associated with an alternative.
2. For each non-time-based media, check that the alternative is relevant (it provides access to the same content and similar functions).
3. If this is the case for each non-time-based media, the test is validated.

1. When the document is loaded, if a sound is triggered automatically, check that
   • either the sound sequence lasts 3 seconds or less;
   • or a device (a button, for example) on the element that triggered the sound (see note), or on the page, can be used to stop it;
   • or the volume of the sequence can be controlled by the user, independently of the system volume control.
2. If this is the case, the test is validated.

Note: the following elements are likely to trigger sounds when the page is loaded: <audio>, <video>, <object>, <embed>, <bgsound> elements or JavaScript code (using the Web Audio API, for example).

1. Find the time-based media in the document.
2. For each time-based media, check that the mandatory viewing control functions are present:
   • at least: play, pause or stop;
   • if the media has sound, it must have a sound on/off function;
   • if the media has subtitles or captions, it must have a function for controlling the appearance/disappearance of subtitles or captions;
   • if the media has audio description, it must have a function for controlling the appearance/disappearance of the audio description.
3. If this is the case for each time-based media, the test is validated.

1. Find the time-based media with control features in the document.
2. For each time-based media, check that
   • either the feature is accessible via the keyboard and any pointing device;
   • or a feature accessible via the keyboard and any pointing device enabling the same action to be performed is present on the page.
3. If this is the case for each time-based media, the test is validated.

1. Find the time-based media with control functions in the document.
2. For each time-based media, check that:
   • either the functionality can be activated using the keyboard and any pointing device;
   • or the page contains a function that can be activated using the keyboard and any pointing device to perform the same action.
3. If this is the case for each time-based media, the test is validated.

1. Find the data tables in the document.
2. For each column header that applies to the entire column, check that the column header is implemented using
   • either a <th> element;
   • or an element with a WAI-ARIA role="columnheader" attribute.
3. If this is the case for each column header applying to the entire column, the test is validated.

1. Find the data tables in the document.
2. For each line header that applies to the whole line, check that the line header is implemented using
   • either a <th> element;
   • or an element with a WAI-ARIA role="rowheader" attribute.
3. If this is the case for each line header applying to the entire line, the test is validated.

1. Find the data tables in the document.
2. For each header which does not apply to the entire row or column, check that the row header is implemented using a <th> element.
3. If this is the case for each header which does not apply to the whole row or column, the test is validated.

1. Find the data tables in the document.
2. For each cell associated with several headers, is it implemented using a <th> or <td> tag.
3. If this is the case for each header that does not apply to the whole row or column, the test is validated.

1. Find the data tables in the document.
2. For each header (<th> element) applying to the entire row or column, check that the <th> element has
   • either a unique id attribute;
   • or a scope attribute;
   • or a WAI-ARIA role="rowheader" or "columnheader" attribute.
3. If this is the case for each header applying to the entire row or column, the test is validated.

1. Find the data tables in the document.
2. For each header (<th> element) applying to the whole row or column and provided with a scope attribute, check that the scope attribute has
   • either a "row" value for row headers;
   • or a "col" value for column headers.
3. If this is the case for each header which applies to the entire row or column and has an scope attribute, the test is validated.

1. Find the data tables in the document.
2. For each header (<th> element) which does not apply to the whole row or column, check that the <th> element
   • has a unique id attribute;
   • does not have a scope attribute;
   • does not have a WAI-ARIA role="rowheader" or "columnheader" attribute.
3. If this is the case for each header that does not apply to the entire row or column, the test is validated.

1. Find the data tables in the document.
2. For each <td> or <th> element associated with one or more headers with an id attribute, check that
   • the <td> or <th> element has a headers attribute;
   • the headers attribute has the list of id attribute values for the associated headers.
3. If this is the case for each <td> or <th> element associated with one or more headers with an id attribute, the test is validated.

1. Find the data tables in the document.
2. For each header that applies to the entire row or column and has a WAI-ARIA role="rowheader" or "columnheader" attribute, check that the element has
   • either a WAI-ARIA role="rowheader" attribute for row headers;
   • or a WAI-ARIA role="columnheader" attribute for column headers.
3. If this is the case for each header that applies to the entire row or column and has a WAI-ARIA role="rowheader" or "columnheader" attribute, the test is validated.

1. Find the text links in the document.
2. For each text link, check that the information used to understand the function and destination of the link is
   • either the accessible name of the link alone;
   • or the link context.
3. If this is the case for each text link, the test is validated.

1. Find the image links in the document (link with the content of an <img> element or an element with the WAI-ARIA role="img" attribute, an <area> element with a href attribute, an <object> element, a <canvas> element or a <svg> element).
2. For each image link, check that the information used to understand its function and destination is
   • either the accessible name of the link alone, provided by the text alternative (image);
   • or the link context.
3. If this is the case for each image link, the test is validated.

1. Find composite links in the document (links made up of both text content and image elements).
2. For each composite link, check that the information used to understand the function and destination of the link is
   • either the accessible name of the link alone, provided by the combination of the text content and the alternative text for the image;
   • or the link context.
3. If this is the case for each composite link, the test is validated.

1. Find SVG links in the document (<svg> element which has an <a> element with a xlink-href attribute (SVG 1.1) or href (SVG 2)).
2. For each SVG link, check that what makes it possible to understand the function and destination of the link is
   • either the accessible name of the link alone, provided by the accessible name of the <svg> element (generally resolved from the content of a <text> element);
   • or the link context.
3. If this is the case for each SVG link, the test is validated.

1. Find in the document links other than SVG whose content is provided both by a visible label and by the content of either a title attribute, an aria-label attribute or an aria-labelledby attribute.
2. For each link, check that the value of the title attribute or the aria-label attribute or the aria-labelledby attribute contains the visible label.
3. If this is the case for each link, the test is validated for links other than SVG.
4. Find in the document the SVG links whose content is provided both by a visible label and by the content of either an aria-labelledby attribute, or an aria-label attribute or a title element (direct child of the <svg> element) or an x-link:title attribute (SVG 1.1) or one or more <text> elements.
5. For each SVG link, check that the value of the aria-labelledby attribute or the aria-label attribute or the <title> element or the x-link:title attribute or one or more <text> elements contains the visible label.
6. If this is the case for each SVG link, the test is validated for the SVG links.
7. If the test is validated for both non-SVG links and SVG links, the test is validated overall.

1. Find any links in the document.
2. For each link, check that the content of the <a> element (or of an element with a WAI-ARIA role=link attribute) contains an accessible name (text or alternative).
3. If this is the case for each link, the test is validated.

1. Find in the document all the elements on which a JavaScript event handler is implemented (for example click, focus, mouseover, blur, keydown, touch, etc.).
2. Check that the element can be accessed using the keyboard:
   • It can be reached with the tab key.
   • If the element manages a simple action, it can be activated from the keyboard using the enter key.
   • If the element handles a complex action, it can be accessed from the keyboard (generally using the arrow keys).
3. If not, check that the page contains an element that can be accessed from the keyboard to perform the same action.
4. Check that the element can be accessed using any pointing device (mouse, touch, stylus, etc.).
5. If not, check that the page contains an element that can be accessed using a pointing device and that performs the same action.
6. If this is the case, the test is validated.

1. Activate, one after the other, all elements capable of receiving the focus.
2. Check that the focus is not removed via a JavaScript function.
3. If so, the test is validated.

1. Find the default language indication in the document.
2. Check for the presence of a language indication
   • either using the lang attribute on the html tag if the code is HTML5 or HTML4;
   • or using the lang and xml:lang attributes on the html tag if the code is XHTML 1.0;
   • or using the xml:lang attribute on the html tag if the code is XHTML 1.1;
   • otherwise, check for the presence of a language indication on each text element or one of its parents.
3. If this is the case, the test is validated.

1. The default language is indicated in the document.
2. Check that the language code is
   • valid (compliant with ISO 639-1 or ISO 639-2 and subsequent standards);
   • relevant (indicating the main language of the document).
3. If this is the case, the test is validated.

1. Find in the document the title implemented using a <title> element.
2. If this is the case, the test is validated.

1. Find in the document the title implemented using a <title> element.
2. Check whether the content of the <title> element is sufficiently relevant (it allows the page to be found in the browsing history or the list of tabs).
3. If this is the case, the test is validated.

1. Find passages of text in a foreign language, with the exception of
   • proper names;
   • words of foreign origin, present in the dictionary of the language of the document;
   • words of foreign origin in common usage whose pronunciation does not cause misunderstanding.
2. Check that each passage of text selected has a language indication (lang and/or xml:lang attribute on the element itself or one of its parents).
3. If this is the case, the test is validated.

1. For each passage of text validated in test 8.7.1, check that
   • The language code is valid.
   • The language indication is relevant.
2. If this is the case, the test is validated.

1. Find the headings in the document (<hx> tag or tag with a WAI-ARIA role="heading" attribute associated with a WAI-ARIA aria-level attribute).
2. Check that the hierarchy between the headings is appropriate.
3. If this is the case, the test is validated.

1. For each heading identified in test 9.1.1, check that its content is relevant.
2. If this is the case for each heading, the test is validated.

1. For each heading identified in test 9.1.1, check that
   • either it is implemented using a <hx> tag ("x" designating a numerical value between 1 and 6);
   • or it is implemented using a tag with a WAI-ARIA role="heading" attribute and a WAI-ARIA aria-level=x attribute ("x" designating a numerical value).
2. If this is the case for each heading, the test is validated.

1. Check that the header region is structured using a <header> element.
2. Check that the main and secondary navigation areas are implemented using a <nav> element.
3. Check that the <nav> element is not used outside the structuring of the main and secondary navigation zones.
4. Check that the main content region is structured using a <main> element.
5. If the document has several <main> elements, check that only one of these elements is visible (the other occurrences of the element have a hidden attribute).
6. Check that the footer region is structured using a <footer> element.
7. If this is the case for each content zone, the test is validated.

1. Find in the document the elements which are likely to receive the focus (interface elements such as links or form controls, as well as any element with a tabindex attribute with a value equal to or greater than 1).
2. For each element likely to receive the focus, check that the visual indication of when the focus is taken is present (by acting on the outline or background or both) and is sufficiently contrasted (contrast ratio equal to or greater than 3:1).
3. If this is the case for each element likely to receive the focus, the test is validated.

1. Find hidden content (elements with the hidden attribute or the WAI-ARIA aria-hidden attribute, or a class or set of CSS styles likely to hide the content).
2. For each hidden content, check that
   • Either the hidden content is intended to be ignored by assistive technologies (a web analytics tracker for example).
   • Or the hidden content is not intended to be ignored by the assistive technologies, in which case it is made renderable by the assistive technologies by means of
     • Either an action performed by the user via the keyboard or any other pointing device on an element preceding the hidden content.
     • Or a programming function that repositions the focus on the content.
3. If this is the case for each hidden content item, the test is validated.

1. Find in the document the information for a text given by its shape, size or position.
2. For each piece of information given by shape, size or position, check that there is another way of retrieving this information.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for an image given by its shape, size or position.
2. For each piece of information given by shape, size or position, check that there is another way of retrieving this information.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for a time-based media given by its shape, size or position.
2. For each item of information given by shape, size or position, check that there is another way of retrieving this information.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for a non-time-based media given by its shape, size or position.
2. For each item of information given by shape, size or position, check that there is another way of retrieving this information.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for a text given by its shape, size or position.
2. For each piece of information given by shape, size or position, check that the alternative means of retrieving this information is relevant, i.e. that it allows the information to be transmitted in all viewing contexts and for all users.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for an image given by its shape, size or position.
2. For each piece of information given by its shape, size or position, check that the alternative means of retrieving this information is relevant, i.e. that it allows the information to be transmitted in all viewing contexts and for all users.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for a time-based media given by its shape, size or position.
2. For each item of information given by shape, size or position, check that the alternative means of retrieving this information is relevant, i.e. that it allows the information to be transmitted in all viewing contexts and for all users.
3. If this is the case for each piece of information, the test is validated.

1. Find in the document the information for a non-time-based media given by its shape, size or position.
2. For each item of information given by shape, size or position, check that the alternative means of retrieving this information is relevant, i.e. that it allows the information to be transmitted in all viewing contexts and for all users.
3. If this is the case for each piece of information, the test is validated.

1. Find additional content in the document that becomes visible when a user interface component is hovered using a CSS mechanism (pseudo-class :hover).
2. For each additional content, check that the additional content also appears
   • When the component is activated using the keyboard or any other pointing device.
   • When the component is focused.
   • When another component is activated or focused.
3. If this is the case for each additional content item, the test is validated.

1. Find in the document the additional content that becomes visible when the focus of a user interface component is activated using a CSS mechanism (pseudo-class :focus).
2. For each additional content item, check that the additional content also appears:

• When the component is activated using the keyboard or any other pointing device.
• When the component is hovered over.
• When another component is activated or hovered over.

3. If this is the case for each additional content item, the test is validated.

1. Find form fields in the document.
2. For each form field, check that the form field
   • has a WAI-ARIA aria-labelledby attribute referencing an identified passage of text;
   • has a WAI-ARIA aria-label attribute;
   • is associated with a <label> element having a for attribute;
   • has a title attribute;
   • a button adjacent to the form field provides it with a visible label and a visually hidden <label> element or a WAI-ARIA aria-label, aria-labelledby or title attribute provides it with an accessible name.
3. If this is the case for a form field, the test is validated.

1. Find the form fields associated with a <label> element in the document.
2. For each form field, check that
   • The form field has an id attribute.
   • The value of the for attribute of the <label> element is equal to the value of the id attribute.
3. If this is the case for the form field, the test is validated.

1. Find in the document form fields whose label is not visible or nearby (hidden, using the aria-label attribute) or is not attached to the field (using the aria-labelledby attribute).
2. For each form field, check that the form field
   • either has a title attribute, the content of which makes it possible to understand the nature of the expected input;
   • is accompanied by a passage of text next to the field which becomes visible when the focus is taken, so that the nature of the expected input can be understood;
   • is accompanied by a passage of visible text next to the field, enabling the nature of the expected input to be understood.

1. Find the form fields in the document whose label is provided by a <label> element.
2. For each form field, check that the content of the element is relevant.
3. If this is the case for each form field, the test is validated.

1. Find in the document the form fields whose label is provided by a title attribute.
2. For each form field, check that the content of the attribute is relevant.
3. If this is the case for each form field, the test is validated.

1. Find in the document the form fields whose label is provided by a WAI-ARIA aria-label attribute.
2. For each form field, check that the content of the attribute is relevant.
3. If this is the case for each form field, the test is validated.

1. Find in the document the form fields whose label is provided by a WAI-ARIA aria-labelledby attribute.
2. For each form field, check that the content of the referenced passage of text is relevant.
3. If this is the case for each form field, the test is validated.

1. Find in the document the form fields whose label is provided both by a visible label and by the content of either a <label> element, or a title attribute or a aria-label attribute or a aria-labelledby attribute.
2. For each form field, check that the content of the <label> element or the title attribute or the aria-label attribute or the aria-labelledby attribute contains the visible label.
3. If this is the case for each form field, the test is validated.

1. Find the form fields in the document whose visible label is provided by an adjacent button.
2. For each form field, check that the visible content of the button is relevant.
3. If this is the case for each form field, the test is validated.

1. Find the related form controls in the document (for example, a group of identity information entries, a series of tick boxes, a date entry in several successive fields, etc.).
2. For each group of form related form controls, check that these related form controls are grouped together:
   • either in a <fieldset> element;
   • or in an element with a WAI-ARIA role="group" attribute;
   • or in an element with a WAI-ARIA role="radiogroup" or "group" attribute, in the case of <input> elements of type radio (or elements with a WAI-ARIA role="radio" attribute).
3. If this is the case for each group of form related form controls, the test is validated.

1. Find the groups of related form controls in the document.
2. For each group of related form controls, check that
   • If the grouping uses a <fieldset> element, the <fieldset> element has a <legend> element.
   • If the grouping element uses a WAI-ARIA role="group" or "radiogroup" attribute, it has a WAI-ARIA aria-label or aria-labelledby attribute.
3. Otherwise, for each of the related form controls, check for the presence of
   • either a title attribute to determine whether the field belongs to the field grouping;
   • or an aria-label attribute to determine whether the field belongs to the field grouping;
   • or an aria-labelledby attribute which references a passage of text used to determine whether the field belongs to the field grouping;
   • or an aria-describedby attribute which references a passage of text used to determine whether the field belongs to the field grouping;
4. If this is the case for each group of form fields or for each of the related form controls, the test is validated.

1. Find groups of related form controls in the document.
2. For each group of related form controls in the form, or for each related form control that has a legend, check that the text in the legend is relevant.
3. If this is the case for each group of form fields or for each of the related form controls, the test is validated.

1. Find the buttons in a form in the document.
2. For each button, check that its visible text and accessible name are relevant.
3. If this is the case for each button, the test is validated.

1. Find the buttons in a form in the document.
2. For each button, check that its accessible name contains at least its visible label.
3. If this is the case for each button, the test is validated.

1. Find the mandatory form fields in the document.
2. For each form field, check that before validating the form
   • either a mandatory field indication is visible, identifying the field;
   • or the field has an aria-required="true" or required attribute.
3. If this is the case for each mandatory form field, the test is validated.

1. Find in the document the mandatory form fields that have an aria-required="true" or required attribute.
2. For each form field, check that before validating the form
   • either a mandatory field indication is visible and located in the label associated with the field;
   • or a mandatory field indication is visible in the passage of text associated with the field.
3. If this is the case for each mandatory form field which has an aria-required="true" or required attribute, the test is validated.

1. Find in the document the error messages indicating that a mandatory field has not been entered.
2. For each error message, check that
   • either the error message is visible and allows the field concerned to be identified;
   • or the mandatory field associated with the error message has an aria-invalid="true" attribute.
3. If this is the case for each error message indicating that a mandatory field has not been entered, the test is validated.

1. Find in the document the mandatory form fields which have an aria-invalid="true" attribute.
2. For each form field, check that
   • either the error message indicating that the input is invalid is visible and located in the label associated with the field;
   • or the error message indicating that the input is invalid is visible and located in the passage of text associated with the field.
3. If this is the case for each mandatory form field which has an aria-invalid="true" attribute, the test is validated.

1. Find in the document mandatory form fields with an associated instruction or indication of data type and/or format.
2. For each form field, check that the instruction or indication of mandatory data type and/or format is visible before the form is validated:
   • is visible and enables the field concerned to be identified;
   • visible in the label or passage of text associated with the field.
3. If this is the case for each mandatory form field with an associated instruction or indication of data type and/or format, the test is validated.

1. Find in the document error messages that provide an instruction or indication of data type and/or mandatory format for a field.
2. For each error message, check that
   • either the error message is visible and allows the field concerned to be identified;
   • or the field associated with the error message has an aria-invalid="true" attribute.
3. If this is the case for each error message indicating that a mandatory field has not been entered, the test is validated.

1. Find in the document the form fields which have an aria-invalid="true" attribute.
2. For each form field, check that
   • either an instruction or indication of data type and/or mandatory format is visible and located in the <label> element associated with the field;
   • or an instruction or indication of data type and/or mandatory format is visible and located in the passage of text associated with the field.
3. If this is the case for each form field which has an aria-invalid="true" attribute, the test is validated.

1. Find the content grouping zones in the document (header region, main navigation region, main content region, footer region and search engine region).
2. For each zone, check that the zone
   • either has a WAI-ARIA landmark role corresponding to its nature;
   • or has a heading whose content makes it possible to understand the nature of the zone content;
   • or can be hidden by means of a button directly preceding the zone in the order of the source code;
   • or can be avoided by means of a skip link directly preceding the zone in the order of the source code;
   • or can be reached using a bypass link, either visible by default, or visible when focused during tabbing.
3. If this is the case for each content grouping zone, the test is validated.

1. Find in the document the main content region (indicated by the visible main content element).
2. Check that the zone
   • either can be avoided using a skip link directly preceding the zone in the source code order;
   • or can be reached by means of a quick access link visible when focused by tabbing.
3. If this is the case, the test is validated.

1. Find in the document the main content region (indicated by the visible main element).
2. Check that the bypass or skip link to the zone is
   • located at the same place in the presentation;
   • always present in the same relative order in the source code (generated on the client side);
   • visible when focused during tabbing;
   • functional.
3. If this is the case, the test is validated.

1. Tab forward (Tab key) and backward (Shift+Tab key) through all the content in the document.
2. Check that the order in which the focus is moved is consistent with the content in question (for example, the navigation sequence in a modal window should only consider the interface elements present in this window).
3. If this is the case, the test is validated.

Note: the navigation sequence does not have to follow the natural reading order (left to right and top to bottom, for example) as long as the elements are accessible in a coherent order.

1. Find all the content inserted in the document using a script (display hidden elements, update content using AJAX for example).
2. Position the tab on the trigger element and activate it.
3. After displaying the updated content, check that the navigation sequence remains consistent (correct repositioning of the focus).
4. If this is the case, the test is validated.

1. Find all the interface elements in the document that can receive focus (using the tab key or a script).
2. For each interface element, check that the user can move to the next or previous element that can receive focus
   • either using the tab key (Tab or Shift+Tab);
   • or by means of another keyboard interaction of which the user is aware (for example, the arrow keys).
3. If this is the case for each interface element, the test is validated.

Note: some complex interface elements, such as a group of radio buttons, a listbox and all the components developed with WAI-ARIA call for optimised navigations which generally use the arrow keys to move from one part of the component to another. For example, in a group of radio buttons, the options can be navigated using the arrow keys. Similarly, in a tabbed system, the user activates the tabs using the arrow keys. The test on the keyboard trap is then limited to checking that the component is reached with the tab key and that it is possible to move on to the next component or return to the previous component.

1. Find in the document all the additional content that appears when hovering, focusing or activating a user interface component.
2. For each additional content item, if it contains user interface components that the user can interact with using the keyboard (for example, a customised tooltip with a link in its content), check that these user interface components can be reached using the keyboard.
3. If this is the case for each additional content item, the test is validated.

1. Find in the document the refreshes initiated in the content by an <object>, <embed>, <svg>, <canvas> element or by a <meta http-equiv="refresh" content="[compteur]"> element (in the <head> element of the page).
2. For each refresh, check that
   • either there is a mechanism allowing the user to stop and restart the refresh;
   • or a mechanism is present which allows the user to increase the time limit between two refreshes by at least ten times;
   • or the presence of a mechanism which warns the user of the imminence of the refreshment, allows the user at least 20 seconds to increase the time limit before the next refreshment;
   • or the time limit between two refreshes is at least twenty hours.
3. If this is the case, the test is validated.

1. In the document, find an automatic redirect initiated by a <meta http-equiv="refresh" content="0;URL='[targeted URL]'" /> element.
2. Check that the redirect is immediate.
3. If this is the case, the test is validated.

1. Find in the document the automatic redirects initiated by a script (in the form of a countdown for example).
2. For each automatic redirect, check that
   • Either there is a mechanism enabling the user to stop and restart the redirect.
   • Or the presence of a mechanism allows the user to increase the time limit before refreshment by at least ten times.
   • Or the presence of a mechanism, that warns the user of the imminence of the refreshment, gives the user at least 20 seconds to increase the time limit before the next refreshment.
   • Or the time limit before the redirect is at least twenty hours.
3. If this is the case, the test is validated.

1. Find in the document the procedures for limiting the time of a session (for example, after authentication).
2. For each process, check that
   • either the presence of a mechanism allows the user to remove the time limit;
   • or the presence of a mechanism allows the user to increase the time limit;
   • or the time limit is at least twenty hours.
3. If this is the case, the test is validated.

1. Find in the document content which flashes or causes flash effects of the animated image, video (see note) or animation type (<img>, <svg>, <canvas>, <embed>, <object> or <video> elements).
2. For all content that flashes or causes flash effects, check that
   • either the frequency of the effect is less than 3 per second;
   • or the total surface area is less than 21824 pixels.
3. If this is the case for each content item that flashes or causes flash effects, the test is validated.

Note: assessing this criterion can be complex. When the effect is managed by a script or using CSS, analysis of the code is sufficient. The PEAT tool can be used to analyse videos in .avi format, for example. An example of a video that caused epileptic seizures can be found here: London 2012 Olympics Seizure.

1. Find in the document the content that flashes or causes flash effects using a script.
2. For each content item that flashes or causes flash effects, check that
   • either the frequency of the effect is less than 3 per second;
   • or the total surface area is less than 21824 pixels.
3. If this is the case for each content item that flashes or causes flash effects, the test is validated.

1. Find content in the document that flashes or causes flash effects using CSS animation.
2. For each piece of content that flashes or causes flash effects, check that
   • either the frequency of the effect is less than 3 per second;
   • or the total surface area is less than 21824 pixels.
3. If this is the case for each content item that flashes or causes flash effects, the test is validated.

1. Find moving content in the document (obtained using an image, script or CSS effect) triggered automatically when the page is loaded or when content is displayed (see note).
2. For each content item, check that
   • either the duration of the movement is less than 5 seconds;
   • or there is a mechanism (a button, for example) to stop and restart the movement;
   • or either the presence of a mechanism (such as a button) means that the moving content can be hidden and displayed again;
   • or the presence of a mechanism (e.g. a button) enables the entire content to be displayed without movement.
3. If this is the case for each piece of moving content, the test is validated.

1. Find blinking content in the document (obtained using an image, a script or a CSS effect) triggered automatically when the page is loaded or when content is displayed (see note).
2. For each content item, check that
   • either the blinking time is less than 5 seconds;
   • there is a mechanism (a button, for example) to stop and restart the blinking;
   • or the presence of a mechanism (a button, for example) means that the blinking content can be hidden and displayed again;
   • or a mechanism (such as a button) can be used to display all the blinking content.
3. If this is the case for each blinking content item, the test is validated.

Note: Stopping or pausing moving or blinking content by means of when focused (for example, the effect is only suspended when focused) is not considered a compliant process. In some cases, movement cannot be stopped, for example in the case of a progress bar, in which case the criterion is not applicable.