How to use the RGAA

The RGAA applies to any HTML content (HTML4, XHTML1, HTML5). For some tests, a reference baseline is used. This baseline takes into account a set of assistive technologies, browsers and operating systems, on which the accessibility of JavaScript-based interface components must be tested, among others. A detailed description is provided here: Baseline.

Important notice regarding HTML content prior to HTML5 specification

When the HTML code of the page is not HTML5, the HTML5 elements (tags and attributes) required by a criterion or test, are not applicable. Every other criteria or tests remain applicable, including those related to ARIA attributes, states or properties. The following criteria and tests are not applicable:

Validation process

For each criterion, compliance is defined as follows:

The RGAA proposes two additional compliance statuses:

Images

WCAG principle: perceivable.

General guidelines

Give each image conveying information a relevant text alternative and a detailed description if necessary. Replace images of text with styled text when possible.

Criterion 1.1 [A] Does each image have a text alternative?

  • Test 1.1.1: Does each image (img tag) have an alt attribute?
  • Test 1.1.2: Does each area (area tag) of an image map have an alt attribute?
  • Test 1.1.3: Does each form button (input tag with the type="image" attribute) have an alt attribute?
  • Test 1.1.4: Does each area (area tag) of a server-side image map have an equivalent link in the page?

Criterion 1.2 [A] For each decorative image with a text alternative, is this alternative empty?

  • Test 1.2.1: Does each decorative image (img tag), without caption and with an alt attribute, meet the following conditions:
    • The alt attribute has an empty value (alt="")
    • The decorative image does not have a title attribute
  • Test 1.2.2: Does each non clickable area (area tag with no href attribute), not conveying any information, and with an alt attribute, meet the following conditions:
    • The alt attribute has an empty value (alt="")
    • The non clickable area does not have a title attribute
  • Test 1.2.3: For each image object without caption (object tag with the attribute type="image/…"), not conveying any information, is the text alternative between <object> and </object> empty?
  • Test 1.2.4: Does each decorative vector image (svg tag), not conveying any information, and with an alternative, meet the following conditions:
    • The svg tag has a role="img"
    • The svg tag, or one of its children, has no ARIA role, property or state, that aims at labeling the vector image (aria-label, aria-describedby, or aria-labelledby, for example)
    • The title and desc tags are missing, or empty
    • The svg tag, or one of its children, has no title attribute
  • Test 1.2.5: For each decorative bitmap image (canvas tag), there must be no text content between <canvas> and </canvas>. Has this rule been followed?

Technical note: read the technical note about the presentation role.

Criterion 1.3 [A] For each image conveying information with a text alternative, is this alternative relevant (except in particular cases)?

  • Test 1.3.1: Does each image (img tag) conveying information, with an alt attribute, meet the following conditions (except in particular cases):
    • The alt attribute has a relevant value
    • If present, the value of the title attribute matches the value of the alt attribute
  • Test 1.3.2: Does each area (area tag), conveying information, and with an alt attribute, meet the following conditions (except in particular cases):
    • The alt attribute has a relevant value
    • If present, the value of the title attribute matches the value of the alt attribute
  • Test 1.3.3: For each button associated with an image (input tag with the attribute type="image"), and with an alt attribute, is the content of this attribute relevant (except in particular cases)?
  • Test 1.3.4: Does each image object (object tag with the attribute type="image/…"), conveying information, meet one of the following conditions (except in particular cases)?
    • The image object is immediately followed by an adjacent link giving access to a page or a chunk of text containing a relevant alternative
    • The user can replace the image object by a relevant text alternative, via a provided mechanism
    • The user can replace the image object by an image with a relevant alternative, via a provided mechanism
  • Test 1.3.5: Does each embedded image (embed tag with the attribute type="image/…"), conveying information, meet one of the following conditions (except in particular cases)?
    • The embedded image is immediately followed by an adjacent link giving access to a page or a chunk of text containing a relevant alternative
    • The user can replace the embedded image by a relevant text alternative, via a provided mechanism
    • The user can replace the embedded image by an image with a relevant alternative, via a provided mechanism
  • Test 1.3.6: Does each vector image (svg tag), conveying information, and with an alternative, meet one of the following conditions (except in particular cases):
    • The svg tag has a role="img" 
    • The svg tag has an aria-label property with a relevant value, matching the title attribute of the svg tag, if present
    • The svg tag has a desc tag with a relevant content, equal to the title attribute of the svg tag, if present
    • An adjacent link gives access to an alternative with relevant content, equal to the title attribute of the svg tag, if present
  • Test 1.3.7: For each vector image (svg tag), conveying information, and with an alternative, is this alternative correctly rendered by assistive technologies?
  • Test 1.3.8: For each bitmap image (canvas tag), conveying information, and with an alternative (content between <canvas> and </canvas>), is this alternative correctly rendered by assistive technologies?
  • Test 1.3.9: For each bitmap image (canvas tag), conveying information, and with an alternative (content between <canvas> and </canvas>), is this alternative relevant?
  • Test 1.3.10: For each image conveying information and with a text alternative, is the text alternative short and concise (except in particular cases)?

Technical note: read the technical note about the vector images.

Criterion 1.4 [A] For each image used as CAPTCHA or as test image, with a text alternative, does this alternative describe the nature and the purpose of the image?

  • Test 1.4.1: Does each image (img tag) used as a CAPTCHA or test image, with an alt attribute, meet the following conditions?
    • The content of the alt attribute describes the nature and purpose of the image
    • If present, the value of the title attribute matches the value of the alt attribute
  • Test 1.4.2: Does each area (area tag) of an image map used as a CAPTCHA or test image, with an alt attribute, meet the following conditions?
    • The content of the alt attribute describes the nature and purpose of the image
    • If present, the value of the title attribute matches the value of the alt attribute
  • Test 1.4.3: For each button associated with an image (input tag with the attribute type="image"), used as a CAPTCHA or test image, with an alt attribute, meet the following conditions?
    • The content of the alt attribute describes the nature and purpose of the image
    • If present, the value of the title attribute matches the value of the alt attribute
  • Test 1.4.4: For each image object (object tag with the attribute type="image/…"), used as a CAPTCHA or test image, with a text alternative, does the text alternative describe the nature and purpose of the image?
  • Test 1.4.5: For each embedded image (embed tag with the attribute type="image/…"), used as a CAPTCHA or test image, with a text alternative, does the text alternative describe the nature and purpose of the image?
  • Test 1.4.6: Does each vector image (svg tag), used as a CAPTCHA or test image, with a text alternative provided via the aria-label property or the desc tag, meet the following conditions?
    • The text alternative provided via the aria-label property describes the nature and purpose of the image, and matches the value of the title attribute of the svg tag, if present
    • The text alternative provided via the desc tag describes the nature and purpose of the image, and matches the value of the title attribute of the svg tag, if present
  • Test 1.4.7: For each vector image (svg tag), used as a CAPTCHA or test image, with a text alternative, is this alternative correctly rendered by assistive technologies?
  • Test 1.4.8: For each bitmap image (canvas tag), used as a CAPTCHA or test image, with a text alternative, does this alternative describe the nature and purpose of the image?
  • Test 1.4.9: For each bitmap image (canvas tag), used as a CAPTCHA or test image, with a text alternative, is this alternative correctly rendered by assistive technologies?

Criterion 1.5 [A] For each image used as CAPTCHA, is a solution for alternative access to the content or to the purpose of the CAPTCHA available?

  • Test 1.5.1: Does each image (img, area, object, embed, svg, canvas tags) used as CAPTCHA meet one of the following conditions?
    • Another non graphic form of CAPTCHA is available, at least
    • Another solution to access the functionality protected by the CAPTCHA is available
  • Test 1.5.2: Does each button associated with an image (input tag with the attribute type="image") used as CAPTCHA meet one of the following conditions?
    • Another non graphic form of CAPTCHA is available, at least
    • Another solution to access the functionality protected by the CAPTCHA is available

