RAWeb 1: Criteria and tests

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 in the document the images of text implemented using an <img> element (or an element with the WAI-ARIA role="img" attribute).
2. For each image, check that:
   • either a replacement mechanism exists;
   • or the image contains text which uses a graphic effect which cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. Find in the document the "image of text" buttons (<input> element with the type="image" attribute).
2. For each image, check that
   • either there is a replacement mechanism;
   • or the image contains text that uses a graphic effect that cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. Find in the document the image of text objects (<object> element with the type="image/..." attribute).
2. For each image, check that
   • either there is a replacement mechanism;
   • or the image contains text which uses a graphic effect which cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. Find in the document the embedded images of text (<embed> element with the type="image/..." attribute).
2. For each image, check that
   • Either there is a replacement mechanism;
   • Or the image contains text which uses a graphic effect which cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. Find in the document the bitmap images of text (<canvas> element).
2. For each image, check that
   • either there is a replacement mechanism;
   • or the image contains text that uses a graphic effect that cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. Find in the document the vector images of texts (<svg> element) that carry information and whose text is not completely implemented using <text> elements.
2. For each image, check that
   • either there is a replacement mechanism;
   • or the image contains text which uses a graphic effect which cannot be reproduced in CSS.
3. If this is the case for each image, the test is validated.

1. In the document, find the images with a legend implemented using the <img> element, an <input> element with the type="image" attribute or an element with the WAI-ARIA role="img" attribute.
2. For each image, check that
   • the image and its legend are contained in a <figure> tag;
   • the <figure> tag has a WAI-ARIA property role="figure" or role="group";
   • the <figure> tag has a WAI-ARIA aria-label attribute whose content is identical to the content of the legend;
   • the legend is contained in a <figcaption> tag.
3. If this is the case for each image, the test is validated.

1. Find in the document the object images with a legend (<object> element with the type="image/..." attribute).
2. For each image, check that
   • the image and its legend are contained in a <figure> tag;
   • the <figure> tag has a WAI-ARIA property role="figure" or role="group";
   • the <figure> tag has a WAI-ARIA aria-label attribute whose content is identical to the content of the legend;
   • the legend is contained in a <figcaption> tag.
3. If this is the case for each image, the test is validated.

1. Find in the document the embedded images with a legend (<embed> element with the type="image/..." attribute).
2. For each image, check that
   • the image and its legend are contained in a <figure> tag;
   • the <figure> tag has a WAI-ARIA role="figure" or role="group" property;
   • the <figure> tag has a WAI-ARIA aria-label attribute whose content is identical to the content of the legend;
   • the legend is contained in a <figcaption> tag.
3. If this is the case for each image, the test is validated.

1. Find in the document the vector images with a legend (<svg> element).
2. For each image, check that
   • the image and its legend are contained in a <figure> tag;
   • the <figure> tag has a WAI-ARIA role="figure" or role="group" property;
   • the <figure> tag has a WAI-ARIA aria-label attribute whose content is identical to the content of the legend;
   • the legend is contained in a <figcaption> tag.
3. If this is the case for each image, the test is validated.

1. Find in the document the bitmap images (<canvas> element).
2. For each image, check that
   • the image and its legend are contained in a <figure> tag;
   • the <figure> tag has a WAI-ARIA role="figure" or role="group" property;
   • the <figure> tag has a WAI-ARIA aria-label attribute whose content is identical to the content of the legend;
   • the legend is contained in a <figcaption> tag.
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 the frames in the document (<iframe> or <frame> element).
2. For each frame with a title attribute, check that its content is relevant.
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 user interface components that could cause contrast problems.
2. For each of these components, check that
   • either the contrast ratio between the colours of the component in its various states and the adjacent background colour is at least 3:1;
   • or a mechanism allows the user to display the component with a contrast ratio of at least 3:1.
3. If this is the case for each component, the test is validated.

1. Find in the document the graphic elements that could cause contrast problems.
2. For each of these elements, check that
   • either the contrast ratio between the colours of the graphic element required to understand it and the adjacent background colour is at least 3:1;
   • or a mechanism allows the user to display the graphic element with a contrast ratio of at least 3:1.
3. If this is the case for each component, the test is validated.

