The RGAA is the French government's General Accessibility Reference for Administrations. It is meant to provide a way to check conformity to WCAG 2.0.
Table of Contents
How to use the RGAA
The RGAA applies to any HTML content (HTML4, XHTML1, HTML5). For some tests, a reference baseline is used. This baseline takes into account a set of assistive technologies, browsers and operating systems, on which the accessibility of JavaScript-based interface components must be tested, among others. A detailed description is provided here: Baseline.
Important notice regarding HTML content prior to HTML5 specification
When the HTML code of the page is not HTML5, the HTML5 elements (tags and attributes) required by a criterion or test, are not applicable. Every other criteria or tests remain applicable, including those related to ARIA attributes, states or properties. The following criteria and tests are not applicable:
Criterion 1.10;
Criterion 9.2;
Test 11.10.1 (condition 2, relative to the HTML5 attribute required).
Validation process
For each criterion, compliance is defined as follows:
Conforming (C): all applicable tests are passed
Non Conforming (NC): at least one applicable test is failed
Not Applicable (NA): there is no content targeted by the criterion.
The RGAA proposes two additional compliance statuses:
Derogated (D): some contents targeted by the criterion will meet compliance by derogation
Not tested (NT): the criterion has not been tested.
You can get further information about the RGAA validation process in the RGAA companion guide: How is RGAA conformance verified?
Test 1.2.1: Does each decorative
image (img tag), without caption and with an
alt attribute, meet the following conditions:
The alt attribute has an empty value (alt="")
The decorative image does not have a title attribute
The img tag does not have any ARIA role, property or state meant to label the image (aria-label, aria-describedby, aria-labelledby, for example).
Test 1.2.2: Does each non clickable area (area tag with no
href attribute), not conveying any information, and with an alt attribute,
meet the following conditions:
The alt attribute has an empty value (alt="")
The non clickable area does not have a title attribute
The area tag does not have any ARIA role, property or state meant to label the image (aria-label, aria-describedby, aria-labelledby, for example).
Test 1.2.3: Does each decorativeimage object (object tag with the attribute type="image/…"), without caption, not conveying any information, meet these conditions:
The object tag has an aria-hidden="true" attribute
The alternative text between <object> and </object> is empty
The object tag or one of its descendants does not have any ARIA role, property or state meant to label the image (aria-label, aria-describedby, aria-labelledby, for example).
Test 1.2.4: Does each decorative vector image (svg tag), without caption, meet the following conditions:
The svg tag as an aria-hidden="true" attribute
The title and desc tags are missing, or empty
The svg tag, or one of its descendants, has no title attribute
The svg tag, or one of its descendants, has no ARIA role, property or state, that aims at labelling the vector image (aria-label, aria-describedby, or
aria-labelledby, for example)
Test 1.2.5: Does each decorative bitmap image (canvas tag), without caption, meet the follwing conditions?
The canvas tag as an aria-hidden="true" attribute
There is no text content between <canvas> and </canvas>
The canvas tag, or one of its descendants, has no ARIA role, property or state, that aims at labelling the vector image (aria-label, aria-describedby, or
aria-labelledby, for example)
Test 1.2.6: Does each decorative embedded image (embed tag with the attribute type="image/…"), without caption, meet these conditions:
The embed tag has an aria-hidden="true" attribute
The embed tag or one of its descendants does not have any ARIA role, property or state meant to label the image (aria-label, aria-describedby, aria-labelledby, for example).
If present, the value of the title attribute
matches the value of the alt attribute
If present, the value of the aria-label property
matches the value of the alt attribute
If present, the content of the chunk of text linked via the aria-labelledby property
matches the value of the alt attribute.
Test 1.3.3: Does each button associated
with an image (input tag with the attribute
type="image"), and with an alt attribute, meet the following conditions (except in particular cases)?
The alt attribute has a relevant value
If present, the value of the title attribute
matches the value of the alt attribute
If present, the value of the aria-label property
matches the value of the alt attribute
If present, the content of the chunk of text linked via the aria-labelledby property
matches the value of the alt attribute.
The image object is immediately followed by an
adjacent link giving access to a page or a chunk
of text containing a relevant alternative
The user can replace the image
object by a relevant text alternative, via a provided mechanism
The user can replace the image
object by an image with a relevant alternative, via a provided mechanism.
Test 1.3.5: Does each image object
(object tag with the attribute type="image/…"),
conveying information, having an aria-label or an aria-labelledby property, or a title attribute, meet one of the following
conditions (except in particular
cases)?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
Test 1.3.6: 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.7: Does each embedded image
(embed tag with the attribute type="image/…"),
conveying information, meet the following
conditions (except in particular
cases)?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
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.
Test 1.3.9: For each vector image (svg tag), conveying information, and with an alternative,
is this alternative correctly rendered by
assistive technologies?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
Test 1.3.12: For each bitmap image (canvas tag),
conveying information, and with an alternative
(content between <canvas> and
</canvas>), is this alternative correctly rendered by assistive technologies?
Criterion 1.4 [A] For each image used as a CAPTCHA
or as a test image, with a text
alternative, does this alternative describe the nature and the purpose of the image?
Test 1.4.1: Does each image (img tag)
used as a CAPTCHA or test image, with an alt attribute, meet the following conditions?
The content of the alt attribute describes the nature and purpose of the image
If present, the value of the title attribute
matches the value of the alt attribute
If present, the value of the aria-label property
matches the value of the alt attribute
If present, the content of the chunk of text linked via the aria-labelledby property
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
If present, the value of the aria-label property
matches the value of the alt attribute
If present, the content of the chunk of text linked via the aria-labelledby property
matches the value of the alt attribute.
Test 1.4.3: For each button associated
with an image (input tag with the attribute
type="image"), used as a CAPTCHA or test image, with an
alt attribute, meet the following conditions?
The content of the alt attribute describes the nature and purpose of the image
If present, the value of the title attribute
matches the value of the alt attribute
If present, the value of the aria-label property
matches the value of the alt attribute
If present, the content of the chunk of text linked via the aria-labelledby property
matches the value of the alt attribute.
Test 1.4.4: Does each image object (object
tag with the attribute type="image/…"), used
as a CAPTCHA or test image, meet one of the following conditions?
The image object is immediately followed by an
adjacent link giving access to a page or a chunk
of text describing the nature and purpose of the image
The user can replace the image
object by a text describing the nature and purpose of the image, via a provided mechanism
The user can replace the image
object by an image with an alternative describing the nature and purpose of the image, via a provided mechanism.
Test 1.4.5: Does each image object (object
tag with the attribute type="image/…"), used as a CAPTCHA or test image, with a text alternative provided
via the aria-label or the aria-labelledby property or the title attribute, meet the following conditions?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
Test 1.4.6: Does each embedded image
(embed tag with the attribute type="image/…"), used
as a CAPTCHA or test image, with a text
alternative, meet one of these conditions?
The embedded image is immediately followed by an
adjacent link giving access to a page or a chunk
of text describing the nature and purpose of the image
The user can replace the embedded image by a text describing the nature and purpose of the image, via a provided mechanism
The user can replace the embedded image by an image with an alternative describing the nature and purpose of the image, via a provided mechanism.
Test 1.4.7: Does each embedded image (object
tag with the attribute type="image/…"), used as a CAPTCHA or test image, with a text alternative provided
via the aria-label or the aria-labelledby property or the title attribute, meet the following conditions?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
Test 1.4.8: Does each vector image (svg
tag), used as a CAPTCHA or test image, with no text alternative, meet the following conditions?
The svg tag has a role="img"
The svg tag has an
aria-label property that describes the nature and purpose of the
image, and matches the value of the title
attribute, if present
The svg tag has a desc
tag that describes the nature and purpose of the
image, and matches the value of the aria-label
property and of the title
attribute of the svg tag, if present
An adjacent link gives access to an alternative that describes the nature and purpose of the
image, and matches the value of the aria-label
property and of the title
attribute of the svg tag, if present
Test 1.4.10: Does each bitmap image (canvas tag), used
as a CAPTCHA or test image, meet one of the following conditions?
The alternative content (between <canvas> and </canvas>) describes the nature and purpose of the image
The bitmap image is immediately followed by an
adjacent link giving access to a page or a chunk
of text containing an alternative describing the nature and purpose of the image
The user can replace the bitmap image
by an alternative describing the nature and purpose of the image, via a provided mechanism
The user can replace the bitmap image
by an image with an alternative describing the nature and purpose of the image, via a provided mechanism.
Test 1.4.11: Does each bitmap image (canvas
tag), used as a CAPTCHA or test image, with a text alternative provided
via the aria-label or the aria-labelledby property or the title attribute, meet the following conditions?
If present, the value of the title attribute
matches the value of the aria-label property
If present, the value of the title attribute matches the content of the chunk of text linked via the aria-labelledby property.
Test 1.4.12: 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
There is a clearly identifiable detailed description adjacent to the image object.
Test 1.6.3: Does each embedded image
(embed tag with an attribute type="image/…") conveying information needing a detailed description, meet one of the following conditions?
An aria-describedby property references a chunk of text serving as a detailed description.
Test 1.6.5:
Does each image button (input tag with the attribute
type="image") conveying information, that references a detailed description via an aria-describedby property, meet the following conditions?
The chunk of text is identified via an id attribute
The value of the id attribute is unique in the page
The value of the aria-describedby property matches the value of the id attribute.
Test 1.6.7: For each vector image (svg tag) conveying information, 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.10: For each image (img, area, object, embed, svg, or canvas tag) conveying information,
with a reference to a detailed description, and having an aria-describedby property, does the aria-describedby property reference the detailed description?
The detailed description adjacent to the object image is
relevant
The detailed description available via an adjacent
link is relevant.
Test 1.7.4: Does each embedded image
(embed tag with the attribute type="image/…") conveying information, 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.9.4: Each embedded image of
text (embed tag with the attribute type="image/…") conveying information
must be replaced with styled
text if possible. Has this rule been followed (except in particular cases)?
Criterion 1.10
[A] Is each image caption correctly associated with the
corresponding image, if necessary?
Test 1.10.1: Does each image with a
caption (img tag or input tag with the attribute
type="image", associated with an adjacent caption) meet,
if necessary, the following conditions?
The image (img tag) and its caption are contained
in a figure tag
The figure tag has an attribute role="group"
The content of the alt attribute contains a
reference to the adjacent caption.
Test 1.10.2: Does each image object with a caption (object tag with the attribute type="image/…",
associated with an adjacent caption) meet, if necessary,
the following conditions?
The image (object tag) and its caption are
contained in a figure tag
The figure tag has an attribute role="group".
Test 1.10.3: Does each embedded image
with a caption (embed tag with the attribute
type="image/…", associated with an adjacent caption)
meet, if necessary, the following conditions?
The embedded image (embed tag) and its caption
are contained in a figure tag
The figure tag has an attribute role="group"
The content of the text alternative contains a
reference to the adjacent caption.
Test 1.10.4: Does each vector image
with a caption (svg tag associated with an adjacent
caption) meet, if necessary, the following conditions?
The vector image (svg tag) and its caption are
contained in a figure tag
The figure tag has an attribute role="group"
The content of the aria-label property or the desc
tag of the vector image contains a reference to the
adjacent caption
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
Criterion 3.1 [A] On each Web page, information must
not be conveyed through color only. 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 through color only. Has this rule been
followed?
Test 3.1.2: For each color indication
provided by a text, information
must not be conveyed through color only. Has this rule been
followed?
Test 3.1.3: For each image conveying
information, information
must not be conveyed through color only. Has this rule been
followed?
Test 3.1.5: For each time-based
media conveying information, information
must not be conveyed through color only. Has this rule been
followed?
Test 3.1.6: For each non-time-based
media conveying
information, information
must not be conveyed through color only. Has this rule been
followed?
Criterion 3.2 [A] On each Web page, information
must not be conveyed through color only. 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 through color only. 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 through color only. 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 through color only. 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 through color only. 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 through color only. 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
There is an alternative version with synchronized
captions that is accessible via an
adjacent link (a URL or an anchor)
Test 4.3.2: For each prerecorded
synchronized time-based
media with synchronized
captions provided through a track tag, does the
track tag have an attribute kind="captions"?
Criterion 4.9 [AAA] Does each prerecorded
time-based
media have a sign language interpretation (except
in particular cases) if necessary?
Test 4.9.1: Does each prerecorded
audio-only time-based
media have a sign language interpretation if
necessary, that is adapted to the media language (except
in particular cases)?
Test 4.9.2: Does each prerecorded
synchronized time-based
media have a sign language interpretation, if
necessary, that is adapted to the media language (except
in particular cases)?
Criterion 4.10 [AAA] For each prerecorded
time-based
media with a sign language interpretation, is this
interpretation relevant?
Test 4.10.1: For each prerecorded
audio-only time-based
media with a sign language interpretation, is this
interpretation relevant?
Test 4.10.2: For each prerecorded
synchronized time-based
media with a sign language interpretation, is this
interpretation relevant?
Test 4.15.1: For each audio-only, video-only or
synchronized time-based
media , does the adjacent textual content help
to clearly identify the time-based media (except
in particular cases)?
Test 4.15.2: For each live audio-only, live video-only or
live synchronized time-based
media, does the adjacent textual content help
to clearly identify the time-based media (except
in particular cases)?
The page to which the adjacent
link refers is accessible
The alternative in the page to which the adjacent
link refers is accessible.
Criterion 4.17 [A] For each non
time-based media with an alternative, is this
alternative relevant?
Test 4.17.1: For each non
time-based media with an alternative, does this
alternative provide access to the same content, and to
similar functionalities?
Test 4.18.1: Does each audio
sequence played automatically via an object, video,
audio, embed, bgsound tag, or a JavaScript code 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, bgsound 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.
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.
Test 5.6.2: For each data
table (table tag), does each row
header have a th tag?
Criterion 5.7 [A] For each data
table, is each cell associated with its header cell 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 cell has a scope attribute with the value
"row" for row headers
The header cell 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 cell does not have a scope attribute
The header cell has a unique id attribute
Test 5.7.4: Does each cell (td or th
tag) associated with one or several header cells 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 header cells 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.
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
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?
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 inline frame) and that has an alternative
meet the following conditions?
The alternative of the non text element is updated
An element that is accessible
through a keyboard and a mouse, performing
the same action, is available in the page
Test 7.3.2: A script
must not remove focus from an element that receives it.
Has this rule been followed (except
in particular cases)?
Test 7.3.3: Does each interface
component implemented via a role defined by the ARIA
API, and matching a Design Pattern, meet one of the
following conditions?
The keyboard interactions comply with the Design
Pattern for the Esc, Space bar, Tab, and arrow keys,
at least
An interface component available in the page,
performing the same action, has keyboard
interactions complying with the Design Pattern for
the Esc, Space bar, Tab, and arrow keys, at least
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)?
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
Test 8.8.1: On each Web page, is each
change in the human language identification (lang and/or
xml:lang attribute) technically valid?
Test 8.8.2: On each Web page, is each
change in the 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.
Test 8.10.2: On each Web page, does
each change in the reading
direction (dir attribute) meet the following conditions?
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. Ensure that the document outline is coherent.
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?
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.
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 sufficient,
and give the user the ability to control text
justification. Ensure that hidden texts are correctly rendered
and that information is not conveyed only by an
element's shape, size or location.
Criterion 10.4 [AA] On each Web page, is
text still readable when characters
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 characters
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 (color) accompanied by a
background color declaration (background, background-color) 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 (background, background-color) accompanied by a
foreground color declaration (color) 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 (background, background-image), is there a
corresponding background color declaration (background, background-color), at least,
inherited from a parent element?
Test 10.6.1: On each Web page, does
each text
link indicated through color alone, and
whose nature is not obvious, have a contrast ratio of 3:1 or greater
with the surrounding text?
Criterion 10.7 [A] On each Web page, is
the focus visible for each element that receives focus?
Test 10.7.1: For each element
receiving focus, the browser default visual cue must not
be removed (CSS property outline, outline-color,
outline-width, outline-style). Has this rule been
followed?
Test 10.7.2: For each element
receiving focus, the browser default visual cue must not
be degraded (CSS property outline-color). Has this rule
been followed?
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
Test 10.14.1: On each Web page, for
each text or set of texts, the information must not be
conveyed by shape, size or location alone. Has this rule
been followed?
Test 10.14.2: On each Web page, for
each image or set of images, the information must not be
conveyed by shape, size or location alone. Has this rule
been followed?
Criterion 10.15 [A] On each Web page,
information must not be conveyed by shape, size or location alone. Has this rule been implemented in a relevant way?
Test 10.15.1: On each Web page, for
each text or set of texts, the information must not be
conveyed by shape, size or location alone. Has this rule
been implemented in a relevant way?
Test 10.15.2: On each Web page, for
each image or set of images, the information must not be
conveyed by shape, size or location alone. Has this rule
been implemented in a relevant way?
For each form, associate each field with its label,
group fields 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.
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-labelledby property, meet the following
conditions?
The label has an id
attribute
The value of the id
attribute is unique
The values of the
aria-labelledby property match the values of the
id attributes of the chunks of text used as labels
The label referenced via the
aria-labelledby property is visible at least when the field gets focus.
Test
11.1.4: Each form
field with an
aria-label property must have a visible adjacent text describing the nature of the expected input. Has this rule been followed?
Test
11.1.5: Does each form
field with a title attribute used as a label, meet one of the following
conditions?
There is no placeholder
attribute
The placeholder
attribute matches the title attribute.
Criterion 11.2 [A] Is each label
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-label property describe the exact function of the associated form field?
Test 11.2.4: Does each label
implemented via the aria-labelledby property describe the exact function of the associated form field?
Test 11.5.1: In each form, is the information of same nature grouped together via a fieldset tag, 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, for
each selection
list (select tag), are 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-label property is relevant
A chunk of text is tied to the button via an
aria-labelledby property.
Test
11.9.2: In each form, does the text of each button
implemented via an aria-labelledby property meet
the following conditions?
Each text used to label the button has an id attribute
The value of each of these id
attributes is unique
The values of the
aria-labelledby property match the values of the
id attributes of the texts used to label the button
The texts used to label the button are
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 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 property
Test
11.10.2: Each mandatory field indication based on the
aria-label or the aria-required properties, 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-describedby
or aria-labelledby properties. Has this rule been followed?
Test
11.10.3: Does each mandatory field indication provided
via a chunk of text tied by
aria-describedby or aria-labelledby properties meet the following
conditions?
The referenced chunk of
text has an id attribute
The value of the id attribute is unique
The values of the aria-describedby or aria-labelledby properties match
the values of the id attributes.
Test
11.10.4: For each form, do the input error messages 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-describedby property
The input error is
signaled via the aria-invalid property.
Test 11.10.5: Each input
error indication based on the
aria-label or aria-invalid properties must have an explicit
visual cue in the label: a label tag, an adjacent visible text or a chunk of
text tied to the form field via the aria-describedby or aria-labelledby properties. Has this rule
been followed?
Test
11.10.6: Does each input error indication provided via
a chunk of text tied by aria-describedby or aria-labelledby properties meet the following
conditions?
The referenced chunk of
text has an id attribute
The value of the id
attribute is unique
The values of the aria-describedby or aria-labelledby properties match
the values of the id attributes of the texts used as labels.
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 property.
Test
11.10.8: Each data type and/or format indication based
on the aria-label property 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-describedby or aria-labelledby properties. Has this
rule been followed?
Test
11.10.9: Does each data type and/or format indication
provided via a chunk of text tied to the form field by
aria-describedby or aria-labelledby properties meet the following
conditions?
The referenced chunk of
text has an id attribute
The value of the id
attribute is unique
The values of the
aria-describedby or aria-labelledby properties match
the values of these id attributes.
Test
11.10.10: Does each form
field with a title attribute used as an input help, meet one of the following
conditions?
There is no placeholder
attribute
The placeholder
attribute matches the title attribute.
Criterion 11.11 [AA] In each form, is input
control accompanied, if necessary,
by suggestions helping with the correction of input
errors?
Test 11.11.1: For each form, for
each input error, are each data
types and formats suggested, if necessary?
Test 11.11.2: For each form, for
each input error, are examples for expected values
suggested, if necessary?
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 property
An assistant is available.
Test
11.14.2: Each indication based on the
aria-label property 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-describedby property meet
the following conditions?
The referenced chunk of
text has an id attribute
The value of the id
attribute is unique
The values of the aria-describedby property match the values of the id
attributes.
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
property.
Test 11.14.5: Each input
suggestion based on the aria-label property 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-describedby property meet the following conditions?
The referenced chunk of
text has an id attribute
The value of the id
attribute is unique
The values of the
property aria-describedby properties match the value of the id
attributes.
Criterion 11.15 [AAA] For each form, is
each input assistance relevant?
Test 11.15.1: For each form, is
each input assistance relevant?
Criterion 12.14 [A] On each Web page,
navigation must not contain keyboard trap. Has this rule
been followed?
Test 12.14.1: On each Web page, does
each element that receives focus meet one of the
following conditions?
It is possible to reach the next or previous
element that can receive focus with the tab key
The user is informed about the existence of a functional mechanism,
allowing to reach the next or previous element that
can receive focus with the keyboard.
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 (object tag, embed tag, svg tag, canvas 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 redirection initiated via a script
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 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 limitation of the session duration meet one of the
following conditions (except in particular cases)?
The user can suppress the limitation
The user can increase the session duration
The session duration 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 triggered by a link
(target attribute) or a JavaScript command, is
the user warned?
Test 13.2.2: On each Web page, for
each window opening triggered by an object, or
embed tag, is the user warned?
Test 13.2.3: On each Web page, for
each window opening triggered by 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 happen 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 office document
that can be downloaded have an accessible version if
necessary?
Test 13.7.1: On each Web page, does
each downloading functionality for an office
document meet one of the following conditions?
An alternative accessibility-supported version of
the document that can be downloaded is available
An alternative version of the document that
can be downloaded is available in HTML format.
Criterion 13.8 [A] For each office document with an accessible version, does this version provide the same information?
Test 13.8.1: Does each office
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 expressions, idioms or jargon made explicit?
Test 13.9.1: On each Web page, does
each expressions used in an unusual or restricted way, each
idiom or jargon meet one of the following conditions?
A definition is available in the adjacent context of the expression and is marked up by the dfn tag
A definition is available via a definition list
A definition is available in the page
The expression is contained in a link giving access to the definition.
Criterion 13.10 [AAA] On each Web page,
for each expression 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 expression used in an unusual or restricted way, each 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 cryptic content (ASCII art, emoticon,
leetspeak) have an alternative?
Test 13.11.1: On each Web page,
does each cryptic content (ASCII art, emoticon,
leetspeak) 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 cryptic content (ASCII art, emoticon, leetspeak) with an alternative, is this alternative relevant?
Test 13.12.1: On each Web page,
does each cryptic content (ASCII art, emoticon,
leetspeak) 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 nouns and the title) meet one of the
following conditions?
An illustration or graphic symbols adapted to the
reading level of the lower secondary education level
are available
A version in sign language (adapted to the human
language of the content) is available
A spoken version of the text is available
A summary adapted to the reading level of the
lower secondary education level is available.
Test 13.15.1: On each Web page, does
each image (img tag, svg tag, canvas tag, embed tag, or object tag)
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 surface of effects is smaller than
or equal to 21,824 pixels.
Test 13.16.1: On each Web page, does
each sudden change in luminosity or flashing effect
caused by an image (img tag, svg
tag, embed tag, canvas tag, or object tag) have
a frequency lower than or equal to 3 per second?