Criterion 1.6 [A] Does each image conveying information have a detailed description if necessary?

  • Test 1.6.1: Does each image conveying information (img tag) needing a detailed description, meet one of the following conditions?
  • Test 1.6.2: Does each image object (object tag with an attribute type="image/…") conveying information needing a detailed description, meet one of the following conditions?
  • Test 1.6.3: Does each embedded image (embed tag with an attribute type="image/…") conveying information needing a detailed description, meet one of the following conditions?
  • Test 1.6.4: Does each image button (input tag with the attribute type="image"), needing a detailed description, meet one of the following conditions?
  • Test 1.6.5: Does each vector image (svg tag) conveying information needing a detailed description, meet one of the following conditions?
    • There is an aria-label property referencing a detailed description adjacent to the vector image
    • There is a desc tag containing a reference to a detailed description adjacent to the vector image
    • There is a desc tag containing a detailed description
    • There is an adjacent link (URL or anchor) giving access to the detailed description
  • Test 1.6.6: For each vector image (svg tag), with a reference to a detailed description provided via an aria-label property or a desc tag, is this reference correctly rendered by assistive technologies?
  • Test 1.6.7: Does each bitmap image (canvas tag) conveying information needing a detailed description, meet one of the following conditions?
    • There is a chunk of text between <canvas> and </canvas> referencing a detailed description adjacent to the bitmap image
    • There is a text content between <canvas> and </canvas> serving as a detailed description
    • There is an adjacent link (URL or anchor) giving access to the detailed description
  • Test 1.6.8: For each bitmap image (canvas tag), with a reference to an adjacent detailed description, is this reference correctly rendered by assistive technologies?

Technical note: read the technical note about vector images and the use of the aria-describedby property.

Criterion 1.7 [A] For each image conveying information with a detailed description, is this description relevant?

  • Test 1.7.1: Does each image conveying information (img or input tag with the attribute  type="image") with a detailed description meet one of the following conditions?
  • Test 1.7.2: Does each image object (object tag with the attribute  type="image/…") with a detailed description meet one of the following conditions?
  • Test 1.7.3: Does each embedded image (embed tag with the attribute  type="image/…") with a detailed description meet one of the following conditions?
    • The detailed description adjacent to the embedded image is relevant
    • The detailed description available via an adjacent link is relevant
  • Test 1.7.4: Does each vector image (svg tag) with a detailed description meet one of the following conditions?
    • The detailed description adjacent to the vector image is relevant
    • The detailed description available via an adjacent link is relevant
  • Test 1.7.5: For each vector image (svg tag) with a detailed description, is this detailed description correctly rendered by assistive technologies?
  • Test 1.7.6: Does each bitmap image (canvas tag) with a detailed description meet one of the following conditions?    
    • The detailed description adjacent to the bitmap image is relevant
    • The detailed description available between <canvas> and </canvas> is relevant
    • The detailed description available via an adjacent link is relevant
  • Test 1.7.7: For each bitmap image (canvas tag) with a detailed description between <canvas> and </canvas>, is this detailed description correctly rendered by assistive technologies?

Criterion 1.8 [AA] When an alternate mechanism is missing, each image of text conveying information must be replaced with styled text, if possible. Has this rule been followed (except in particular cases)?

Criterion 1.9 [AAA] Each image of text conveying information must be replaced with styled text. Has this rule been followed (except in particular cases)?

  • Test 1.9.1: Each image of text (img tag) must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
  • Test 1.9.2: For each image map (img or object tag with the usemap attribute), each text area (area tag) must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
  • Test 1.9.3: For each form tag, each button "image of text" (input tag with the attribute type="image") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
  • Test 1.9.4: Each text image object (object tag with the attribute type="image/…") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
  • Test 1.9.5: Each embedded image of text (embed tag with the attribute type="image/…") must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?
  • Test 1.9.6: Each bitmap image of text (canvas tag) must be replaced with styled text if possible. Has this rule been followed (except in particular cases)?

Criterion 1.10 [A] Is each image caption correctly associated with the corresponding image, if necessary?

  • Test 1.10.1: Does each image with a caption (img tag or input tag with the attribute type="image", associated with an adjacent caption) meet, if necessary, the following conditions?
    • The image (img tag) and its caption are contained in a figure tag
    • The figure tag has an attribute role="group"
    • The content of the alt attribute contains a reference to the adjacent caption
    • The value of the title attribute of the image, if present, is strictly equal to the value of the alt attribute
  • Test 1.10.2: Does each image object with a caption (object tag with the attribute type="image/…", associated with an adjacent caption) meet, if necessary, the following conditions?
    • The image (object tag) and its caption are contained in a figure tag
    • The figure tag has an attribute role="group"
  • Test 1.10.3: Does each embedded image with a caption (embed tag with the attribute type="image/…", associated with an adjacent caption) meet, if necessary, the following conditions?
    • The embedded image (embed tag) and its caption are contained in a figure tag
    • The figure tag has an attribute role="group"
    • The content of the alt attribute contains a reference to the adjacent caption
    • The value of the title attribute of the image, if present, is strictly equal to the value of the alt attribute
  • Test 1.10.4: Does each vector image with a caption (svg tag associated with an adjacent caption) meet, if necessary, the following conditions?
    • The vector image (svg tag) and its caption are contained in a figure tag
    • The figure tag has an attribute role="group"
    • The content of the aria-label property or the desc tag of the vector image contains a reference to the adjacent caption
    • The value of the title attribute of the vector image (svg tag), if present, is strictly equal to the content of the aria-label property or the desc tag used as an alternative
  • Test 1.10.5: Does each bitmap image with a caption (canvas tag associated with an adjacent caption) meet, if necessary, the following conditions?
    • The bitmap image (canvas tag) and its caption are contained in a figure tag
    • The figure tag has an attribute role="group"
    • The content between <canvas> and </canvas> contains a reference to the adjacent caption

Technical note: read the technical note about captioned images.

Frames

WCAG principle: robust.

General guidelines

Provide each iframe with a relevant title.

Criterion 2.1 [A] Does each iframe have a frame title?

  • Test 2.1.1: Does each iframe (iframe tag) have a title attribute?

Criterion 2.2 [A] For each iframe with a frame title, is this frame title relevant?

  • Test 2.2.1: For each iframe (iframe tag) with a title attribute, is the content of this attribute relevant?

Colors

WCAG principle: perceivable.

General guidelines

Do not provide information through color only, and use sufficient color contrasts.

Criterion 3.1 [A] On each Web page, information must not  be conveyed only through color. Has this rule been followed?

  • Test 3.1.1: For each word or for each group of words where color is used to convey information, information must not be conveyed only through color. Has this rule been followed?
  • Test 3.1.2: For each color indication provided by a text, information must not be conveyed only through color. Has this rule been followed?
  • Test 3.1.3: For each image conveying information, information must not be conveyed only through color. Has this rule been followed?
  • Test 3.1.4: For each CSS property defining a color and conveying information, information must not be conveyed only through color. Has this rule been followed?
  • Test 3.1.5: For each time-based media conveying information, information must not be conveyed only through color. Has this rule been followed?
  • Test 3.1.6: For each non-time-based media conveying information, information must not be conveyed only through color. Has this rule been followed?