1. Find in the document the graphic elements that could cause contrast problems.
2. For each of these elements, check that
   • either the contrast ratio between the different adjacent colours of the graphic element, when they are necessary for its understanding, is at least 3:1;
   • a mechanism allows the user to display the graphic element with a contrast ratio of at least 3:1.
3. If this is the case for each graphic element, the test is validated.

1. Find in the document the mechanisms that enable a compliant contrast ratio to be displayed.
2. For each of these mechanisms, check that the contrast ratio between the colours of the component or the graphic element conveying information of which it is composed 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 in the document the pre-recorded video-only time-based media that require an audio description.
2. For each video-only time-based media, check for the presence of
   • either an audio description;
   • or an alternative version with an audio description accessible via a button or an adjacent link (a URL or an anchor).
3. If this is the case for video-only time-based media, the test is validated.

1. Find in the document the pre-recorded synchronised time-based media that require an audio description.
2. For each synchronised time-based media, check the presence of:
   • either an audio description;
   • or an alternative version with an audio description accessible via a button or an adjacent link (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 video-only time-based media that have an audio description.
2. For each time-based media, check that the synchronised audio description is relevant (all the visual information that can be vocalised in the blanks of the main soundtrack is present, in particular the inlaid texts).
3. If this is the case for each video-only time-based media, the test is validated.

1. Find in the document the synchronised time-based media with an audio description.
2. For each time-based media, check that the audio description is relevant (all the visual information that can be vocalised in the blanks of the main soundtrack is present, including inlaid text).
3. If this is the case for each synchronised time-based media, the test is validated.

1. Find in the document the pre-recorded time-based media (video, audio or synchronised only).
2. For each time-based media, check that a passage of text (a heading or paragraph, for example) immediately preceding or following the time-based media enables it to be identified.
3. If this is the case for each 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 non-time-based media with control features in the document.
2. For each non-time-based media, check that
   • either the feature is accessible via the keyboard and any pointing device;
   • or a function 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 non-time-based media, the test is validated.

1. Find in the document the non-time-based media with control functions.
2. For each non-time-based media, check that
   • either the feature can be activated using the keyboard and any pointing device;
   • or a function operable 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 non-time-based media, the test is validated.

1. Find the non-time-based and time-based media in the document.
2. For each media, check that:
   • either the name, role, value, settings and status changes of the user interface components are accessible to assistive technologies via an accessibility API (for example, dynamically updated zones in a video player are correctly rendered);
   • or an alternative compatible with an accessibility API can be used to access the same accessibility features.
3. If this is the case for each time-based or non-time-based media, the test is validated.

1. Find the time-based and non-time-based media in the document that have an alternative compatible with assistive technologies.
2. For each media, check that
   • either the alternative is adjacent to the time-based or non-time-based media;
   • either the alternative is accessible via a link or an adjacent button;
   • or there is a mechanism for replacing the time-based or non-time-based media with its alternative.
3. If this is the case for each time-based or non-time-based media, the test is validated.

1. Locate pre-recorded time-based media with a synchronised caption track or audio description.
2. Check that it is possible to activate and deactivate captions or audio description without any additional steps to the main features (play, pause, etc.).
3. If this is the case, the test is validated.

Example: If the play button can be activated from the interface by a simple mouse click (without the need to activate a first component to display a drop-down menu, for example), the captions feature should be available in the same way, with a simple click. Conversely, if the captions feature is available from a drop-down menu that must first be activated (by a mouse click, for example), it will not be considered to be at the same level, as there will be an additional step to perform.

1. Identify the features that allow you to transmit (e.g. send content to another terminal or send a video by e-mail), convert (e.g. convert a video in .avi format to .mpg format) or record pre-recorded synchronised time-based media (e.g. record a video from a broadcasting platform onto your personal computer).
2. Perform each of the functions (transmit, convert and record).
3. For each function, check that the captions
   • are always present;
   • can be displayed;
   • are correctly synchronised;
   • retain their key features (for example, if the captions were coloured according to the speaker, the colours must be retained).
4. If this is the case, the test is validated.

1. Identify the features for transmitting, converting or recording time-based media. For example: send content to another terminal or by email, convert an .avi format video into an .mpg format, record a video from a broadcasting platform on your personal computer.
2. Perform each of the features (send, convert and record).
3. For each feature, check whether audio description
   • is present
   • can be activated;
   • is correctly synchronised:
     • the sounds and words of the audio description do not overlap with those of the original soundtrack and do not cause perception and comprehension problems;
     • the information conveyed in the audio description is given at the same time as the equivalent visual information appears.
4. If this is the case, the test is validated.

1. Locate pre-recorded time-based media with captions.
2. Define one or more caption presentation parameters from the customisation options provided by the operating system, for example: caption size, colour, border style, background colour, background opacity, etc. (Note: the standard does not give a precise list of parameters that must be defined, so the ability to modify a single caption characteristic is sufficient to make the criterion compliant).
3. Check that the defined parameters are applied to the captions.
4. If not, check the page to see if there is a function that allows you to change the presentation parameters of the captions (on the page or directly from the media player).
5. Check that the defined parameters are applied to the captions.
6. If this is the case, the test is validated.

1. Locate pre-recorded synchronised time-based media with subtitles.
2. Check for the presence of an audio track that would be the vocalised version of the subtitles:
   1. activate the sound track;
   2. check that the vocalised subtitles correspond to the displayed subtitles.
3. If not, check that there is a feature that allows you to voice subtitles:
   1. Text-to-speech. Some media players (e.g. AblePlayer or VideoJS) offer the option of adding a description track in the form of a text file (similar in construction to a subtitle file with a time stamp) that can be synthesised using the Web Speech API of browsers (this is known as text-to-speech, or TTS). By activating this feature, the browser reads the description. This feature can be used to provide a vocalised version of subtitles, and would therefore be considered a compliant implementation if properly documented for the user. To test it:
      1. activate the feature;
      2. start playing the multimedia content;
      3. check that the texts displayed by this means are vocalised.
   2. Description. Some media players (for example, AblePlayer or BrightCove) offer the option of integrating description tracks in the form of a text file (similar in construction to a subtitle file with a time stamp) which is declared in the code using the <track> tag with the kind="descriptions" attribute and whose final implementation has sufficient properties to enable them to be played back by screen readers (presence of the aria-live property, for example). This feature can be used to provide a version of the subtitles that can be vocalised by screen readers, and would therefore be considered a compliant implementation if it is properly documented for the user. To test it:
      1. activate the functionality;
      2. activate the screen reader;
      3. check that the texts displayed by this means are vocalised.
4. If not
   1. activate the subtitles;
   2. activate the screen reader;
   3. check that the spoken subtitles match the displayed subtitles.
5. Otherwise
   1. check for alternative media whose soundtracks contain voice-activated subtitles;
   2. check that the spoken subtitles match the displayed subtitles.
6. If this is the case, the test is validated.

1. Find in the document the complex data tables (data table - <table> element or element with a WAI-ARIA role="table" attribute - containing headers which are not distributed only on the first row and/or the first column of the grid or whose scope is not valid for the whole column or row).
2. For each complex data table, check that there is a passage of text explaining the nature and structure of the table:
   • either in the <caption> element;
   • or in the summary attribute of the <table> element (in versions of HTML and XHTML prior to HTML 5);
   • or in a passage of text linked to the table with the aria-describedby attribute.
3. If this is the case for each complex data table, the test is validated.

1. Find in the document the summaries of complex data tables (as determined by test 5.1.1).
2. For each summary, check that its content is relevant.
3. If this is the case for each summary (of table) of complex data tables, the test is validated.

1. Find the layout tables in the document.
2. For each layout table, check that
   • The order in which the cells are accessed is consistent with the content.
   • The <table> element has a WAI-ARIA role="presentation" attribute.
3. If this is the case for each layout table, the test is validated.

1. Find the data tables with a title in the document.
2. For each title, check that it is provided by means of
   • either a <caption> element;
   • or a title attribute;
   • or a WAI-ARIA aria-label attribute;
   • or a WAI-ARIA aria-labelledby attribute referencing a passage of text.
3. If this is the case for each data table title, the test is validated.

1. Find the data tables with a title in the document.
2. For each title, check that it is relevant.
3. If this is the case for each data table title, 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 layout tables in the document.
2. For each layout table, check that
   • The <table> element does not have a summary attribute, <caption>, <thead>, <th>, <tfoot> child elements or elements with a WAI-ARIA role="rowheader" or role="columnheader" attribute.
   • <td> elements do not have scope, headers or axis attributes.
3. If this is the case for each layout table, 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 all the user interface components generated or controlled using JavaScript in the document.
2. Check that
   • The component has a role consistent with its use (generally a button or a link).
   • The component has an explicit name.
   • The name of the component is consistent with the state of the feature or controlled content (for example, for a feature that displays or hides a content zone).
3. If not, check that there is an accessible user interface component providing access to the same feature.
4. If not, check for the presence of an accessible alternative providing access to the same feature.
5. If this is the case, the test is validated.

1. For each user interface component that has passed test 7.1.1, check that the user interface component is correctly rendered (by assistive technologies).
2. If not, check that an accessible alternative to the user interface component provides access to the same feature.
3. If this is the case, the test is validated.

1. For each user interface component that has passed the 7.1.1 test, check that the user interface component has
   • a relevant name (visible label);
   • a relevant role.
2. If the user interface component has an accessible name, check that this name is relevant and contains at least the visible label.
3. If this is the case, the test is validated.

1. Find alternatives to JavaScript features
2. Search the page for available alternatives to a JavaScript component or function.
3. Deactivate JavaScript in the document and find the proposed alternatives.
4. For each of the alternatives proposed, check that it provides access to the same content and similar functions.
5. If this is the case, the test is validated.

1. Find all non-text elements in the document that have been updated by a JavaScript function.
2. If the non-text element has an alternative, check that
   • the alternative is updated when the non-text content is updated;
   • the updated alternative is relevant.
3. If this is the case, 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 all the JavaScript events in the document which initiate a change of context, for example
   • dynamic updating of form fields;
   • the opening of a new page when an option in a combobox is activated (<select> element);
   • AJAX updating of an essential part of the page;
   • automatic launch of a video player when a playlist is selected;
   • focus manipulation to change the user's current position on the page.
2. Check that
   • the user is warned by a message about the script action and the type of change before it is triggered;
   • or the change of context is initiated by an explicit button (input of the submit, button or image type or the button tag);
   • or the change of context is initiated by an explicit link.
3. If this is the case, the test is validated.

1. Find the messages in the document that are status messages.
2. For each of these messages, determine the nature of the information contained in the message:
3. If the message informs you of the success or result of an action, or the state of an application, check that the element containing the message
   • either uses the WAI-ARIA role="status" attribute;
   • or uses the WAI-ARIA aria-live="polite" and aria-atomic="true" attributes.
4. If the message presents a suggestion, or warns of the existence of an error, check that the element containing the message
   • either uses the WAI-ARIA role="alert" attribute;
   • or uses the aria-live="assertive" and aria-atomic="true" attributes.
5. If the message indicates the progress of a process, check that the element containing the message
   • either uses one of the WAI-ARIA role="log", role="progressbar" or role="status" attributes;
   • or use the WAI-ARIA aria-live="polite" attribute if the intention is to report the equivalent of a "log" role;
   • or use the WAI-ARIA aria-live="polite" and aria-atomic="true" attributes if the intention is to signal the equivalent of a "status" role.
6. If this is the case, the test is validated.

Tests identical to 7.5.1

Tests identical to 7.5.1

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 in the document all the semantic elements used for presentation purposes
2. For each of these elements, check that
   • The element has a role="presentation" attribute.
   • The use of this element for presentation purposes remains justified.
3. If this is the case, the test is validated.

Note: Here are a few non-exhaustive examples of markup misuse: a <div> element used as a paragraph, a heading used as a legend, a <blockquote> element or empty paragraphs or even spaces used to create margin effects. The use of a role="presentation" is formally discouraged, but may be justified in rare cases. This may be acceptable on a <blockquote> element or an empty paragraph, but will be considered non-compliant on a heading.

Tables: note that this test deals with presentation tables, which should not appear in the Tables theme.

1. Find in the document passages of text that use a language that is read in the opposite direction to the document language (such as Arabic or Hebrew for French, for example).
2. For each passage of text, check that the passage of text is contained in a tag which has a dir attribute.
3. If this is the case for each passage of text, the test is validated.

1. For each passage of text validated in test 8.10.1, check that
   • The reading direction is correct (ltr, for the direction "left to right" and rtl for the direction "right to left")
   • The reading direction is relevant.
2. If this is the case for each passage of text, 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 elements in the document that are visually grouped together in the form of an unordered list.
2. For each list, check that the list is structured
   • either using the elements <ul> and <li>;
   • or using elements with WAI-ARIA attributes role="list" and role="listitem".
3. If this is the case for each unordered list, the test is validated.

1. Find elements in the document that are visually grouped together in the form of an ordered list.
2. For each list, check that the list is structured
   • either using the elements <ol> and <li>;
   • or using elements with WAI-ARIA attributes role="list" and role="listitem".
3. If this is the case for each ordered list, the test is validated.

1. Find the elements in the document that are visually grouped together in the form of a description list.
2. For each list, check that the list is implemented using the elements <dl>, <dt> and <dd>.
3. If this is the case for each description list, the test is validated.

1. Find the short (or inline) quotations in the document.
2. For each quotation, check that the quotation is implemented using a <q> element.
3. If this is the case for each short quotation, the test is validated.

1. Find the quotation blocks in the document.
2. For each quotation block, check that the quotation block is implemented using a <blockquote> element.
3. If this is the case for each quotation block, the test is validated.

1. Check that the <basefont>, <big>, <blink>, <center>, <font>, <marquee>, <s>, <strike>, <tt> presentation elements are not present.
2. Check for the absence of the <u> element only if the DOCTYPE of the document does not correspond to HTML 5.
3. If this is the case, the test is validated.

1. Check that these presentation attributes are not present: align, alink, background, bgcolor, border, cellpadding, cellspacing, char, charoff, clear, color, compact, frameborder, hspace, link, marginheight, marginwidth, text, valign, vlink, vspace, size (with the exception of the <select> element), width (with the exception of the <img>, <object>, <embed>, <canvas> and <svg> elements), height (with the exception of the <img>, <object>, <embed>, <canvas> and <svg> elements).
2. If this is the case, the test is validated.

1. Disable styles (CSS) in the document.
2. Check that no spaces are used:
   • between the letters of a word;
   • to create margin or alignment effects;
   • to simulate tables or columns.
3. If this is the case, the test is validated.

1. Deactivate the styles (CSS) in the document.
2. Compare the unstyled document with the formatted document.
3. Check whether the visible content carrying information is still present in the unstyled document.
4. If this is the case, the test is validated.

1. Deactivate the styles (CSS) in the document.
2. Check that the order in which the content is implemented does not raise understanding issues.
3. If this is the case, the test is validated.

1. Check in the document whether the text remains present and legible when
   • The browser's text zoom is set to 200%.
   • The browser's graphical zoom is set to 200%.
   • The personalised zoom functions offered by the document are used.
2. If this is the case, the test is validated.

1. Check in the document whether the text is actually enlarged when
   • The browser's text zoom is set to 200%.
   • The browser's graphical zoom is set to 200%.
   • The personalised zoom functions offered by the document are used.
2. If this is the case, the test is validated.

1. Find coloured text in the document, with the exception of default colours (e.g. links, etc.).
2. Identify the element containing the text and check that there is a calculated value for the element's background-color property.
3. If this is the case, the test is validated.

1. Find coloured text in the document, with the exception of default colours (e.g. links, etc.).
2. Identify the element containing the text and check that there is a calculated value for the element's color property.
3. If this is the case, the test is validated.

1. Find text in the document whose background is an image (background-image property).
2. Identify the element containing the text and check that if the background image is missing, the text is still legible.
3. If this is the case, the test is validated.

1. Find in the document link type elements (<a> element or element with a WAI-ARIA role="link" attribute).
2. For each link element, if it can be confused with normal text when indicated by colour alone, check that the contrast between the font colour of the link and the font colour of the surrounding text is at least 3:1.
3. This check must be carried out for the different states of the link if they are presented using a different colour: the unvisited state, the visited state, the activated state, the hover state and the state when focused.
4. If this is the case for each element of the link type, 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.