Criterion 3.2 [A] On each Web page, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?

  • Test 3.2.1: For each word or a group of words, whose color conveys information, information must not be conveyed only through color. Has this rule been implemented in a relevant way?
  • Test 3.2.2: For each information conveyed through color and specified by a word or a group of words, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?
  • Test 3.2.3: For each image conveying information, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?
  • Test 3.2.4: For each CSS element background property conveying information, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?
  • Test 3.2.5: For each time-based media conveying information, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?
  • Test 3.2.6: For each non time-based media conveying information, information  must not be conveyed only through color. Has this rule been implemented in a relevant way?

Criterion 3.3 [AA] On each Web page, is the contrast between the text and background colors sufficient (except in particular cases)?

  • Test 3.3.1: On each Web page, do non-bold texts and images of non-bold text with font sizes smaller than or equal to 150% of the default font size (or 1.5em)  meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 4.5:1
    • The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
  • Test 3.3.2: On each Web page, do bold texts and images of bold text with font sizes smaller than or equal to 120% of the default font size (or 1.2em) meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 4.5:1
    • The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
  • Test 3.3.3: On each Web page, do non-bold texts and images of non-bold text with font sizes larger than 150% of the default font size (or 1.5em), meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 3:1
    • The user can display the text with a contrast ratio of at least 3:1, via a provided mechanism
  • Test 3.3.4: On each Web page, do bold texts and images of bold text with font sizes larger than 120% of the default font size (or 1.2em), meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 3:1
    • The user can display the text with a contrast ratio of at least 3:1, via a provided mechanism

Criterion 3.4 [AAA] On each Web page, is the contrast between the text and background colors enhanced (except in particular cases)?

  • Test 3.4.1: On each Web page, do non-bold texts and images of non-bold text with font sizes smaller than or equal to 150% of the default font size (or 1.5em) meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 7:1
    • The user can display the text with a contrast ratio of at least 7:1, via a provided mechanism
  • Test 3.4.2: On each Web page, do bold texts and images of bold text with font sizes smaller than or equal to 120% of the default font size (or 1.2em) meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 7:1
    • The user can display the text with a contrast ratio of at least 7:1, via a provided mechanism
  • Test 3.4.3: On each Web page, do non-bold texts and images of non-bold text with font sizes larger than 150% of the default font size (or 1.5em), meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 4.5:1
    • The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism
  • Test 3.4.4: On each Web page, do bold texts and images of bold text with font sizes larger than 120% of the default font size (or 1.2em), meet one of the following conditions (except in particular cases)?
    • The contrast ratio between text and its background is at least 4.5:1
    • The user can display the text with a contrast ratio of at least 4.5:1, via a provided mechanism

Multimedia

General guidelines

If necessary, provide each time-based media with relevant text transcript, synchronized captions and a synchronized audio description. Provide each non time-based media with a relevant text alternative. Make possible the playing control of each time-based and non time-based media with the keyboard and ensure that they are compatible with assistive technologies.

Criterion 4.1 [A] Does each prerecorded time-based media have a text transcript or an audio description if necessary (except in particular cases)?

Criterion 4.2 [A] For each prerecorded time-based media with a text transcript or a synchronized audio description, are these relevant (except in particular cases)?

Criterion 4.3 [A] Does each prerecorded synchronized time-based media have synchronized captions if necessary (except in particular cases)?

Criterion 4.4 [A] For each prerecorded synchronized time-based media with synchronized captions, are these captions relevant?

Criterion 4.5 [AA] Does each live time-based media have synchronized captions or a text transcript if necessary (except in particular cases)?

Criterion 4.6 [AA] Are each synchronized captions or text transcript, provided for live time-based media, relevant?

Criterion 4.7 [AA] Does each prerecorded time-based media have a synchronized audio description if necessary (except in particular cases)?

Criterion 4.8 [AA] For each prerecorded time-based media with a synchronized audio description, is this audio description relevant?

Criterion 4.9 [AAA] Does each prerecorded time-based media have a sign language interpretation (except in particular cases) if necessary?

  • Test 4.9.1: Does each prerecorded audio-only time-based media have a sign language interpretation if necessary, that is adapted to the media language (except in particular cases)?
  • Test 4.9.2: Does each prerecorded synchronized time-based media have a sign language interpretation, if necessary, that is adapted to the media language (except in particular cases)?

Criterion 4.10 [AAA] For each prerecorded time-based media with a sign language interpretation is this interpretation relevant?

  • Test 4.10.1: For each prerecorded audio-only time-based media with a sign language interpretation, is this interpretation relevant?
  • Test 4.10.2: For each prerecorded synchronized time-based media with a sign language interpretation, is this interpretation relevant?

Criterion 4.11 [AAA] Does each prerecorded time-based media have a synchronized extended audio description if necessary (except in particular cases)?

Criterion 4.12 [AAA] For each prerecorded time-based media with a synchronized extended audio description, is this audio description relevant?

Criterion 4.13 [AAA] Does each synchronized or video-only time-based media have a text transcript (except in particular cases)?

Criterion 4.14 [AAA] For each synchronized or video-only time-based media with a text transcript, is this text transcript relevant?

Criterion 4.15 [A] Can each time-based media be clearly identified (except in particular cases)?

  • Test 4.15.1: For each audio-only, video-only or synchronized time-based media , does the adjacent textual content help to clearly identify the time-based media (except in particular cases)?
  • Test 4.15.2: For each live audio-only, live video-only or live synchronized time-based media, does the adjacent textual content help to clearly identify the time-based media (except in particular cases)?

Criterion 4.16 [A] Does each non time-based media have, if necessary, an alternative (except in particular cases)?

Criterion 4.17 [A] For each non time-based media with an alternative, is this alternative relevant?

  • Test 4.17.1: For each non time-based media with an alternative, does this alternative provide access to the same content, and to similar functionalities?

Criterion 4.18 [A] Can each autoplaying sound be controlled by the user?

  • Test 4.18.1: Does each audio sequence played automatically via an object, video, audio, embed tag, a JavaScript code or bgsound property meet one of the following conditions?
    • The audio sequence lasts 3 seconds or less
    • The audio sequence can be stopped by an action initiated by the user
    • The volume of the audio sequence can be controlled by the user independently from the system volume control.

Criterion 4.19 [AAA] For each prerecorded audio-only time-based media, are the dialogues audible enough (except in particular cases)?

  • Test 4.19.1: Does each prerecorded audio time-based media, played via an object, video, audio, embed tag, or provided for download, meet one of the following conditions (except in particular cases)?
    • The background sounds can be turned off
    • The volume of the dialogue track(s) is 20 decibels higher than the volume of the background sounds.
    • An alternative version, for which the background sounds can be turned off, is available
    • An alternative version in which the volume of the dialogue track(s) is 20 decibels higher than the volume of the background sounds, is available.

Criterion 4.20 [A] Can each time-based media be, if necessary, controlled by keyboard and mouse?

  • Test 4.20.1: Does each time-based media have the control features to be played, if necessary?
  • Test 4.20.2: For each time-based media, does each control feature meet one of the following conditions:
    •     The control feature can be reached by the keyboard and by the mouse?
    •     A keyboard and mouse accessible control feature, performing the same action, is available in the same page
  • Test 4.20.3: For each time-based media, does each control feature meet one of the following conditions:
    •     The control feature can be activated by the keyboard and by the mouse?
    •     A control feature, performing the same action, and that can be activated by the keyboard and by the mouse, is available in the same page

Criterion 4.21 [A] Can each non time-based media be controlled by the keyboard and by the mouse?

  • Test 4.21.1: For each non time-based media, does each control feature meet one of the following conditions:
    •     The control feature can be reached by the keyboard and by the mouse?
    •     A keyboard and mouse accessible control feature, performing the same action, is available in the same page
  • Test 4.21.2: For each non time-based media, does each control feature meet one of the following conditions:
    •     The control feature can be activated by the keyboard and by the mouse?
    •     A control feature, performing the same action, and that can be activated by the keyboard and by the mouse, is available in the same page

Criterion 4.22 [A] Is each time-based media and each non time-based media compatible with assistive technologies (except in particular cases)?

  • Test 4.22.1: Does each time-based media and each non time-based media, inserted via an object or embed tag, meet one of the following conditions (except in particular cases)?
  • Test 4.22.2: Does each time-based media and each non time-based media, inserted via an object or embed tag, with an alternative compatible with an accessibility API, meet one of the following conditions?
    • The alternative is adjacent to the time-based media, or the non time-based media
    • The alternative can be reached via an adjacent link (a URL or an anchor)
    • A functionality is available to replace the time-based or non time-based media by its alternative

Tables

WCAG principle: perceivable.

General guidelines

Provide each complex data table, with a relevant summary and a title, clearly identify header cells, use a relevant mechanism to associate data cells with header cells. Ensure that each layout table is correctly linearized.

Criterion 5.1 [A] Does each complex data table have a summary?

  • Test 5.1.1: Does each complex data table (table tag) have a summary, provided through the caption tag?

Criterion 5.2 [A] For each complex data table with a summary, is this summary relevant?

  • Test 5.2.1: For each complex data table (table tag) with a summary, is this summary relevant?

Criterion 5.3 [A] For each layout table, is the linearized content still understandable?

  • Test 5.3.1: Does each layout table meet the following conditions?
    • the linearized content is still understandable
    • the table tag has an attribute role="presentation"

Criterion 5.4 [A] Does each data table have a title?

  • Test 5.4.1: Does each data table (table tag) have a caption tag?

Criterion 5.5 [A] For each data table with a title, is this title relevant?

  • Test 5.5.1: For each data table (table tag) with a caption tag, does the content of this tag provide the title of the table?

Criterion 5.6 [A] For each data table, are each column header and each row header correctly identified?

Criterion 5.7 [A] For each data table, is each cell associated with its header using the appropriate technique?

  • Test 5.7.1: Does each header cell (th tag) applied to the whole row or to the whole column have a unique id attribute or a scope attribute?
  • Test 5.7.2: Does each header cell (th tag) applied to the whole row or the whole column and having a scope attribute meet one of the following conditions?
    • The header has a scope attribute with the value "row" for row headers
    • The header has a scope attribute with the value "col" for column headers
  • Test 5.7.3: Does each header cell (th tag) that is not applied to the whole column meet the following conditions?
    • The header does not have a scope attribute
    • The header has a unique id attribute
  • Test 5.7.4: Does each cell (td or th tag) associated with one or several headers with an id attribute meet the following conditions?
    • The cell has a headers attribute
    • The headers attribute contains a list of values matching the id attributes of the headers associated with the cell.

Criterion 5.8 [A] Each layout table must not use elements intended for data tables. Has this rule been followed?

  • Test 5.8.1: Does each layout table (table tag) meet the following conditions?
    • The layout table (table tag) does not have any caption, th, thead, tfoot tags
    • The cells of the layout table (td tag) have no scope, headers, colgroup, axis attributes.

Links

WCAG principle: perceivable, operable, understandable.

General guidelines

Provide explicit link text, in particular, with context information, and use the link title as sparsely as possible. Add links or a navigation form to the areas of a server-side image map.

Criterion 6.1 [A] Is each link explicit (except in particular cases)?

  • Test 6.1.1: Does each link context meet one of the following conditions (except in particular cases)?
    • The link text alone is sufficient to understand the link purpose and target
    • The link context is sufficient to understand the link purpose and target
  • Test 6.1.2: Does each image link (content of the alt attribute, text between <canvas> and </canvas>, or text between <object> and </object>) meet one of the following conditions (except in particular cases)?
    • The link text alone is sufficient to understand the link purpose and target
    • The link context is sufficient to understand the link purpose and target
  • Test 6.1.3: Does each link that doubles a clickable area of a server-side image map meet one of the following conditions (except in particular cases)?
    • The link text alone is sufficient to understand the link purpose and target
    • The link context is sufficient to understand the link purpose and target
  • Test 6.1.4: Does each combined link meet one of the following conditions (except in particular cases)?
    • The link text alone is sufficient to understand the link purpose and target
    • The link context is sufficient to understand the link purpose and target
  • Test 6.1.5: Does each  vector link meet one of the following conditions (except in particular cases)?
    • The link text alone is sufficient to understand the link purpose and target
    • The link context is sufficient to understand the link purpose and target

Criterion 6.2 [A] For each link with a link title, is this title relevant?

  • Test 6.2.1: For each text link with a link title (title attribute), is the content of this attribute relevant?
  • Test 6.2.2: For each image link with a link title (title attribute), is the content of this attribute relevant?
  • Test 6.2.3: For each clickable area (area tag) with a link title (title attribute), is the content of this attribute relevant?
  • Test 6.2.4: For each combined link with a link title (title attribute), is the content of this attribute relevant?
  • Test 6.2.5: For each  vector link with a link title (title attribute), is the content of this attribute relevant?

Criterion 6.3 [AAA] Is each link text alone explicit out of context (except in particular cases)?

Criterion 6.4 [A] For each web page, does each identical link have the same purpose and target?

  • Test 6.4.1: For each web page, does each identical link of type text have the same purpose and target?
  • Test 6.4.2: For each web page, does each identical link of type image have the same purpose and target?
  • Test 6.4.3: For each web page, does each identical link of type clickable area have the same purpose and target?
  • Test 6.4.4: For each web page, does each identical link of type combined link have the same purpose and target?
  • Test 6.4.5:For each web page, does each identical link that are vector links have the same purpose and target?

Criterion 6.5 [A] On each Web page, does each link, except in anchors, have a text?

  • Test 6.5.1: On each Web page, does each link (a tag with an href attribute), except in anchors, have a text between <a> and </a>?

Scripts

General guidelines

Provide, if necessary, each script with a relevant alternative. Make each script controllable at least by keyboard and mouse, and ensure that it is compatible with assistive technologies.

Criterion 7.1 [A] Does each script support assistive technologies, if necessary?

  • Test 7.1.1: Does each script generating or controlling an interface component meet one of the following conditions, if necessary?
  • Test 7.1.2: Does each functionality for content insertion controlled by a script, use properties and methods compliant with the DOM (Document Object Model) specification?
  • Test 7.1.3: Does each script generating or controlling an interface component, having roles, states or properties matching with an ARIA API Design Pattern, meet one of the following conditions?
    • The interface component complies with the Design Pattern defined by the ARIA API
    • An interface component, available in the page, providing access to the same functionalities, complies with the Design Pattern defined by the ARIA API
    • The interface component adapts a Design Pattern defined by the ARIA API
    • An accessible interface component providing access to the same functionalities is available in the page
  • Test 7.1.4: Does each change of native role of an HTML element respect the rules and recommendations of the HTML5 specifications, and the associated technical notes?
  • Test 7.1.5: Does each script generating or controlling an interface component, via roles, states or properties defined by the ARIA API, meet one of the following conditions?
    • The interface component is correctly rendered by assistive technologies
    • An accessible alternative provides access to the same functionalities
  • Test 7.1.6: Does each interface component with an ARIA role application meet one of the following conditions?
    • The interface component is correctly rendered by assistive technologies
    • An accessible alternative provides access to the same functionalities

Technical note: read the technical note about the alternatives to scripts.

Criterion 7.2 [A] For each script with an alternative, is this alternative relevant?

  • Test 7.2.1: Does each script beginning with the script tag, and having an alternative, meet one of the following conditions?
    • The alternative between <noscript> and </noscript> provides access to similar content and functionalities
    • When JavaScript is disabled, the displayed page provides access to similar content and functionalities
    • The alternative page provides access to similar content and functionalities
    • The server-side script language provides access to similar content and functionalities
    • The alternative available in the same page provides access to  similar content and functionalities
  • Test 7.2.2: Does each non text element that is updated by a script (in the page or an iframe) and that has an alternative meet the following conditions?

Criterion 7.3 [A] Can each script be controlled by keyboard and mouse (except in particular cases)?

  • Test 7.3.1: Does each element with an event handler controlled by a script meet one of the following conditions (except in particular cases)?
  • Test 7.3.2: Does each element with an event handler controlled by a script meet one of the following conditions (except in particular cases)?
  • Test 7.3.3: A script must not remove focus from an element that receives it. Has this rule been followed (except in particular cases)?
  • Test 7.3.4: Does each interface component implemented via a role defined by the ARIA API, and matching a Design Pattern, meet one of the following conditions?
    • The keyboard interactions comply with the Design Pattern for the Esc, Space bar, Tab, and arrow keys, at least
    • An interface component available in the page, performing the same action, has keyboard interactions complying with the Design Pattern for the Esc, Space bar, Tab, and arrow keys, at least
    • An alternative providing access to the same functionalities can be controlled by the keyboard and the mouse.

Technical note: read the technical note about keyboard interactions in the ARIA API.

Criterion 7.4 [A] For each script that initiates a change of context, is the user warned or can he control it?

  • Test 7.4.1: Does each script initiating a change of context meet one of the following conditions?
    • The user is warned by a text about the script action and the kind of change before it is activated
    • The change of context is initiated by an explicit button (input tag of type submit, button or image, or button tag)
    • The change of context is initiated by an explicit link

Criterion 7.5 [AAA] Can each script causing an unrequested alert be controlled by the user (except in particular cases)?

Mandatory elements

General guidelines

Check that each Web page has a valid source code according to the document type, a relevant title and a default human language identification. Check that tags are not used for presentation only, that changes in human language and changes in the direction of reading order are specified.

Criterion 8.1 [A] Is each Web page defined by a document type?

  • Test 8.1.1: For each Web page, is the document type (doctype tag) available?
  • Test 8.1.2: For each Web page is the document type (doctype tag) valid?
  • Test 8.1.3: For each Web page with a document type declaration, is this declaration located before the HTML tag in the source code?

Criterion 8.2 [A] For each Web page, is the source code valid according to the specified document type (except in particular cases)?

  • Test 8.2.1: For each document type declaration, does the page source code meet the following conditions (except in particular cases)?
    • Tags follow the writing rules
    • Tag nesting is conform
    • Tag opening and closing are conform
    • Attributes follow the writing rules
    • The attribute values follow the writing rules
  • Test 8.2.2: For each document type declaration, the page source code must not contain obsolete elements. Has this rule been followed (except in particular cases)?

Criterion 8.3 [A] On each Web page, is the default human language identifiable?

  • Test 8.3.1: For each Web page, does the default human language identification meet one of the following conditions?
    • The human language identification (lang and/or xml:lang attribute) for the page is provided via the HTML element
    • The human language identification (lang and/or xml:lang attribute) for the page is provided via each text element or one of the parent elements

Criterion 8.4 [A] For each Web page with a default human language, is the language code appropriate?

Criterion 8.5 [A] Does each Web page have a page title?

  • Test 8.5.1: Does each Web page have a page title (title tag)?

Criterion 8.6 [A] For each Web page with a page title, is this title relevant?

  • Test 8.6.1: For each Web page with a page title (title tag), is the content of this tag relevant?

Criterion 8.7 [AA] On each Web page, is each change in the human language identified via the source code (except in particular cases)?

  • Test 8.7.1: On each Web page, does each text written in a language differing from the default human language meet one of the following conditions (except in particular cases)?
    • The human language identification is provided via the element containing the text
    • The human language identification is provided via one of the parent elements

Criterion 8.8 [AA] On each Web page, is each change in human language relevant?

  • Test 8.8.1: On each Web page, is each change in human language identification (lang and/or xml:lang attribute) technically valid?
  • Test 8.8.2: On each Web page, is each change in human language identification (lang and/or xml:lang attribute) relevant?

Criterion 8.9 [A] On each Web page, tags must not be used only for layout. Has this rule been followed?

  • Test 8.9.1: On each Web page, tags must not be used (except div, span and table) only for layout. Has this rule been followed?

Criterion 8.10 [A] On each Web page, are changes in reading direction identified?

  • Test 8.10.1: On each Web page, does each text for which the reading direction is different from the default reading direction meet the following conditions?
    • the text is contained in an element with a dir attribute
    • The value of the dir attribute is valid (rtl or ltr)
    • The value of the dir attribute is relevant

Information structure

General guidelines

Use headings, landmarks, lists, abbreviations and quotes to structure information.

Criterion 9.1 [A] On each Web page, is information structured by the appropriate use of headings?

  • Test 9.1.1: Is there a level 1 heading (h1 tag or a tag with an ARIA role="heading" associated to an aria-level="1" property) on each Web page?
  • Test 9.1.2: On each Web page, is the hierarchy between the headings (h1 to h6 tags or tags with an ARIA role="heading" associated to an aria-level property) relevant?
  • Test 9.1.3: On each Web page, when a heading (h1 to h6 tag or a tag with an ARIA role="heading" associated to an aria-level property), is necessary to structure information, is this heading available?
  • Test 9.1.4: On each Web page, is each heading (h1 to h6 tag or a tag with an ARIA role="heading" associated to an aria-level property) relevant?

Technical note: read the technical note about the ARIA heading role and h1 headings.

Criterion 9.2 [A] On each Web page, is the document outline coherent?

Technical note: read the technical note about the document outline.

Criterion 9.3 [A] On each Web page, is each list structured  appropriately?

  • Test 9.3.1: On each Web page, does information grouped in an unordered list meet one of the following conditions?
    • the list uses the ul and li tags
    • the list uses the ARIA roles list and listitem
  • Test 9.3.2: On each Web page, does information grouped in ordered lists meet one of the following conditions?
    • the list uses the ol and li tags
    • the list uses the ARIA roles list and listitem
  • Test 9.3.3: On each Web page, does information grouped in definition lists use the dl and dt/dd tags?

Technical note: read the technical note about the list and listitem roles.

Criterion 9.4 [AAA] On each Web page, does the first occurence of each abbreviation help to know its meaning?

  • Test 9.4.1: On each Web page, does the first occurence of each abbreviation meet one of the following conditions?
    • The abbreviation is provided with its meaning as an adjacent link
    • The abbreviation is implemented via a link referring to a page or a location in the page, providing its meaning
    • The abbreviation is included in a link with a title attribute providing its meaning
    • The meaning of the abbreviation is available in a glossary on the website
    • The abbreviation is implemented via an abbr tag with a title attribute providing its meaning

Technical note: read the technical note about the ARIA role definition.

Criterion 9.5 [AAA] On each Web page, is the meaning of each abbreviation relevant?

  • Test 9.5.1: On each Web page, is the meaning of each abbreviation relevant?

Criterion 9.6 [A] On each Web page, is each quotation identified properly?

  • Test 9.6.1: On each Web page, does each short quotation use a q tag?
  • Test 9.6.2: On each Web page, does each long quotation use a blockquote tag?

Presentation of information

General guidelines

Use style sheets to control information presentation. Check for the effect of font size increasing on readability. Ensure that links can be correctly identified, that focus is specified, that line spacing is suffiscient, and give the user the ability to control text justification. Ensure that hidden texts are rendered properly and that information is not conveyed only by an element's shape, size or location.

Criterion 10.1 [A] In the Web site, are style sheets used to control information presentation?

  • Test 10.1.1: On each Web page, tags used for information presentation must not be available in the source code. Has this rule been followed?
  • Test 10.1.2: On each Web page, attributes used for information presentation must not be available in the source code. Has this rule been followed?
  • Test 10.1.3: On each Web page, does the use of white spaces meet the following conditions?
    • White spaces characters are not used to control spacing within a word
    • White spaces characters are not used to format tables in plain text content
    • White spaces characters are not used to create multiple columns in plain text content

Criterion 10.2 [A] On each Web page, is visible content still available when style sheets or images are disabled?

Criterion 10.3 [A] On each Web page, is information still understandable when style sheets are disabled?

Criterion 10.4 [AA] On each Web page, is text still readable when character size is increased until at least 200%?

  • Test 10.4.1: In the style sheets of the website, non relative units (pt, pc, mm, cm, in) must not be used for the media types screen, tv, handheld, projection. Has this rule been followed?
  • Test 10.4.2: In the style sheets of the website, for the media types screen, tv, handheld, projection, do font sizes use relative units only?
  • Test 10.4.3: On each Web page, increasing the character size up to 200% must not cause loss of information. Has this rule been followed?

Criterion 10.5 [AA] On each Web page, are CSS declarations for background and foreground colors appropriate?

  • Test 10.5.1: On each Web page, for each element that may contain text, is the CSS declaration for foreground color accompanied by a background color declaration at least, inherited from a parent element?
  • Test 10.5.2: On each Web page, for each element that may contain text, is the CSS declaration for background color accompanied by a foreground color declaration at least, inherited from a parent element?
  • Test 10.5.3: On each Web page, for each element that may contain text, if an image is used to provide a background color via CSS, is there a corresponding background color declaration, at least, inherited from a parent element?

Criterion 10.6 [A] On each Web page, can each link whose nature is not obvious be distinguished from the surrounding text?

  • Test 10.6.1: On each Web page, does each text link indicated through color alone, and whose nature is not obvious, have a contrast ratio of 3:1 or greater with the surrounding text?

Criterion 10.7 [A] On each Web page, is the focus visible for each element that receives focus?

  • Test 10.7.1: For each element receiving focus, the browser default visual cue must not be removed (CSS property outline, outline-color, outline-width, outline-style). Has this rule been followed?
  • Test 10.7.2: For each element receiving focus, the browser default visual cue must not be degraded (CSS property outline-color). Has this rule been followed?
  • Test 10.7.3: Does each link inside a text, indicated through color alone, meet the conditions below?
    • An additional visual cue, other than color, is provided when the user tabs to the link with the keyboard
    • An additional visual cue, other than color, is provided when the user points to the link (hovers) with the mouse

Criterion 10.8 [AAA] On each Web page, can the user specify the background and foreground colors?

  • Test 10.8.1: For each block of text inside an HTML element, can the background color be specified by the user?
  • Test 10.8.2: For each block of text inside an HTML element, can the foreground color be specified by the user?
  • Test 10.8.3: For each block of text inside an object, embed, svg or canvas tag, can the background color be specified by the user?
  • Test 10.8.4: For each block of text inside an object, embed, svg or canvas tag, can the foreground color be specified by the user?

Criterion 10.9 [AAA] for each Web page, text must not be fully justified. Has this rule been followed?

  • Test 10.9.1: Does each Web page meet one of the following conditions?
    • The text is not fully justified
    • The user can remove the full justification of text, via a provided mechanism

Criterion 10.10 [AAA] For each Web page, on a full-screen window and with a font size of 200%, is each block of text still readable without the use of horizontal scrolling?

  • Test 10.10.1: On each Web page, does increasing the text size up to 200% meet one of the following conditions?
    • In a full-screen window, the use of horizontal scrolling is not required to read a block of text
    • The user can display, via a provided mechanism, a version of the content where the use of horizontal scrolling is not required to read a block of text, in a full-screen window

Criterion 10.11 [AAA] For each Web page, is the length of lines of text equal to 80 characters or less (except in particular cases)?

  • Test 10.11.1: For each Web page, does each line of text meet one of the following conditions (except in particular cases)?
    • The length of each line of text is equal to 80 characters or less
    • The user can reduce the length of each line of text, down to 80 characters or less, when resizing the browser window

Criterion 10.12 [AAA] For each Web page, is line and paragraph spacing sufficient?

  • Test 10.12.1: For each Web page, does each block of text meet one of the following conditions?
    • The line spacing is 1.5 times the text size, or more
    • The user can increase the line spacing to at least 1.5 times the text size, via a provided mechanism
  • Test 10.12.2: For each Web page, does each block of text meet one of the following conditions?
    • The spacing between two paragraphs is 1.5 times the line spacing, or more
    • The user can increase the spacing between two paragraphs to at least 1.5 times the line spacing, via a provided mechanism

Criterion 10.13 [A] For each Web page, are hidden texts rendered properly by assistive technologies?

  • Test 10.13.1: On each Web page, does each hidden text meet one of the following conditions?
    • The text is not intended to be rendered by assistive technologies
    • The text is made visible on user action on the element itself or on an element before the hidden text
    • The hidden text is part of a user interface component ruled by the ARIA API, which manages the displayed or hidden status of the content
  • Test 10.13.2: On each Web page, does each hidden text using an ARIA property aria-hidden meet one of the following conditions?
    • The text is not intended to be rendered by assistive technologies
    • The value of the ARIA property aria-hidden matches the visible or hidden status of the text
  • Test 10.13.3: On each Web page, does each hidden text using the hidden attribute meet one of the following conditions?
    • The text is not intended to be rendered by assistive technologies
    • The text is made visible on user action on the element itself or on an element before the hidden text
    • The hidden text is part of a user interface component ruled by the ARIA API, which manages the displayed or hidden status of the content

Technical note: read the technical note about the aria-hidden property and the hidden attribute.

Criterion 10.14 [A] On each Web page, information must not be conveyed by shape, size or location alone. Has this rule been followed?

Criterion 10.15 [A] On each Web page, information must not be conveyed by shape, size or location alone. Has this rule been implemented in a relevant way?

Forms

General guidelines

For each form, associate each control with its label, group controls in similar blocks of information, structure selection lists in a consistent way, give each button an explicit label. Check that input help is available, ensure that the input control is accessible and that the user can control financial, legal or personal data.

Criterion 11.1 [A] Does each form field have a label?

  • Test 11.1.1: Does each form field meet one of the following conditions?
    • The form field has a title attribute
    • A label (label tag) is associated with the form field
    • The form field has an aria-label property
    • The form field has an aria-labelledby property that references an identified chunk of text
  • Test 11.1.2: Does each form field that is associated with a label (label tag), meet the following conditions?
    • The form field has an id attribute
    • The value of the id attribute is unique
    • The label tag has a for attribute
    • The value of the for attribute matches the value of the corresponding form field id attribute
  • Test 11.1.3: Does each form field associated with a label, via the ARIA aria-labelledby property, meet the following conditions?
    • The label has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA aria-labelledby property matches the value of the label id attribute

Criterion 11.2 [A] Is each label that is associated with a form field relevant?

  • Test 11.2.1: Does each label (label tag) describe the exact function of the associated form field?
  • Test 11.2.2: Does each title attribute describe the exact function of the associated form field?
  • Test 11.2.3: Does each label implemented via the ARIA aria-label property describe the exact function of the associated form field?
  • Test 11.2.4: Does each label implemented via the ARIA aria-labelledby property describe the exact function of the associated form field?

Criterion 11.3 [AA] On a given page, or set of pages, all form fields with similar functions must have consistent labels. Has this rule been followed?

  • Test 11.3.1: On a given page, all form fields with similar functions must have consistent labels. Has this rule been followed?
  • Test 11.3.2: On a given set of pages, all form fields with similar functions must have consistent labels. Has this rule been followed?

Criterion 11.4 [A] In each form, are each label and its related control positioned next to each other?

  • Test 11.4.1: In each form, are each label and its related control positioned next to each other?

Criterion 11.5 [A] In each form, is the information of same nature grouped together, if necessary?

Criterion 11.6 [A] In each form, does each form field grouping have a legend?

  • Test 11.6.1: Is each form field grouping (fieldset tag) followed by a legend (legend tag) in the source code?

Criterion 11.7 [A] In each form, is each legend, related to a form field grouping, relevant?

  • Test 11.7.1: In each form, is each legend (legend tag), related to a form field grouping (fieldset tag), relevant?

Criterion 11.8 [A] In each form, is each selection list structured in a relevant way?

  • Test 11.8.1: In each form, are for each selection list (select tag) items grouped together with an optgroup tag, if necessary?
  • Test 11.8.2: In each selection list (select tag), does each list item grouping (optgroup tag) have a label attribute?
  • Test 11.8.3: For each list item grouping (optgroup tag) with a label attribute, is the content of the label attribute relevant?

Criterion 11.9 [A] In each form, is the text of each button relevant?

  • Test 11.9.1: In each form, does the text of each button meet one of the following conditions?
    • The content of the value attribute of the form buttons of type submit, reset or button is relevant
    • The content of the <button> tag is relevant
    • The content of the title attribute is relevant
    • The content of the ARIA property aria-label is relevant
  • Test 11.9.2: In each form, does the text of each button implemented via an ARIA property aria-labelledby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-labelledby matches the value of the id attribute of the chunk of text
    • The chunk of text is relevant

Criterion 11.10 [A] In each form, is the input control used in a relevant way?

  • Test 11.10.1: For each form, do mandatory fields indications meet one of the following conditions?
    • The mandatory field indication is provided via a chunk of text before the form field
    • The mandatory field indication is provided via a "required" attribute
    • The mandatory field indication is provided via an aria-required ARIA property
    • The mandatory field indication is provided via the label (label tag, or title attribute, or aria-label property, or labelling chunk of text identified via the aria-labelledby property) of the form field
    • The mandatory field indication is provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
  • Test 11.10.2: Each mandatory field indication based on the ARIA properties aria-label, aria-required, or the "required" attribute, must have an explicit visual cue in its label (label tag) or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
  • Test 11.10.3: Does each mandatory field indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute
  • Test 11.10.4: For each form, do the input errors meet one of the following conditions?
    • The input error message is provided via the label (label tag, or title attribute, or aria-label property, or labelling chunk of text identified via the aria-labelledby property) of the form field
    • The input error message is provided via a chunk of text before the form field
    • The form field has a type that automatically generates an input error message
    • The input error message is provided via a chunk of text tied to the form field via the ARIA property aria-describedby
    • The input error is signaled via the ARIA property aria-invalid
  • Test 11.10.5: Each input error indication based on the ARIA properties aria-label or aria-invalid must have an explicit visual cue in the label (label tag) or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
  • Test 11.10.6: Does each input error indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute
  • Test 11.10.7: For each form, does each mandatory field meet one of the following conditions?
    • The data type and/or format is provided, if necessary, via the field label (label tag, or title attribute, or aria-label property, or labelling chunk of text identified via the aria-labelledby property)
    • The data type and/or format is provided, if necessary, via a chunk of text before the form field 
    • The data type and/or format is provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
  • Test 11.10.8: Each data type and/or format indication based on the ARIA properties aria-label must have an explicit visual cue in its label (label tag) or in a chunk of text tied to the form field via the ARIA property aria-describedby or aria-labelledby. Has this rule been followed?
  • Test 11.10.9: Does each data type and/or format indication provided via a chunk of text tied by an ARIA property aria-describedby or aria-labelledby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-describedby or aria-labelledby matches the value of the id attribute

Criterion 11.11 [AA] In each form, is input control accompanied, if necessary, by suggestions helping with the correction of input errors?

  • Test 11.11.1: For each form, for each input error, are each data types and formats suggested, if necessary?
  • Test 11.11.2: For each form, for each input error, are examples for expected values suggested, if necessary?

Technical note: read the technical note about automatic format controls in HTML5.

Criterion 11.12 [AA] For each form, can financial, legal or personal data be changed, updated or retrieved by the user?

  • Test 11.12.1: For each form, do the input of financial, legal or personal data meet one of the following conditions?
    • The user can change or reset the data, and cancel actions made on these data after they have been entered
    • The user can check and modify data before form submission
    • An explicit confirmation mechanism, via a form field or an additional step, is available
  • Test 11.12.2: For each form, does the deletion of financial, legal or personal data meet one of the following conditions?
    • The user can recover data that have been deleted, via a provided mechanism
    • An explicit mechanism confirming deletion, via a form field or an additional step, is available

Criterion 11.13 [AAA] For each form, can all data be changed, updated or recovered by the user?

  • Test 11.13.1: For each form, does data input meet one of the following conditions?
    • The user can change or cancel data and actions on this data after it has been entered
    • The user can check and correct data before form submission
    • An explicit confirmation mechanism, via a form field or an additional step, is available
  • Test 11.13.2: For each form, does data deletion meet one of the following conditions?
    • The user can recover data that have been deleted, via a provided mechanism
    • An explicit mechanism confirming deletion, via a form field or an additional step, is available

Criterion 11.14 [AAA] For each form, is input assistance available?

  • Test 11.14.1: Does each form meet one of the following conditions?
    • There is a link to a help page
    • Indications before the form are available
    • Indications before form fields are available
    • Indications are provided via the form field label (label tag, or title attribute, or aria-label property, or labelling chunk of text identified via the aria-labelledby property)
    • Indications are provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
    • an assistant is available
  • Test 11.14.2: Each indication based on the ARIA property aria-label must have an explicit visual cue. Has this rule been followed?
  • Test 11.14.3: Does each indication provided via a chunk of text tied by an ARIA property aria-describedby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-describedby matches the value of the id attribute
  • Test 11.14.4: Does each field of type text meet one of the following conditions, if necessary?
    • A spell checking tool is available
    • Input suggestions are provided before the form field
    • Input suggestions are provided via the form field label (label tag, or title attribute, or aria-label property, or labelling chunk of text identified via the aria-labelledby property)
    • Input suggestions are provided via a chunk of text, tied to the form field via the aria-describedby ARIA property
  • Test 11.14.5: Each input suggestion based on the ARIA property aria-label must have an explicit visual cue. Has this rule been followed?
  • Test 11.14.6: Does each input suggestion provided via a chunk of text tied by an ARIA property aria-describedby meet the following conditions?
    • The referenced chunk of text has an id attribute
    • The value of the id attribute is unique
    • The value of the ARIA property aria-describedby matches the value of the id attribute

Criterion 11.15 [AAA] For each form, is each input assistance relevant?

  • Test 11.15.1: For each form, is each input assistance relevant?

Consultation

General guidelines

Check that the user can control the refresh processes, sudden changes in luminosity, openings of new windows and moving or blinking content. Specify when a content opens in a new window and provide information regarding viewing of files to download. Do not make the completion of a task rely upon a time limit except if it is essential and ensure that entered data is retrieved after an authenticated session has expired. Ensure that unusual phrases and jargon are made explicit. Provide accessible versions or make downloadable documents accessible.

Criterion 13.1 [A] For each Web page, can the user control each time limit that modifies content (except in particular cases)?

  • Test 13.1.1: For each Web page, does each refresh process or automatic redirection (code, script, object tag, applet tag, meta tag) meet one of the following conditions (except in particular cases)?
    • The user can stop or restart the refresh process
    • The user can increase the time limit between two refresh processes by at least a factor of ten
    • The user is warned about the imminence of the refresh, and has at least 20 seconds to increase the time limit before the next refresh
    • The time limit between two refresh processes is at least twenty hours
  • Test 13.1.2: For each Web page, is each redirection initiated via the meta tag immediate (except in particular cases)?
  • Test 13.1.3: For each Web page, does each redirect process initiated via a script meet one of the following conditions (except in particular cases)?
    • the user can stop or restart the redirect
    • the user can increase the time limit to at least ten times before redirection
    • The user is warned about the imminence of the redirection and has at least twenty seconds to increase the time limit before the next redirection
    • The time limit before the redirection is at least twenty hours
  • Test 13.1.4: For each Web page, does each server-side redirect process meet one of the following conditions (except in particular cases)?
    • The user can stop or restart the redirection
    • The user can increase the time limit before the redirection to at least ten times
    • The user is warned about the imminence of the redirection and has at least twenty seconds to increase the time limit before the next redirection
    • Time limit before redirection is at least twenty hours
  • Test 13.1.5: For each Web page, does each process restricting a session time meet one of the following conditions (except in particular cases)?
    • The user can suppress time limit
    • The user can increase time limit
    • Time limit before the session expires is at least twenty hours.

Criterion 13.2 [A] On each Web page, is the user warned each time a new window opens?

  • Test 13.2.1: On each Web page, for each new window opening launched via a link (target="_blank" attribute) or a JavaScript command, is the user warned?
  • Test 13.2.2: On each Web page, for each window opening launched via an object, applet or embed tag, is the user warned?
  • Test 13.2.3: On each Web page, for each window opening launched via a form control, is the user warned?

Criterion 13.3 [A] On each Web page, the opening of a new window must not happen without user action. Has this rule been followed?

  • Test 13.3.1: On each Web page, the opening of a new window must not be launched without user action. Has this rule been followed?

Criterion 13.4 [AAA] On each Web page, a task must not require a time limit to be completed, except if it occurs in real time or if this time limit is essential. Has this rule been followed?

  • Test 13.4.1: On each Web page, does each task with a time limit meet one of the following conditions?
    • The task occurs in real time
    • The task requires a time limit that is essential for the task to occur successfully

Criterion 13.5 [AAA] On each Web page, when an authenticated session is interrupted, is the data entered by the user retrieved after re-authenticating?

  • Test 13.5.1: On each Web page, when an authenticated session is interrupted, is the data entered by the user retrieved after re-authenticating?

Criterion 13.6 [A] On each Web page, for each file that can be downloaded, is there sufficient information provided  (except in particular cases)?

  • Test 13.6.1: On each Web page, does each file that can be downloaded via a link or a form have information about its format (except in particular cases)?
  • Test 13.6.2: On each Web page, does each file that can be downloaded via a link or a form have information about its weight (except in particular cases)?
  • Test 13.6.3: On each Web page, does each file that can be downloaded via a link or a form have information about its human language if necessary (except in particular cases)?

Criterion 13.7 [A] On each Web page, does each electronic document that can be downloaded have an accessible version if necessary?

Criterion 13.8 [A] For each electronic document with an accessible version, does this version provide the same information?

  • Test 13.8.1: Does each electronic document with an accessible version meet one of the following conditions?
    • The accessibility-supported version provides the same information
    • The alternative version in HTML format is relevant and provides the same information

Criterion 13.9 [AAA] On each Web page, are unusual phrases, idioms or jargon made explicit?

  • Test 13.9.1: On each Web page, does each phrase used in an unusual or restricted way, each idiom or jargon meet one of the following conditions?
    • A definition is available in the context right next to the phrase and is specified by the dfn tag
    • A definition is available via a definition list
    • A definition is available in the page
    • The phrase is contained in a link giving to access to the definition.

Criterion 13.10 [AAA] On each Web page, for each phrase used in an unusual or restricted way, each idiom or jargon with a definition, is this definition relevant?

  • Test 13.10.1: On each Web page, for each phrase used in an unusual or restricted way, idiom or jargon with a definition, does this definition meet one of the following conditions?
    • The content of the associated definition is relevant
    • The content of the dd tag of the definition list is relevant
    • The definition provided by the adjacent context is relevant.

Criterion 13.11 [A] On each Web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) have an alternative?

  • Test 13.11.1: On each Web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) meet one of the following conditions?
    • A title attribute is available
    • A definition is provided by the adjacent context

Criterion 13.12 [A] On each Web page, for each cryptical content (ASCII art, emoticon, cryptical syntax) with an alternative, is this alternative relevant?

  • Test 13.12.1: On each Web page, does each cryptical content (ASCII art, emoticon, cryptical syntax) meet one of the following conditions?
    • the content of the title attribute is relevant
    • the definition provided by the adjacent context is relevant

Criterion 13.13 [AAA] On each Web page, for each word whose meaning cannot be understood without knowing the pronunciation, is this pronunciation specified?

  • Test 13.13.1: On each Web page, does each word whose meaning cannot be understood without knowing the pronunciation, meet one of the following conditions?
    • The phonetic pronunciation is available in the adjacent context
    • The phonetic pronunciation is accessible via a link

Criterion 13.14 [AAA] On each Web page, does each text that requires a reading ability more advanced than the lower secondary education level have an alternative version?

  • Test 13.14.1: On each Web page, does each text that requires a reading ability more advanced than the lower secondary education level (except for proper names and title) meet one of the following conditions?
    • An illustration or graphic symbols adapted to the reading level of the lower secondary education level are available
    • A version in sign language (adapted to the human language of the content) is available
    • A spoken version of the text is available
    • A summary adapted to the reading level of the lower secondary education level is available.

Criterion 13.15 [A] On each Web page, are sudden changes in luminosity or flashing effects used accurately?

  • Test 13.15.1: On each Web page, does each animated image (img tag, svg tag, or object tag) causing a suddent change in luminosity or a flashing effect meet one of the following conditions?
    • The effect's frequency is lower than 3 per second
    • The cumulated area of effects is smaller than or equal to 21,824 pixels
  • Test 13.15.2: On each Web page, does each script causing a sudden change in luminosity or a flashing effect meet one of the following conditions?
    • The effect's frequency is lower than 3 per second
    • The cumulated area of the effects is less than or equal to 21,824 pixels
  • Test 13.15.3: On each Web page, does each CSS layout causing a sudden change in luminosity or a flashing effect meet one of the following conditions?
    • The effect's frequency is lower than 3 per second
    • The cumulated area of the effects is less than or equal to 21,824 pixels

Criterion 13.16 [AAA] On each Web page, do the sudden changes in luminosity or flashing effects have a frequency lower than or equal to 3 per second?

  • Test 13.16.1: On each Web page, does each sudden change in luminosity or a flashing effect caused by an animated image (img tag, svg tag, embed tag, canvas tag, or object tag) have a frequency lower than or equal to 3 per second?
  • Test 13.16.2: On each Web page, does each sudden change in luminosity or a flashing effect caused by a script have a frequency lower than or equal to 3 per second?
  • Test 13.16.3: On each Web page, does each sudden change in luminosity or a flashing effect caused by CSS layout have a frequency lower than or equal to 3 per second?

Criterion 13.17 [A] On each Web page, can each moving or blinking content be controlled by the user?

  • Test 13.17.1: On each Web page, does each moving content that starts moving automatically, meet one of the following conditions?
    • The motion stops within 5 seconds
    • The user can stop and restart the motion
    • The user can display or hide the moving content
    • The user can display the same information without moving content.
  • Test 13.17.2: On each Web page, does each blinking content that starts blinking automatically, meet one of the following conditions?
    • The blinking stops within 5 seconds
    • The user can stop and restart the blinking
    • The user can display and hide the blinking content
    • The user can display the whole information without blinking content.