RGAA V2
Contents
- 1 RGAA v.2 (English Translation)
- 2 1.1 [Frames]1: The page is free of untitled frames
- 3 1.2 [Frames]2: Relevance of frame titles
- 4 2.1 [Colors]1: Provision of an alternative means of identification in the event that color names are used to refer to page content
- 5 2.2 [Colors]2: Provision of an alternative means of identification in the event that color names are used in non-text elements to refer to page content
- 6 2.3 [Colors]3: Provision of a means of transmitting information other than by color based on CSS styles
- 7 2.4 [Colors]4: Provision of an alternative to color as a means of transmitting information in non-text elements
- 8 2.5 [Colors]5: Value of the contrast ratio for text contained within non-text elements (minimum)
- 9 2.6 [Colors]6: Value of the contrast ratio for text contained within non-text elements that are used as backgrounds for HTML elements (minimum)
- 10 2.7 [Colors]7: Value of the contrast ratio of text contained within a text segment (minimum)
- 11 2.8 [Colors]8: Value of the contrast ratio of enlarged text contained within non-text elements (minimum)
- 12 2.9 [Colors]9: Value of the contrast ratio of enlarged text contained in non-text elements used as HTML background elements (minimum)
- 13 2.10 [Colors]10: Value of the contrast ratio for enlarged text contained within a text segment (minimum)
- 14 2.11 [Colors]11: Value of the contrast ratio of text contained in non-text elements (enhanced)
- 15 2.12 [Colors]12: Value of the contrast ratio of text contained in non-text elements used as HTML background elements (enhanced)
- 16 2.13 [Colors]13: Value of the contrast ratio of text contained within a text segment (enhanced)
- 17 2.14 [Colors]14: Value of the contrast ratio of enlarged text contained within non-text elements (enhanced)
- 18 2.15 [Colors]15: Value of the contrast ratio of enlarged text contained in non-text elements used as HTML background elements (enhanced)
- 19 2.16 [Colors]16: Value of the contrast ratio of enlarged text contained within a text segment (enhanced)
- 20 3.1 [Forms]1: Possibility of identifying data entry errors
- 21 3.2 [Forms]2: Provision of prior warnings relating to mandatory fields as well as the type/format of the expected input if necessary
- 22 3.3 [Forms]3: Correct positioning of labels with respect to fields in a form
- 23 3.4 [Forms]4: Grouping of form elements via the fieldset element
- 24 3.5 [Forms]5: No fieldset appears without an associated legend
- 25 3.6 [Forms]6: Relevance of the content of the legend element in the context of the fieldset in question
- 26 3.7 [Forms]7: Correct use of the optgroup element to group option elements within a select element
- 27 3.8 [Forms]8: Provision of a label attribute on the optgroup element
- 28 3.9 [Forms]9: Relevance of the label attribute's content within the optgroup element
- 29 3.10 [Forms]10: No form element appears without an identifier
- 30 3.11 [Forms]11: No form element appears without a label
- 31 3.12 [Forms]12: Relevance of form element labels
- 32 3.13 [Forms]13: Provision of information or suggestions to facilitate form data-entry
- 33 3.14 [Forms]14: Provision of mechanisms allowing the verification, modification and confirmation of legal, financial or personal data
- 34 3.15 [Forms]15: Provision of mechanisms allowing the verification, modification and confirmation of all user-entered data
- 35 3.16 [Forms]16: Provision of a help page or a contextual help mechanism for form entry data
- 36 4.1 [Images]1: Provision of the alt attribute
- 37 4.2 [Images]2: Relevance of the text alternative in the case of image links
- 38 4.3 [Images]3: Relevance of the text alternative in the case of clickable regions or image based buttons
- 39 4.4 [Images]4: Relevance of the text alternative to non-text elements
- 40 4.5 [Images]5: Appropriateness of the empty text alternative to decorative elements
- 41 4.6 [Images]6: Length of text alternatives
- 42 4.7 [Images]7: Existence of a long description for images, when necessary
- 43 4.8 [Images]8: Relevance of the long description for images that need it
- 44 4.9 [Images]9: Provision of the longdesc attribute to link an image to its long description
- 45 4.10 [Images]10: Provision of contextual information and a means of access for Captcha when the alternative cannot be communicated
- 46 4.11 [Images]11: Coherence of text alternatives and form labels across the site
- 47 5.1 [Multimedia]1: Access to summary information for audio content, animated graphics or synchronized media
- 48 5.2 [Multimedia]2: Provision of a text transcription for audio content, animated graphics or synchronized media
- 49 5.3 [Multimedia]3: Relevance of the text transcription for audio content, animated graphics or synchronized media
- 50 5.4 [Multimedia]4: Provision of a synchronized audio description or a textual transcription for animated visual content and synchronized media
- 51 5.5 [Multimedia]5: Relevance of the synchronized audio description to the animated visual content or synchronized media
- 52 5.6 [Multimedia]6: Possibility of controlling the activation of the synchronized audio description
- 53 5.7 [Multimedia]7: Provision of an extended synchronized audio description for animated visual content and synchronized media
- 54 5.8 [Multimedia]8: Provision of a synchronized audio description for animated visual content and synchronized media
- 55 5.9 [Multimedia]9: Provision of synchronized sub-titles for synchronized media that is not a live broadcast
- 56 5.10 [Multimedia]10: Relevance of the synchronized sub-titles to the synchronized media
- 57 5.11 [Multimedia]11: Provision of an alternative for all applet or object elements
- 58 5.12 [Multimedia]12: Provision of an alternative for embedded objects
- 59 5.13 [Multimedia]13: The page is free of any element that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
- 60 5.14 [Multimedia]14: The page is free of any javascript code that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
- 61 5.15 [Multimedia]15: The page is free of any style layout that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
- 62 5.16 [Multimedia]16: Compatibility of all programmed elements with respect to assistive technology
- 63 5.17 [Multimedia]17: Total absence of sudden changes in brightness or red flash behavior beyond the threshold frequency
- 64 5.18 [Multimedia]18: Provision of synchronized sub-titles for live sound or synchronized media
- 65 5.19 [Multimedia]19: Absence of the blink element
- 66 5.20 [Multimedia]20: The page is free of elements that cause automatically initiated and unstoppable blinking effects
- 67 5.21 [Multimedia]21: The page is free of javascript that causes automatically initiated and unstoppable blinking effects
- 68 5.22 [Multimedia]22: The page is free of all style layouts that cause automatically initiated and unstoppable blinking effects
- 69 5.23 [Multimedia]23: Absence of the marquee element
- 70 5.24 [Multimedia]24: The page is free of elements displaying automatically initiated and unstoppable motion effects
- 71 5.25 [Multimedia]25: The page is free of all javascript code that causes automatically initiated and unstoppable motion effects
- 72 5.26 [Multimedia]26: The page is free of all style layouts that cause automatically initiated and unstoppable motion effects
- 73 5.27 [Multimedia]27: Device independence for object, embed and applet elements
- 74 5.28 [Multimedia]28: Provision of an alternative for any object, embed or applet element that is device dependent
- 75 5.29 [Multimedia]29: The page is free of any element that initiates unstoppable audio output
- 76 5.30 [Multimedia]30: Absence of the bgsound element
- 77 5.31 [Multimedia]31: Provision of a version signed in French sign language facilitating understanding of synchronized media
- 78 5.32 [Multimedia]32: Relevance of the sign language version
- 79 5.33 [Multimedia]33: Sound volume of audio tracks
- 80 5.34 [Multimedia]34: It is possible to change the foreground and background colors in text blocks
- 81 6.1 [Navigation]1: Provision of text based links doubling server-side clickable regions
- 82 6.2 [Navigation]2: Advance warning for all new browser windows that may open as a result of the use of the target attribute on text based links and in forms
- 83 6.3 [Navigation]3: Advance warning for all new browser windows that may open as a result of the use of the target attribute in image based links and in clickable regions
- 84 6.4 [Navigation]4: Advance warning for all new browser windows that may open as a result of javascript code
- 85 6.5 [Navigation]5: The page is free of any automatically opening browser windows (without user action)
- 86 6.6 [Navigation]6: The page is free of obstacles to keyboard navigation
- 87 6.7 [Navigation]7: The page is free of any meta element that provokes a page refresh
- 88 6.8 [Navigation]8: The page is free of any javascript code that provokes an automatic and unstoppable page refresh
- 89 6.9 [Navigation]9: The page is free of elements that provoke an automatic and unstoppable page refresh
- 90 6.10 [Navigation]10: The page is free of any meta element that provokes an automatic page redirect
- 91 6.11 [Navigation]11: The page is free of any javascript code that provokes an automatic and unstoppable page redirect
- 92 6.12 [Navigation]12: The page is free of elements that provoke an automatic and unstoppable page redirects
- 93 6.13 [Navigation]13: Possibility of identifying the destination or action of all links and buttons
- 94 6.14 [Navigation]14: Possibility of identifying the destination or action of all links and buttons (link text only)
- 95 6.15 [Navigation]15: Consistency of the destination or action of links that carry the same link text
- 96 6.16 [Navigation]16: The page is free of unnamed links
- 97 6.17 [Navigation] Provision of a page containing the site map
- 98 6.18 [Navigation]18: Coherence of the site map
- 99 6.19 [Navigation]19: Provision of a link to the site map on the home page
- 100 6.20 [Navigation]20: Provision of breadcrumbs
- 101 6.21 [Navigation]21: Provision of menus or navigation bars
- 102 6.22 [Navigation]22: Consistency of the placement of menus and navigation bars in the HTML source
- 103 6.23 [Navigation]23: Consistency of the presentation of menus and navigation bars
- 104 6.24 [Navigation]24: Keyboard navigation follows a logical order with respect to page content
- 105 6.25 [Navigation]25: Advance warning of a new browser window opening via an object or embed element
- 106 6.26 [Navigation]26: Document downloads: inclusion of information regarding document format
- 107 6.27 [Navigation]27: Document downloads: inclusion of information regarding document size
- 108 6.28 [Navigation]28: Document downloads: inclusion of information regarding document language
- 109 6.29 [Navigation]29: Links of like functionality are grouped together
- 110 6.30 [Navigation]30: Groups of links are tagged accordingly
- 111 6.31 [Navigation]31: Skip links and rapid access links are present for the link groups
- 112 6.32 [Navigation]32: Consistency across the site for the skip links and rapid access links to the link groups
- 113 6.33 [Navigation]33: Order of the skip links or the rapid access links in the page source code
- 114 6.34 [Navigation]34: A search function is present
- 115 6.35 [Navigation]35: Possibility of navigating easily within a group of pages
- 116 6.36 [Navigation]36: Provision of an indicator giving the current position during navigation
- 117 7.1 [Visual Presentation]1: No information bearing content is generated via the CSS
- 118 7.2 [Visual Presentation]2: No change to the possible interpretation of a block of information in the event that the CSS is deactivated
- 119 7.3 [Visual Presentation]3: Readability of information displayed as page background via the CSS is retained when the styles are deactivated
- 120 7.4 [Visual Presentation]4: No spaces are used for separating the letters in a word
- 121 7.5 [Visual Presentation]5: No text color is specified without a background color also being specified and vice-versa
- 122 7.6 [Visual Presentation]6: Possibility of replacing non text elements with equivalent text elements stylized accordingly by the CSS
- 123 7.7 [Visual Presentation]7: Possibility of replacing non text elements with equivalent text elements stylized accordingly by the CSS (without exceptions)
- 124 7.8 [Visual Presentation]8: The page is free of HTML page-layout tags or attributes
- 125 7.9 [Visual Presentation]9: The page is free of any HTML elements used solely for page layout purposes
- 126 7.10 [Visual Presentation]10: Links are visually distinct from surrounding text
- 127 7.11 [Visual Presentation]11: Focus effects on links have not been removed
- 128 7.12 [Visual Presentation]12: The page is free of text justification
- 129 7.13 [Visual Presentation]13: Document legibility is not adversely affected by increased text character size
- 130 7.14 [Visual Presentation]14: The page is free of styles using absolute unit values or pixels for character sizes in form elements
- 131 7.15 [Visual Presentation]15: The page is free of horizontal scroll bars, even on full screen displays
- 132 7.16 [Visual Presentation]16: Width of text blocks
- 133 7.17 [Visual Presentation]17: Interline and inter-paragraph spacing
- 134 7.18 [Visual Presentation]18: Correct screen reader rendering of hidden elements
- 135 8.1 [Scripts]1: Updating of elements that are alternatives to non-text elements
- 136 8.2 [Scripts]2: Non-dependence on the onclick event manager
- 137 8.3 [Scripts]3: No specific device dependence for event managers
- 138 8.4 [Scripts]4: Possibility of turning off unsolicited alerts and automatic updates in a page
- 139 8.5 [Scripts]5: The page is free of changes in context based on user input but without explicit validation or warning
- 140 8.6 [Scripts]6: Tabulation order of dynamically updated content in javascript
- 141 8.7 [Scripts]7: Correct use of the role of an element
- 142 8.8 [Scripts]8: Provision of an alternative to javascript code when that code is device-dependent or contains non-universal event managers
- 143 8.9 [Scripts]9: The page is free of any javascript whose effect would be to inhibit keyboard focus on an element
- 144 8.10 [Scripts]10: Absence of time limits for completing tasks
- 145 8.11 [Scripts]11: No information loss upon the expiration of an authenticated session
- 146 8.12 [Scripts]12: Provision of an alternative to javascript
- 147 8.13 [Scripts] Accessibility of dynamic javascript content
- 148 9.1 [Standards]1: Provision of a declared DTD
- 149 9.2 [Standards]2: Correct placement of the declared DTD
- 150 9.3 [Standards]3: Correct syntax of the declared DTD
- 151 9.4 [Standards]4: HTML / XHTML validity with respect to the declared DTD
- 152 9.5 [Standards]5: The page is free of obsolete components with respect to the W3C specifications used
- 153 9.6 [Standards]6: Provision of a page title
- 154 9.7 [Standards]7: Relevance of the page title
- 155 9.8 [Standards]8: Explicit mention of the page's language
- 156 10.1 [Structure]1: Provision of at least one top level header (H1)
- 157 10.2 [Structure]2: Relevance of page header content
- 158 10.3 [Structure]3: Continuity of the hierarchy of page headers
- 159 10.4 [Structure]4: Provision of a complete hierarchy of page headers
- 160 10.5 [Structure]5: The page is free of fake (simulated) lists
- 161 10.6 [Structure]6: Systematic use of true ordered list structures for enumerated lists
- 162 10.7 [Structure]7: Correct tagging for definition lists
- 163 10.8 [Structure]8: Correct tagging of quotations
- 164 10.9 [Structure]9: Correct tagging of abbreviations present in the page
- 165 10.10 [Structure]10: Correct tagging of acronyms present in the page
- 166 10.11 [Structure]11: Relevance of an abbreviation's declared meaning
- 167 10.12 [Structure]12: Relevance of an acronym's declared meaning
- 168 10.13 [Structure] Accessibility of documents that are offered for download
- 169 11.1 [Tables]11: Provision of th tags to indicate header lines and columns in data-tables
- 170 11.2 [Tables]2: Relation between the headers (th) and the data-cells (td) associated with them in a data-table through use of the id and headers or scope attributes
- 171 11.3 [Tables]3: Relation between the headers (th) and the data-cells (td) associated with them in a complex data-table through use of the id and headers attributes
- 172 11.4 [Tables]4: Tables used for layout purposes do not contain elements particular to data-tables
- 173 11.5 [Tables]5: Text characters are not used in the formatting of data-tables or column layouts
- 174 11.6 [Tables]6: Correct linearization of layout tables
- 175 11.7 [Tables]7: Provision of a title for each data-table
- 176 11.8 [Tables]8: Provision of a summary for each data-table
- 177 11.9 [Tables]9: Relevance of the table's title to its content
- 178 11.10 [Tables]10: Relevance of the table's summary to its content
- 179 12.1 [Texts]1: Language changes in the text are indicated
- 180 12.2 [Texts]2: Indications of language changes are provided as attributes in HTLM elements
- 181 12.3 [Texts]3: Synchronization and equivalence of information made available in an alternative version
- 182 12.4 [Texts] Availability of necessary complementary information via links or definitions
- 183 12.5 [Texts]5: Absence of cryptic syntax to make references to the site's own content
- 184 12.6 [Texts]6: Availability, where necessary, of phonetic transcriptions for words
- 185 12.7 [Texts]7: Provision of a means of information transmission other than shape or position in non-text elements
- 186 12.8 [Texts]8: Provision of an alternate means of identifying content which is referred to in a non-text element with regard to the content's shape or position
- 187 12.9 [Texts]9: Provision of an alternate means for identifying content which is referred to textually with respect to its shape or position
- 188 12.10 [Texts]10: Use of clear and simple concise writing style, universally comprehensible
RGAA v.2 (English Translation)
The "Référentiel Général d'Accessibilité pour les Administrations" (RGAA) is the French Accessibility standard, heavily based on the WCAG but differing in structure from WCAG 2.
The is intended to define, in France, the technical modalities of accessibility of online services of the State, local authorities and public institutions over the three channels Web, television and telephony.
RGAA is the result of the reachability obligation imposed by Article 47 of the Law of 11 February 2005 for "equal rights and opportunities, participation and citizenship of people with disabilities" the application of the law was published in the Official Journal 16 May 2009 and was approved for the Web in October 2009.
The RGAA gathers success criteria into 12 themes:
- Frames
- Colors
- Forms
- Images
- Multimedia
- Navigation
- Display
- Scripts
- Standards
- Structure
- Tables
- Texts
(The above has been translated from the <a href="http://fr.wikipedia.org/wiki/RGAA">French Wikipedia article about the RGAA</a>).
The following is a translation of the <a href="http://references.modernisation.gouv.fr/sites/default/files/RGAA-v2.2_Annexe2-Tests.pdf">Annex 2: Tests, of the RGAA v.2</a> (pdf file, 3.5Mb)
1.1 [Frames]1: The page is free of untitled frames
Applies to:
- frame
- iframe
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element contains a non-empty title attribute, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H64">H64: Using the title attribute of the frame and iframe elements</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- 4.1.2 Name, Role, Value: – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, Role, Value:">Understanding success criterion 4.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
1.2 [Frames]2: Relevance of frame titles
Applies to:
- frame
- iframe
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element contains a non-empty title attribute, continue; otherwise, the test is not applicable.
- If the title attribute accurately describes the frame's content, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H64">H64: Using the title attribute of the frame and iframe elements</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- 4.1.2 Name, Role, Value: – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, Role, Value:">Understanding success criterion 4.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
2.1 [Colors]1: Provision of an alternative means of identification in the event that color names are used to refer to page content
Applies to:
Any text segment mentioning a color (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
- If the text segment named in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the text segment refers to content in the page or of the site, continue; otherwise, the test is not applicable.
- If the text segment allows for the identification of said content by another means than color, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G182">G182: Ensuring that additional visual cues are available when text color differences are used to convey information</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0 .
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
- Editors and content providers
2.2 [Colors]2: Provision of an alternative means of identification in the event that color names are used in non-text elements to refer to page content
Applies to:
- img
- inputs of type image
- applet
- object
- embed
- or javascript code generating any of these elements
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays text graphically or contains a non-empty alt attribute, continue; otherwise, the test is not applicable.
- If the graphically rendered text or its alternative name a color and refer to content of the page or site, continue; otherwise, the test is not applicable.
- If the graphically rendered text or its alternative allow for identification of said content by another means than color, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H92">H92: Including a text cue for colored form control labels</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0 .
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
- Editors and content providers
2.3 [Colors]3: Provision of a means of transmitting information other than by color based on CSS styles
Applies to:
Any HTML element carrying a style that uses at least one of the following CSS properties:
- color
- background-color
- background
- border-color
- border
- outline-color
- outline
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element bears information by means of color, continue; otherwise, the test is not applicable.
- If the information borne by the element is also transmitted by a means other than color, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G14">G14: Ensuring that information conveyed by color differences is also available in text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G138">G138: Using semantic markup whenever color cues are used</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F81">F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0 .
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
- Editors and content providers
2.4 [Colors]4: Provision of an alternative to color as a means of transmitting information in non-text elements
Applies to:
- img
- inputs of type image
- applet
- object
- embed
or javascript code generating any of these elements.
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays color zones that convey information, continue; otherwise, the test is not applicable.
- If the information conveyed via the color in these zones is also transmitted by a means other than color, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G111">G111: Using color and pattern</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0 .
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
- Editors and content providers
2.5 [Colors]5: Value of the contrast ratio for text contained within non-text elements (minimum)
Applies to:
- img
- inputs of type image
- applet
- object
- embed
as well as CSS property or javascript code generating any of these elements.
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 4.5, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G18">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0 .
- 1.4.3 Contrast (Minimum): – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum):">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.6 [Colors]6: Value of the contrast ratio for text contained within non-text elements that are used as backgrounds for HTML elements (minimum)
Applies to:
- background
- background-image
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 4.5, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F83">F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.7 [Colors]7: Value of the contrast ratio of text contained within a text segment (minimum)
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript code or style sheets, and colored by style declarations using at least one of the following CSS properties:
- color
- background
- background-color
- background-image
- content
- list
- list-style-image
Test procedure
- If the text segment named in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the text segment displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 4.5, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G18">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.8 [Colors]8: Value of the contrast ratio of enlarged text contained within non-text elements (minimum)
Applies to:
- img
- inputs of type image
- applet
- object
- embed
or CSS property generating one of these elements, or javascript code generating any of these elements.
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 3, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G145">G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.9 [Colors]9: Value of the contrast ratio of enlarged text contained in non-text elements used as HTML background elements (minimum)
Applies to:
Any HTML element being subject to styles using at least one of the following CSS properties:
- background
- background-image
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 3, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G145">G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.10 [Colors]10: Value of the contrast ratio for enlarged text contained within a text segment (minimum)
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript code or style sheets, and colored by style declarations using at least one of the following CSS properties:
- color
- background
- background-color
- background-image
- content
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 3, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G145">G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.11 [Colors]11: Value of the contrast ratio of text contained in non-text elements (enhanced)
Applies to:
- img
- inputs of type image
- applet
- object
- embed
or CSS property generating one of these elements, or javascript code generating any of these elements.
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 7, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G17">G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.12 [Colors]12: Value of the contrast ratio of text contained in non-text elements used as HTML background elements (enhanced)
Applies to:
Any HTML element being subject to styles using at least one of the following CSS properties:
- background
- background-image
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 7, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F83">F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text)</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.13 [Colors]13: Value of the contrast ratio of text contained within a text segment (enhanced)
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript code or style sheets, and colored by style declarations using at least one of the following CSS properties:
- color
- background
- background-color
- background-image
- content
- list
- list-style-image
Test procedure
- If text segment mentioned in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 7, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G17">G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.14 [Colors]14: Value of the contrast ratio of enlarged text contained within non-text elements (enhanced)
Applies to:
- img
- inputs of type image
- applet
- object
- embed
or CSS property generating one of these elements, or javascript code generating any of these elements.
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 4.5, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G18">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.15 [Colors]15: Value of the contrast ratio of enlarged text contained in non-text elements used as HTML background elements (enhanced)
Applies to:
Any HTML element being subject to styles using at least one of the following CSS properties:
- background
- background-image
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the color of the text and that of the background are based on values defined by the style-guide for public online communications, and this dates from before the publication of the RGAA, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 4.5, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G18">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
2.16 [Colors]16: Value of the contrast ratio of enlarged text contained within a text segment (enhanced)
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript code or style sheets, and colored by style declarations using at least one of the following CSS properties:
- color
- background
- background-color
- background-image
- content
- list
- list-style-image
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays information-bearing text, is not a logo or a text component of a logo and no mechanism allowing the correct display at sufficient contrasts exists, continue; otherwise, the test is not applicable.
- If the final size of the displayed text is less than 150% (120% for bold face) of the default text size specified by the styles of the page, or, if these are absent, the current default size instated by a browser, continue; otherwise, the test is not applicable.
- If the contrast ratio between the text and the background is greater than or equal to 3, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G18">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G174">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.6 Contrast (enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
3.1 [Forms]1: Possibility of identifying data entry errors
Applies to:
The form element
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element is subject to verification before processing, continue; otherwise, the test is not applicable.
- If the verification indicates which fields are in error, and, if necessary, offers some precision on the data format that is expected, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G83">G83: Providing text descriptions to identify required fields that were not completed</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G84">G84: Providing a text description when the user provides information that is not in the list of allowed values</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G85">G85: Providing a text description when user input falls outside the required format or values</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.1 Error Identification –<a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-identified.html" title="Understanding success criterion 3.3.1: Error Identification">Understanding success criterion 3.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
3.2 [Forms]2: Provision of prior warnings relating to mandatory fields as well as the type/format of the expected input if necessary
Applies to:
- input type="text"
- input type="checkbox"
- input type="file"
- input type="radio"
- input type="password"
- select
- textarea
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is subject to verification before processing, continue; otherwise, the test is not applicable.
- If the user is advised as to the mandatory character of the element and, if necessary, its required data format, by one of the following mechanisms:
- indication at the beginning of the form with identification of each of the fields concerned by a distinct marker placed before the element, in terms of the page source, (or after the element for inputs of type "checkbox" or "radio") inside the label tag associated with the element,
- indication before of each element concerned (or after the element for inputs of type "checkbox" or "radio") inside the label tag associated with the element,
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G83">G83: Providing text descriptions to identify required fields that were not completed</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G89">G89: Providing expected data format and example</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G184">G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H44">H44: Using label elements to associate text labels with form controls</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Graphic designers and ergonomics experts
3.3 [Forms]3: Correct positioning of labels with respect to fields in a form
Applies to:
- input type="text"
- input type="password"
- input type="checkbox"
- input type="file"
- input type="radio"
- select
- textarea
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If a text segment is used as a label for one of the elements in the domain of application, continue; otherwise, the test is not applicable.
- If the text segment is placed so as to be associated visually with the element in question, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G162">G162: Positioning labels to maximize predictability of relationships</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
3.4 [Forms]4: Grouping of form elements via the fieldset element
Applies to:
The form element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element doesn't contain a fieldset element, continue; otherwise, the test is not applicable.
- If the fields contained within the form element don't need any global information concerning their function or if such a grouping cannot be maintained for reasons of the type of information expected, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H71">H71: Providing a description for groups of form controls using fieldset and legend elements </a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.5 [Forms]5: No fieldset appears without an associated legend
Applies to:
The fieldset element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element contains a legend element, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H71">H71: Providing a description for groups of form controls using fieldset and legend elements </a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.6 [Forms]6: Relevance of the content of the legend element in the context of the fieldset in question
Applies to:
Any fieldset element fieldset containing a legend.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the content of the legend element provides the necessary information for identifying the content of the fieldset, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H71">H71: Providing a description for groups of form controls using fieldset and legend elements </a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.7 [Forms]7: Correct use of the optgroup element to group option elements within a select element
Applies to:
The select element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element doesn't contain any optgroup element, continue; otherwise, the test is not applicable.
- If the option elements contained in the select element couldn't benefit from at least two distinct regroupings, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H85">H85: Using OPTGROUP to group OPTION elements inside a SELECT</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.8 [Forms]8: Provision of a label attribute on the optgroup element
Applies to:
The optgroup element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.</li
- If the element possesses a label attribute, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H85">H85: Using OPTGROUP to group OPTION elements inside a SELECT</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.9 [Forms]9: Relevance of the label attribute's content within the optgroup element
Applies to:
Any optgroup element having a label attribute.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the content of the label attribute provides the necessary information for the simple identification of the optgroup element's content, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H85">H85: Using OPTGROUP to group OPTION elements inside a SELECT</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.10 [Forms]10: No form element appears without an identifier
Applies to:
- input type="text"
- input type="password"
- input type="file"
- input type="radio"
- input type="checkbox"
- textarea
- select
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element has no title attribute indicating the exact function of the element, continue; otherwise, the test is not applicable.
- If the element has a non-empty id attribute which is unique in the page, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H44">H44: Using label elements to associate text labels with form controls</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
- 4.1.2 Name, Role, Value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, Role, Value">Understanding success criterion 4.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.11 [Forms]11: No form element appears without a label
Applies to:
The form element.
- input type="text"
- input type="password"
- input type="file"
- input type="radio"
- input type="checkbox"
- textarea
- select
that has a non-empty and unique id attribute.
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element has no title attribute indicating the exact function of the element, continue; otherwise, the test is not applicable.
- If a label element is present and contains a for attribute corresponding in value to the id of the form element in question, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G82">G82: Providing a text alternative that identifies the purpose of the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G131">G131: Providing descriptive labels</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H44">H44: Using label elements to associate text labels with form controls</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H65">H65: Using the title attribute to identify form controls when the label element cannot be used/a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F17">F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F68">F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F82">F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F86">F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 2.4.6 Headings and Labels – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-descriptive.html" title="Understanding success criterion 2.4.6: Headings and Labels">Understanding success criterion 2.4.6</a>
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
- 4.1.2 Name, Role, Value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, Role, Value">Understanding success criterion 4.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.12 [Forms]12: Relevance of form element labels
Applies to:
The label element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a text segment contained in the label element, or used as the title attribute of the element, informs as to the exact function of the associated form element, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G82">G82: Providing a text alternative that identifies the purpose of the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G131">G131: Providing descriptive labels</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H44">H44: Using label elements to associate text labels with form controls</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
- 2.4.6 Headings and Labels – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-descriptive.html" title="Understanding success criterion 2.4.6: Headings and Labels">Understanding success criterion 2.4.6</a>
- 3.3.2 Labels or Instructions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-cues.html" title="Understanding success criterion 3.3.2: Labels or Instructions">Understanding success criterion 3.3.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
3.13 [Forms]13: Provision of information or suggestions to facilitate form data-entry
Applies to:
The form element.
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is subject to verification before submission and processing, continue; otherwise, the test is not applicable.
- If specific formats or types of input are expected, continue; otherwise, the test is not applicable.
- If the control procedure indicates which types or formats are expected as input or suggests corrections for erroneous entries, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G84">G84: Providing a text description when the user provides information that is not in the list of allowed values</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G85">G85: Providing a text description when user input falls outside the required format or values</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G177">G177: Providing suggested correction text</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.3 Error Suggestion – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-suggestions.html" title="Understanding success criterion 3.3.3: Error Suggestion">Understanding success criterion 3.3.3</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
3.14 [Forms]14: Provision of mechanisms allowing the verification, modification and confirmation of legal, financial or personal data
Applies to:
The form element.
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows input of a legal, financial or personal nature, continue; otherwise, the test is not applicable.
- If the user has at least one of the following possibilities:
- to modify or cancel the input after its entry
- to verify and correct the input in advance of final submission
- to respond to an explicit confirmation request before submission (this being an additional step or field)
- recover deleted data when the actions involve deletion (except in cases where explicit confirmation of deletion is requested before submission),
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G98">G98: Providing the ability for the user to review and correct answers before submitting</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G99">G99: Providing the ability to recover deleted information</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G155">G155: Providing a checkbox in addition to a submit button</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G164">G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G168">G168: Requesting confirmation to continue with selected action</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- Error Prevention (Legal, Financial, Data) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-reversible.html" title="Understanding success criterion 3.3.4: Error Prevention (Legal, Financial, Data)">Understanding success criterion 3.3.4</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
3.15 [Forms]15: Provision of mechanisms allowing the verification, modification and confirmation of all user-entered data
Applies to:
The form element.
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows user input, continue; otherwise, the test is not applicable.
- If the user has at least one of the following possibilities:
- to modify or cancel the input after its entry
- to verify and correct the input in advance of final submission
- to respond to an explicit confirmation request before submission (this being an additional step or field)
- recover deleted data when the actions involve deletion (except in cases where explicit confirmation of deletion is requested before submission),
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G98">G98: Providing the ability for the user to review and correct answers before submitting</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G99">G99: Providing the ability to recover deleted information</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G155">G155: Providing a checkbox in addition to a submit button</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G164">G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G168">G168: Requesting confirmation to continue with selected action</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.6 Error Prevention (All) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-reversible-all.html" title="Understanding success criterion 3.3.6: Error Prevention (All)">Understanding success criterion 3.3.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
3.16 [Forms]16: Provision of a help page or a contextual help mechanism for form entry data
Applies to:
- input type="text"
- textarea
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows user input, continue; otherwise, the test is not applicable.
- If the user can get contextual help for each field via at least one of the following mechanisms::
- a help page
- a data-entry assistant
- spell checking and suggestions for text input
- information or examples about the required formats or types of input
- indications at the beginning of the form and use of a distinctive marker before each field concerned
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G71">G71: Providing a help link on every Web page</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G89">G89: Providing expected data format and example</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G184">G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G193">G193: Providing help by an assistant in the Web page</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G194">G194: Providing spell checking and suggestions for text input</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.3.5 Help – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/minimize-error-context-help.html" title="Understanding success criterion 3.3.5: Help">Understanding success criterion 3.3.5</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
- Graphic designers and ergonomics experts
4.1 [Images]1: Provision of the alt attribute
Applies to:
- img
- area
- input type="image"
- applet
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is neither a captcha nor part of a test that would be rendered useless were an alternative to be present, continue; otherwise, the test is not applicable.
- If the element possesses an alt attribute, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H37">H37: Using alt attributes on img elements</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F65">F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image"</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
4.2 [Images]2: Relevance of the text alternative in the case of image links
Applies to:
The :: element img or any javascript that generates :: element img.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is contained within a link (an 'a' tag) or a button, continue; otherwise, the test is not applicable.
- If the element is neither a captcha nor part of a test that would be rendered useless were an alternative to be present, continue; otherwise, the test is not applicable.
- If the element possesses an alt attribute, continue; otherwise, the test is not applicable.
- If the alt attribute's content, alone or in association with the text content immediately preceding or following the img element (inside the link (an 'a' tag)), indicates clearly the link's target or action, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F89">F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
4.3 [Images]3: Relevance of the text alternative in the case of clickable regions or image based buttons
Applies to:
- area
- input type="image"
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable. <
- If the element is neither a captcha nor part of a test that would be rendered useless were an alternative to be present, continue; otherwise, the test is not applicable.
- If the element possesses an alt attribute, continue the test; otherwise, the test is not applicable.
- If the alt attribute's content identifies clearly the action or destination of the link, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H24">H24: Providing text alternatives for the area elements of image maps</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H36">H36: Using alt attributes on images used as submit buttons</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
4.4 [Images]4: Relevance of the text alternative to non-text elements
Applies to:
- img
- applet
- object
- embed
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is contained within a link (an 'a' tag) or a button, continue; otherwise, the test is not applicable.
- If the element visually transmits information, continue; otherwise, the test is not applicable.
- If the element does not consist of audio content, video animation, multimedia, a captcha or a test that would be rendered useless were an alternative to be present , continue; otherwise, the test is not applicable.
- If the totality of the information conveyed by the element is re-transcribed by at least one of the following means:
- the content of the alt attribute
- the alternative content, given before the closing of the element, in the case of an object element
- the alternative content in the element noembed, in the case of the embed element
- the alt attribute's content of one of the images in a group of images making up a whole
- the text content immediately preceding or following the element
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G95">G95: Providing short text alternatives that provide a brief description of the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G194">G194: Providing spell checking and suggestions for text input</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F13">F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F30">F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text)</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F38">F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F39">F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 1.4.1 Use of Color – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
4.5 [Images]5: Appropriateness of the empty text alternative to decorative elements
Applies to:
- img
- applet
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is only for decoration, continue; otherwise, the test is not applicable.
- If the element is not part of link (link (an 'a' tag)) or a button, continue; otherwise, the test is not applicable.
- If the element possesses an alt attribute vide, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H67">H67: Using null alt text and no title attribute on img elements for images that AT should ignore</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F38">F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F39">F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
4.6 [Images]6: Length of text alternatives
Applies to:
Any element having an alt attribute.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the alt attribute's content non-empty, continue; otherwise, the test is not applicable.
- If the alt attribute's content is as brief as possible, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G194">G194: Providing spell checking and suggestions for text input</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
4.7 [Images]7: Existence of a long description for images, when necessary
Applies to:
The img element or any javascript that generates an img element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element needs a long description, continue; otherwise, the test is not applicable.
- If a long description is present on the page, or on another page, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G73">G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G74">G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G92">G92: Providing long description for non-text content that serves the same purpose and presents the same information</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F67">F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
4.8 [Images]8: Relevance of the long description for images that need it
Applies to:
The img element or any javascript that generates an img element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element needs a long description, continue; otherwise, the test is not applicable.
- If all the information conveyed by the element is made available via a long description, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G73">G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G74">G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G92">G92: Providing long description for non-text content that serves the same purpose and presents the same information</a>
</ul>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F67">F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Editors and content providers
4.9 [Images]9: Provision of the longdesc attribute to link an image to its long description
Applies to:
The img element or any javascript that generates an img element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element needs a long description to be understood, continue; otherwise, the test is not applicable.
- If the content right next to the element doesn't contain a link giving access to the long description of the element, continue; otherwise, the test is not applicable.
- If the element has at least one of the following:
- longdesc attribute
- alt attribute
- If the content of the longdesc attribute or the alt attribute gives the location of the long description, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G73">G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H45">H45: Using longdesc</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text Content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text Content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
4.10 [Images]10: Provision of contextual information and a means of access for Captcha when the alternative cannot be communicated
Applies to:
- img
- applet
- embed
- object
- input type="image"
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is neither a captcha nor part of a test that would be rendered useless were an alternative to be present, continue; otherwise, the test is not applicable.
- If a functional or use related name, a title, or a summary (of the content, of the process or of the possible ways of obtaining information about the element) is available and as long as an alternative solution is available, permitting access to the function or protected content, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G100">G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G143">G143: Providing a text alternative that describes the purpose of the CAPTCHA</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G144">G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
4.11 [Images]11: Coherence of text alternatives and form labels across the site
Applies to:
All navigation bars as well as the following elements
- applet
- object
- img
- input type="image"
- input type="text"
- input type="checkbox"
- input type="file"
- input type="radio"
- input type="password"
- select
- textarea
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is present many times in the page, or over many pages, continue; otherwise, the test is not applicable.
- If the role played by the element is the same across all of its instantiations (on the same page or over many pages), continue; otherwise, the test is not applicable.
- If the element is identifiable in a coherent way every time it appears, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G197">G197: Using labels, names, and text alternatives consistently for content that has the same functionality</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F31">F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.2.4 Consistent Identification – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-consistent-functionality.html" title="Understanding success criterion 3.2.4: Consistent Identification">Understanding success criterion 3.2.4</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Developers and integrators
5.1 [Multimedia]1: Access to summary information for audio content, animated graphics or synchronized media
Applies to:
- img in gif format, apng or mng
- applet
- object
- embed
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is contained within a link (an 'a' tag) or a button, continue; otherwise, the test is not applicable.
- If the element is information bearing, continue; otherwise, the test is not applicable.
- If the element is identifiable by a name referring to its use or function, a title, a resume of its contents, of the process or actions possible via at least one of the following:
- the content of the alt attribute
- the alternative content, given before the closing of the element, in the case of an object element
- the alternative content in the element noembed, in the case of the embed element
- the alt attribute's content of one of the images in a group of images making up a whole
- the text content immediately preceding or following the element
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G68">G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G100">G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.2 [Multimedia]2: Provision of a text transcription for audio content, animated graphics or synchronized media
Applies to:
- a
- area
- applet
- object
- embed
- all javascript code generating one of the preceding elements or provoking a download
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element concerns download or consultation of sound, animated visual or synchronized media content that is information bearing, continue; otherwise, the test is not applicable.
- If the animated visual, sound, or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If the animated visual or synchronized media content does not already have a synchronized audio description that is complete with respect to the visual content, continue; otherwise, the test is not applicable.
- If a textual transcription of the animated visual, sound, or synchronized media content is present in the page, or downloadable from the page, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G58">G58: Placing a link to the alternative for time-based media immediately next to the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G69">G69: Providing an alternative for time based media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G158">G158: Providing an alternative for time-based media for audio-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G159">G159: Providing an alternative for time-based media for video-only content</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.1 Audio-only and Video-only (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.3 [Multimedia]3: Relevance of the text transcription for audio content, animated graphics or synchronized media
Applies to:
Any text segment acting as a transcription for animated visual, sound, or synchronized media content.
Test procedure
- If the element mentioned in the domain of application is present in the page or in a downloadable file, continue; otherwise, the test is not applicable.
- If the element gives access to the same information as the animated visual, sound, or synchronized media content, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G69">G69: Providing an alternative for time based media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G158">G158: Providing an alternative for time-based media for audio-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G159">G159: Providing an alternative for time-based media for video-only content</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.1 Audio-only and Video-only (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.8 Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-text-doc.html" title="Understanding success criterion 1.2.8: Media Alternative (Prerecorded)">Understanding success criterion 1.2.8</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.4 [Multimedia]4: Provision of a synchronized audio description or a textual transcription for animated visual content and synchronized media
Applies to:
- a
- area
- applet
- object
- embed
- all javascript code generating one of the preceding elements or provoking a download
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element concerns a download or restitution of animated visual or multimedia content bearing information, continue; otherwise, the test is not applicable.
- If the animated visual or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If the animated visual or synchronized media content does not already have a synchronized audio description that is complete with respect to the visual content, continue; otherwise, the test is not applicable.
- If element's content needs a synchronized audio description in order for it to be understood, continue; otherwise, the test is not applicable.
- If at least one version of the element is accompanied by a synchronized audio description, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G78">G78: Providing a second, user-selectable, audio track that includes audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G173">G173: Providing a version of a movie with audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM1">SM1: Adding extended audio description in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM2">SM2: Adding extended audio description in SMIL 2.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM6">SM6: Providing audio description in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM7">SM7: Providing audio description in SMIL 2.0</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
</ul>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.5 [Multimedia]5: Relevance of the synchronized audio description to the animated visual content or synchronized media
Applies to:
All audio content serving as a description to the animated visual content or synchronized media.
Test procedure
- If the element listed in the domain of application is present, continue; otherwise, the test is not applicable.
- If the element provides sufficient information as regards the animated visual content or synchronized media (texts displayed on the screen, visual actions, attitudes, visually apparent emotions, gestures, scene changes, etc.), the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G8">G8: Providing a movie with extended audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G78">G78: Providing a second, user-selectable, audio track that includes audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G166">G166: Providing audio that describes the important video content and describing it as such</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G173">G173: Providing a version of a movie with audio descriptions</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.1 Audio-only and Video-only (Prerecorded)– <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.5 Audio Description (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc-only.html" title="Understanding success criterion 1.2.5: Audio Description (Prerecorded)">Understanding success criterion 1.2.5</a>
- 1.2.7 Extended Audio Description (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-extended-ad.html" title="Understanding success criterion 1.2.7: Extended Audio Description (Prerecorded)">Understanding success criterion 1.2.7</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.6 [Multimedia]6: Possibility of controlling the activation of the synchronized audio description
Applies to:
- a
- area
- applet
- object
- embed
- all javascript code generating one of the preceding elements or provoking a download
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element concerns the display or download of multimedia content, continue; otherwise, the test is not applicable.
- If at least one version of the element is accompanied by a synchronized audio description, continue; otherwise, the test is not applicable.
- If synchronized audio description can be turned on or off, regardless of the device (mouse, keyboard, etc.), the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G78">G78: Providing a second, user-selectable, audio track that includes audio descriptions</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.5 Audio Description (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc-only.html" title="Understanding success criterion 1.2.5: Audio Description (Prerecorded)">Understanding success criterion 1.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.7 [Multimedia]7: Provision of an extended synchronized audio description for animated visual content and synchronized media
Applies to:
- a
- area
- applet
- object
- embed
- all javascript code generating one of the preceding elements or provoking a download
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element concerns a download or restitution of animated visual or multimedia content bearing information, continue; otherwise, the test is not applicable.
- If the animated visual or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If element's content needs a synchronized audio description in order for it to be understood, continue; otherwise, the test is not applicable.
- If the length of the pauses in the soundtrack of the animated visual or synchronized media content make it impossible to include all of the necessary information, continue; otherwise, the test is not applicable.
- If at least one version of the element is accompanied by an extended audio description, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G8">G8: Providing a movie with extended audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM1">SM1: Adding extended audio description in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM2">SM2: Adding extended audio description in SMIL 2.0</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.7 Extended Audio Description (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-extended-ad.html" title="Understanding success criterion 1.2.7: Extended Audio Description (Prerecorded)">Understanding success criterion 1.2.7</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.8 [Multimedia]8: Provision of a synchronized audio description for animated visual content and synchronized media
Applies to:
- a
- area
- applet
- object
- embed
- all javascript code generating one of the preceding elements or provoking a download
Test procedure
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element concerns a download or restitution of animated visual or multimedia content bearing information, continue; otherwise, the test is not applicable.
- If the animated visual or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If element's content needs a synchronized audio description in order for it to be understood, continue; otherwise, the test is not applicable.
- If at least one version of the element is accompanied by an synchronized audio description, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G78">G78: Providing a second, user-selectable, audio track that includes audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G173">G173: Providing a version of a movie with audio descriptions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM6">SM6: Providing audio description in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM7">SM7: Providing audio description in SMIL 2.0</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.5 Audio Description (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc-only.html" title="Understanding success criterion 1.2.5: Audio Description (Prerecorded)">Understanding success criterion 1.2.5</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.9 [Multimedia]9: Provision of synchronized sub-titles for synchronized media that is not a live broadcast
Applies to:
- a
- applet
- object
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element concerns a download or restitution of animated visual or multimedia content bearing information, continue; otherwise, the test is not applicable.
- If this synchronized media is not a live broadcast, continue; otherwise, the test is not applicable.
- If the synchronized media is not an animated visual, audio or synchronized media alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If the synchronized media requires synchronized sub-titles for it to be understood, continue; otherwise, the test is not applicable.
- If at least one version of the synchronized media is accompanied by synchronized sub-titles, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G9">G9: Creating captions for live synchronized media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G87">G87: Providing closed captions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G93">G93: Providing open (always visible) captions</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F75">F75: Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.2 Captions (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-captions.html" title="Understanding success criterion 1.2.2: Captions (Prerecorded)">Understanding success criterion 1.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.10 [Multimedia]10: Relevance of the synchronized sub-titles to the synchronized media
Applies to:
Any textual content serving as synchronized sub-titles for synchronized media.
Test procedure
- If the element listed in the domain of application is present, continue; otherwise, the test is not applicable.
- If the element provides sufficient information for the understanding of the synchronized media's content (spoken words, noises, musical elements, intonations, change of speakers, etc.), the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G9">G9: Creating captions for live synchronized media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM1">SM1: Adding extended audio description in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM12">SM12: Providing captions through synchronized text streams in SMIL 2.0</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F8">F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.2 Captions (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-captions.html" title="Understanding success criterion 1.2.2: Captions (Prerecorded)">Understanding success criterion 1.2.2</a>
- 1.2.4 Captions (Live) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-real-time-captions.html" title="Understanding success criterion 1.2.4: Captions (Live)">Understanding success criterion 1.2.4</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.11 [Multimedia]11: Provision of an alternative for all applet or object elements
Applies to:
- applet
- object
- all javascript code generating one of the preceding elements
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is information-bearing, continue; otherwise, the test is not applicable.
- If the animated visual, audio or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If the content will not be consulted in a controlled computing environment where the rendering of object and applet content can be absolutely assured, continue; otherwise, the test is not applicable.
- If an alternative to the element is available in one of the following ways:
- between the opening and closing tags of the element
- in the alt attribute for the applet element
- outside the element, via a link ('a' tag), an area element or directly in the page content
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G58">G58: Placing a link to the alternative for time-based media immediately next to the non-text content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G69">G69: Providing an alternative for time based media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G158">G158: Providing an alternative for time-based media for audio-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G159">G159: Providing an alternative for time-based media for video-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H27">H27: Providing text and non-text alternatives for object</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H35">H35: Providing text alternatives on applet elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H53">H53: Using the body of the object element</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 1.2.1 Audio-only and Video-only (Prerecorded)– <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.8 Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-text-doc.html" title="Understanding success criterion 1.2.8: Media Alternative (Prerecorded)">Understanding success criterion 1.2.8</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.12 [Multimedia]12: Provision of an alternative for embedded objects
Applies to:
The embed element or any javascript that generates an embed element.
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is information-bearing, continue; otherwise, the test is not applicable.
- If the animated visual, audio or synchronized media content is not an alternative to textual content already present in the page, identified as such and containing no additional information with respect to the textual content concerned, continue; otherwise, the test is not applicable.
- If the content will not be consulted in a controlled computing environment where the rendering of object and applet content can be absolutely assured, continue; otherwise, the test is not applicable.
- If an alternative to the element is available in one of the following ways:
- via a noembed tag
- outside the embed element, via a link ('a' tag), an area element or directly in the page content
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G69">G69: Providing an alternative for time based media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G158">G158: Providing an alternative for time-based media for audio-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G159">G159: Providing an alternative for time-based media for video-only content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H46">H46: Using noembed with embed</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F74">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 1.2.1 Audio-only and Video-only (Prerecorded)– <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.8 Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-text-doc.html" title="Understanding success criterion 1.2.8: Media Alternative (Prerecorded) ">Understanding success criterion 1.2.8</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.13 [Multimedia]13: The page is free of any element that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
Applies to:
- object
- embed
- applet
- img in gif format, apng or mng
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element provokes sudden changes in brightness or red flash behavior, continue; otherwise, the test is not applicable.
- If the sudden changes in brightness or red flash remain at a frequency of 3Hz or less, or the total surface affected by the sudden changes in brightness or red flash in a 341 x 256 pixel zone covers less than 25% of that zone (21 284 pixels), the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G15">G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G19">G19: Ensuring that no component of the content flashes more than three times in any 1-second period</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.3.1 Three Flashes or Below Threshold – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/seizure-does-not-violate.html" title="Understanding success criterion 2.3.1: Three Flashes or Below Threshold">Understanding success criterion 2.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.14 [Multimedia]14: The page is free of any javascript code that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
Applies to:
All javascript used in the page.
Test procedure
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes sudden changes in brightness or red flash behavior, continue; otherwise, the test is not applicable.
- If the sudden changes in brightness or red flash remain at a frequency of 3Hz or less, or the total surface affected by the sudden changes in brightness or red flash in a 341 x 256 pixel zone covers less than 25% of that zone (21 284 pixels), the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G15">G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G19">G19: Ensuring that no component of the content flashes more than three times in any 1-second period</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F17">F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F68">F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F82">F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F86">F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.3.1 Three Flashes or Below Threshold – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/seizure-does-not-violate.html" title="Understanding success criterion 2.3.1: Three Flashes or Below Threshold">Understanding success criterion 2.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.15 [Multimedia]15: The page is free of any style layout that provokes sudden changes in brightness or causes red flash behavior beyond the threshold frequency
Applies to:
Any element subject to style declarations that contain one or more of the following properties:
- background
- background-image
- content
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the layout of the element provokes sudden changes in brightness or red flash behavior, continue; otherwise, the test is not applicable.
- If the sudden changes in brightness or red flash remain at a frequency of 3Hz or less, or the total surface affected by the sudden changes in brightness or red flash in a 341 x 256 pixel zone covers less than 25% of that zone (21 284 pixels), the test is successful; otherwise, it fails. </
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G15">G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G19">G19: Ensuring that no component of the content flashes more than three times in any 1-second period</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.3.1 Three Flashes or Below Threshold – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/seizure-does-not-violate.html" title="Understanding success criterion 2.3.1: Three Flashes or Below Threshold">Understanding success criterion 2.3.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.16 [Multimedia]16: Compatibility of all programmed elements with respect to assistive technology
Applies to:
- objet
- applet
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is not accessible for assistive technology via an accessibility API or accessibility features, continue; otherwise, the test is not applicable.
- If the features contained within the element are available through an accessible alternative, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G10">G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G135">G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F79">F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F15">F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.17 [Multimedia]17: Total absence of sudden changes in brightness or red flash behavior beyond the threshold frequency
Applies to:
All javascript used in the page and any element selected by style declarations that contain one or more of the following properties:
- background
- background-image
- content
In addition to the following elements:
- applet
- object
- embed
- img in gif format, apng or mng
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element provokes sudden changes in brightness or red flash behavior, continue; otherwise, the test is not applicable.
- If the sudden changes in brightness or red flash remain at a frequency of 3Hz or less, the test is successful; otherwise, it fails. </
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G19">G19: Ensuring that no component of the content flashes more than three times in any 1-second period</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.3.2 Three Flashes – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/seizure-three-times.html" title="Understanding success criterion 2.3.2: Three Flashes">Understanding success criterion 2.3.2</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Graphic designers and ergonomics experts
- Editors and content providers
5.18 [Multimedia]18: Provision of synchronized sub-titles for live sound or synchronized media
Applies to:
- a
- applet
- object
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element concerns a download or restitution of synchronized media or audio content bearing information, continue; otherwise, the test is not applicable.
- If this synchronized media or audio content is a live broadcast, continue; otherwise, the test is not applicable.
- If the synchronized media or audio content needs synchronized subtitles in order to be understood, continue; otherwise, the test is not applicable.
- If at least one version of the synchronized media or audio content is accompanied by synchronized sub-titles or a textual transcription containing the same information is available at the moment of the live broadcast (example, a live speech, written in advance), the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G9">G9: Creating captions for live synchronized media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G151">G9: Creating captions for live synchronized media</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G157">G157: Incorporating a live audio captioning service into a Web page</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM11">SM11: Providing captions through synchronized text streams in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM12">SM12: Providing captions through synchronized text streams in SMIL 2.0</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.4 Captions (Live): – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-real-time-captions.html" title="Understanding success criterion 1.2.4: Captions (Live):">Understanding success criterion 1.2.4</a>
- 1.2.9 Audio-only (Live) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-live-audio-only.html" title="Understanding success criterion 1.2.9: Audio-only (Live)">Understanding success criterion 1.2.9</a>
Corresponding WCAG level
Level AA
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.19 [Multimedia]19: Absence of the blink element
Applies to:
The blink element.
Test procedure
If the page contains no blink tag, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G11">G11: Creating content that blinks for less than 5 seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G187">G187: Using a technology to include blinking content that can be turned off via the user agent</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F47">F47: Failure of Success Criterion 2.2.2 due to using the blink element</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.20 [Multimedia]20: The page is free of elements that cause automatically initiated and unstoppable blinking effects
Applies to:
- object
- embed
- applet
- img with a gif, apng, or mng suffix
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element provokes blinking phenomena unsolicited by the user, continue; otherwise, the test is not applicable.
- If the blinking phenomena conveys no actual information, or if this information could be transmitted by other means, non-blinking, continue; otherwise, the test is not applicable.
- If the user can control the blinking in at least one of the following ways:
- possibility to stop and restart the blinking
- the blinking lasts for five seconds maximum
- possibility to hide temporarily the blinking content
- possibility to display all of the blinking content without any blinking
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G11">G11: Creating content that blinks for less than 5 seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G152">G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds)</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G187">G187: Using a technology to include blinking content that can be turned off via the user agent</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F7">F7: Failure of Success Criterion 2.2.2 due to an object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than five seconds</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.21 [Multimedia]21: The page is free of javascript that causes automatically initiated and unstoppable blinking effects
Applies to:
All javascript code in the page.
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes blinking in absence of any user action, continue; otherwise, the test is not applicable.
- If the blinking phenomena conveys no actual information, or if this information could be transmitted by other means, non-blinking, continue; otherwise, the test is not applicable.
- possibility to stop and restart the blinking
- the blinking lasts for five seconds maximum
- possibility to hide temporarily the blinking content
- possibility to display all of the blinking content without any blinking
li>If the user can control the blinking in at least one of the following ways:
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G11">G11: Creating content that blinks for less than 5 seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G187">G187: Using a technology to include blinking content that can be turned off via the user agent</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR22">SCR22: Using scripts to control blinking and stop it in five seconds or less</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F50">F50: Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.22 [Multimedia]22: The page is free of all style layouts that cause automatically initiated and unstoppable blinking effects
Applies to:
Any element selected by style declarations that contain one or more of the following properties:
- background
- background-image
- content
- text-decoration with the value blink
Test procedure
- If the layout of the element provokes blinking in absence of any user action, continue; otherwise, the test is not applicable.
- If the blinking phenomena conveys no actual information, or if this information could be transmitted by other means, non-blinking, continue; otherwise, the test is not applicable.
- possibility to stop and restart the blinking
- the blinking lasts for five seconds maximum
- possibility to hide temporarily the blinking content
- possibility to display all of the blinking content without any blinking
li>If the user can control the blinking in at least one of the following ways:
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G11">G11: Creating content that blinks for less than 5 seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G187">G187: Using a technology to include blinking content that can be turned off via the user agent</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F4">F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.23 [Multimedia]23: Absence of the marquee element
Applies to:
The marquee element.
Test procedure
If there is no marquee element in the page, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F16">F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.24 [Multimedia]24: The page is free of elements displaying automatically initiated and unstoppable motion effects
Applies to:
- object
- embed
- applet
- img in gif format, apng or mng
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element displays movement without any user interaction, continue; otherwise, the test is not applicable.
- If the movement conveys no actual information, or if this information could be transmitted by other means, motionless, continue; otherwise, the test is not applicable.
- possibility to stop and restart the movement
- the movement lasts for five seconds maximum
- possibility to hide temporarily the moving content
- possibility to display all of the moving content without any movement
li>If the user can control the movement in at least one of the following ways:
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G4">G4: Allowing the content to be paused and restarted from where it was paused</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G152">G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds)</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F16">F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.25 [Multimedia]25: The page is free of all javascript code that causes automatically initiated and unstoppable motion effects
Applies to:
All javascript code in the page.
Test procedure
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes movement without any user interaction, continue; otherwise, the test is not applicable.
- If the movement conveys no actual information, or if this information could be transmitted by other means, motionless, continue; otherwise, the test is not applicable.
- possibility to stop and restart the movement
- the movement lasts for five seconds maximum
- possibility to hide temporarily the moving content
- possibility to display all of the moving content without any movement
li>If the user can control the movement in at least one of the following ways:
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G4">G4: Allowing the content to be paused and restarted from where it was paused</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F16">F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.26 [Multimedia]26: The page is free of all style layouts that cause automatically initiated and unstoppable motion effects
Applies to:
Any element selected by style declarations that contain one or more of the following properties:
- background
- background-image
- content
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the layout of the element provokes movement without any user interaction, continue; otherwise, the test is not applicable.
- If the movement conveys no actual information, or if this information could be transmitted by other means, motionless, continue; otherwise, the test is not applicable.
- possibility to stop and restart the movement
- the movement lasts for five seconds maximum
- possibility to hide temporarily the moving content
- possibility to display all of the moving content without any movement
li>If the user can control the movement in at least one of the following ways:
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G4">G4: Allowing the content to be paused and restarted from where it was paused</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G186">G186: Using a control in the Web page that stops moving, blinking, or auto-updating content</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F16">F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.27 [Multimedia]27: Device independence for object, embed and applet elements
Applies to:
- object
- embed
- applet
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element's interface cannot be used with a pointing-device, such as the mouse, as well as by at least one of the following techniques:
- keyboard shortcuts
- keyboard navigation within the interfaces, from element to element
- If an accessible alternative containing the same information is present in the page, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G90">G90: Providing keyboard-triggered event handlers</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.28 [Multimedia]28: Provision of an alternative for any object, embed or applet element that is device dependent
Applies to:
- object
- embed
- applet
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element is instrumental for the information conveyed by the page, continue; otherwise, the test is not applicable.
- If the information conveyed by the element cannot be obtained via a pointing-device, such as the mouse, as well as by at least one of the following techniques:
- keyboard shortcuts
- keyboard navigation within the interfaces, from element to element
- If the element has an alternative containing the same information and accessible regardless of the device being used, either in or from the page, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F15">F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely</a> </a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a> </a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F54">F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.29 [Multimedia]29: The page is free of any element that initiates unstoppable audio output
Applies to:
- object
- embed
- applet
- tout code javascript used in the page
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element provokes an audio output, continue; otherwise, the test is not applicable.
- If the sound can be stopped or its duration is less than or equal to 3 seconds, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G60">G60: Playing a sound that turns off automatically within three seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G170">G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G171">G171: Playing sounds only on user request</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F23">F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.2 Audio Control – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-dis-audio.html" title="Understanding success criterion 1.4.2: Audio Control">Understanding success criterion 1.4.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.30 [Multimedia]30: Absence of the bgsound element
Applies to:
The bgsound element.
Test procedure
If there is no bgsound element in the page, or if audio associated with the element has a duration of 3 seconds maximum, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G60">G60: Playing a sound that turns off automatically within three seconds</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G171">G171: Playing sounds only on user request</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.2 Audio Control – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-dis-audio.html" title="Understanding success criterion 1.4.2: Audio Control">Understanding success criterion 1.4.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
5.31 [Multimedia]31: Provision of a version signed in French sign language facilitating understanding of synchronized media
Applies to:
- a
- area
- applet
- embed
- object
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element makes available (for display or download) a version in French sign language, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G54">G54: Including a sign language interpreter in the video stream</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G79">G79: Providing a spoken version of the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G103">G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G121">G121: Linking to pronunciations</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM13">SM13: Providing sign language interpretation through synchronized video streams in SMIL 1.0</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SM14">SM14: Providing sign language interpretation through synchronized video streams in SMIL 2.0</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.6 Sign Language (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-sign.html" title="Understanding success criterion 1.2.6: Sign Language (Prerecorded))">Understanding success criterion 1.2.6</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
- Editors and content providers
5.32 [Multimedia]32: Relevance of the sign language version
Applies to:
- a
- area
- applet
- embed
- object
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element makes available (for display or download) a complementary version of the content in sign language, continue; otherwise, the test is not applicable.
- If this complementary content, in sign language, conveys all of the information in the original content, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G54">G54: Including a sign language interpreter in the video stream</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G81">G81: Providing a synchronized video of the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G160">G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.2.6 Sign Language (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-sign.html" title="Understanding success criterion 1.2.6: Sign Language (Prerecorded))">Understanding success criterion 1.2.6</a>
- 3.1.5 Reading Level – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-supplements.html" title="Understanding success criterion 3.1.5: Reading Level">Understanding success criterion 3.1.5</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Editors and content providers
5.33 [Multimedia]33: Sound volume of audio tracks
Applies to:
- a
- area
- applet
- object
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element allows for the playing or downloading of an element that contains at least one spoken word soundtrack conveying information and at least one background sound track, continue; otherwise, the test is not applicable.
- If the soundtrack(s) of spoken word information are 20 decibels louder than the background soundtracks, or if the background soundtrack can be deactivated, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G56">G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.7 Low or No Background Audio – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-noaudio.html" title="Understanding success criterion 1.4.7: Low or No Background Audio">Understanding success criterion 1.4.7</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
5.34 [Multimedia]34: It is possible to change the foreground and background colors in text blocks
Applies to:
- applet
- object
- embed
- any html element
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element displays text-blocks, continue; otherwise, the test is not applicable.
- If there is a means made available for personalizing the foreground and background color of text-blocks, the test is successful; otherwise, it fails.
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G156">G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G175">G175: Providing a multi-color selection tool on the page for foreground and background colors</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
Corresponding WCAG level
Level AAA
This checkpoint concerns:
- Developers and integrators
Applies to:
- img
- input type="image"
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element has an ismap attribute or is used as an image with server-side clickable regions, continue; otherwise, the test is not applicable.
- If each clickable region of the element is doubled by a text link pointing to the same destination, continue; otherwise, the test is not applicable.
- If these links, grouped together or otherwise, are present directly after the element concerned, then the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F54">F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
- a
- form
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element has a target attribute, continue; otherwise, the test is not applicable.
- If the target attribute's content is something other than _top, _parent, or _self, continue; otherwise, the test is not applicable.
- If the element does not have, as its only child element an img element, continue the test, otherwise the test is not applicable.
- If a warning signaling the new window is contained within the content of the element or if such a warning is given by :
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the content of the title attribute of the element as long as this is longer than the link text itself
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H83">H83: Using the target attribute to open a new window on user request and indicating this in link text</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F22">F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
- 'a' tags containing only an img element
- area
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element has a target attribute, continue; otherwise, the test is not applicable.
- If the target attribute's content is something other than _top, _parent, or _self, continue; otherwise, the test is not applicable.
- If the element has an alt attribute, continue the test, otherwise the test is not applicable.
- If the content of the alt attribute or other content provided in one of the following ways :
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR24">SCR24: Using progressive enhancement to open new windows on user request</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
All javascript code in the page.
Test procedure
- If javascript code is present in the page, continue; otherwise, the test is not applicable.
- If the javascript code opens a new window, continue; otherwise, the test is not applicable.
- If the content of the element to which the javascript code applies does not warn about the new window, continue; otherwise, the test is not applicable.
- If the content of the element serving as the link text, corresponding to one of the following contexts :
- the element's text content + the content of its parent element, if we are dealing with a p or li
- the element's text content + the content of a header (an Hx tag) immediately preceding the element
- the element's text content + the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the element's text content + the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the element's title attribute's content
- the content of the alt attribute in the case of images or clickable regions
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR24">SCR24: Using progressive enhancement to open new windows on user request</a>
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
All javascript code in the page.
Test procedure
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If, without any user interaction, the javascript code does not provoke a new window opening, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G107">G107: Using "activate" rather than "focus" as a trigger for changes of context</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F22">F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F52">F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F55">F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F60">F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 3.2.1: On Focus – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-receive-focus.html" title="Understanding success criterion 3.2.1: On Focus">Understanding success criterion 3.2.1</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
Any element that can receive keyboard focus.
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If during keyboard navigation, upon arriving on an element, it transpires that we are unable to move the focus forward or backward using the keyboard (tabulation, arrow keys) to the adjacent element that should be able to receive the focus,, continue; otherwise, the test is not applicable.
- If it has been indicated by which specific actions it is possible to move to the preceding or subsequent element and if these actions indeed give the desired result, the test is successful; otherwise, it fails.
Test level
Difficult
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G21">G21: Ensuring that users are not trapped in content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H91">H91: Using HTML form controls and links</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F10">F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.1.2 No Keyboard Trap – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-trapping.html" title="Understanding success criterion 2.1.2: No Keyboard Trap">Understanding success criterion 2.1.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
Any meta element meta having an http-equiv attribute with value "refresh".
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a content attribute is present in the element, continue; otherwise, the test is not applicable.
- If the content attribute has a whole number value greater than 0 and less than 72,000, continue; otherwise, the test is not applicable.
- If the refresh time limit cannot be deleted without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the content attribute has a second url value containing a URL that is different from the current page/resource, or that the refresh time limit cannot be removed without fundamentally changing the information or functionality of the content, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F61">F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
All javascript code in the page.
Test procedure
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes an automatic page refresh, continue; otherwise, the test is not applicable.
- If the automatic refresh cannot be removed without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the user retains the control over the refresh by at least one of the following mechanisms :
- possibility to stop and to restart the refresh
- possibility to freely adjust the duration before the refresh to at least 10 times as long as that initially intended
- possibility, during a preliminary period of no less than 20 seconds, to push back the refresh, delaying it until a later moment
- the refresh is not effected before twenty hours have elapsed
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F61">F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
- server side scripts (session expirations, http refresh headers)
- applet
- object
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element provokes an automatic refresh of the page, continue; otherwise, the test is not applicable.
- If the automatic refresh cannot be removed without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the user retains some control over the refresh, via one of the following mechanisms :
- possibility to stop and to restart the refresh
- possibility to freely adjust the duration before the refresh to at least 10 times as long as that initially intended
- possibility, during a preliminary period of no less than 20 seconds, to push back the refresh, delaying it until a later moment
- the refresh is not effected before twenty hours have elapsed
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F58">F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.2 Pause, Stop, Hide – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-pause.html" title="Understanding success criterion 2.2.2: Pause, Stop, Hide">Understanding success criterion 2.2.2</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
Any meta element meta having an http-equiv attribute with value "refresh".
Test procedure
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a content attribute is present in the element, continue; otherwise, the test is not applicable.
- If the content attribute has a whole number value greater than 0 and less than 72,000, continue; otherwise, the test is not applicable.
- If the refresh time limit cannot be deleted without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the content attribute has a second url value containing a URL equal to that of the current page/resource, or that the redirection time limit cannot be removed without fundamentally changing the information or functionality of the content, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H76">H76: Using meta refresh to create an instant client-side redirect</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SVR1">SVR1: Implementing automatic redirects on the server side instead of on the client side</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F40">F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit </a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F41">F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 2.2.4 Interruptions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-postponed.html" title="Understanding success criterion 2.2.4: Interruptions">Understanding success criterion 2.2.4</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
All javascript code in the page.
Test procedure
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes an automatic redirect of the page, continue; otherwise, the test is not applicable.
- If the automatic redirect cannot be removed without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the user retains some control over the redirect, via one of the following mechanisms :
- possibility to stop the redirect/li>
- possibility to freely adjust the duration before the redirect to at least 10 times as long as that initially intended
- possibility, during a preliminary period of no less than 20 seconds, to push back the redirect, delaying it until a later moment
- the redirect is not effected before twenty hours have elapsed
Test level
Medium
WCAG techniques
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR1SCR1: Allowing the user to extend the default time limit a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SVR1">SVR1: Implementing automatic redirects on the server side instead of on the client side</a>
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F58">F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
- server side scripts (session expirations, http refresh headers)
- applet
- object
- embed
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element provokes an automatic redirection of the page, continue; otherwise, the test is not applicable.
- If the automatic direction cannot be removed without fundamentally changing the information or functionality of the content, continue; otherwise, the test is not applicable.
- If the user retains some control over the redirection, via one of the following mechanisms :
- possibility to stop the redirection
- possibility to freely adjust the duration before the refresh to at least 10 times as long as that initially intended
- possibility, during a preliminary period of no less than 20 seconds, to push back the redirection, delaying it until a later moment
- the redirection is not effected before twenty hours have elapsed
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F58">F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out</a>
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
- 2.2.1 Timing Adjustable – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-required-behaviors.html" title="Understanding success criterion 2.2.1: Timing Adjustable">Understanding success criterion 2.2.1</a>
Corresponding WCAG level
Level A
This checkpoint concerns:
- Developers and integrators
Applies to:
- a
- area
- button
- input type="image"
- input type="submit"
- input type="button"
- input type="reset"
Test procedure
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the link text, taken out of context allows a non-handicapped user to identify the link's action or destination, continue; otherwise, the test is not applicable.
- If the link text alone is clear as to the action or destination of the link, or if this text, with the help of additional content furnished via one of the following ways :
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the element's title attribute's content allows for the full comprehension of the link in question, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G91">G91: Providing link text that describes the purpose of a link</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H30">H30: Providing link text that describes the purpose of a link for anchor elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F63">F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- Developers and integrators
- Editors and content providers
- a
- area
- button
- input type="image"
- input type="submit"
- input type="button"
- input type="reset"
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the link text, taken out of context allows a non-handicapped user to identify the link's action or destination, continue; otherwise, the test is not applicable.
- If the link text alone is clear as to the action or destination of the link, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G91">G91: Providing link text that describes the purpose of a link</a>
- 2.4.9 Link Purpose (Link Only) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-link.html" title="Understanding success criterion 2.4.9: Link Purpose (Link Only)">Understanding success criterion 2.4.9</a>
- Developers and integrators
- Editors and content providers
- a
- area
- button
- input type="image"
- input type="submit"
- input type="reset"
- If at least two of the mentioned elements are present in the page, continue; otherwise, the test is not applicable.
- If the elements have the same text yet point to different destinations or lead to different actions, continue; otherwise, the test is not applicable.
- If the elements have identical identifiers when furnished with additional content by one of the following means:
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- If the elements have a title attribute which differs between them, and this title attribute is longer than the link text alone and it enables clear recognition of the actions or destination of the link, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G91">G91: Providing link text that describes the purpose of a link</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G197">G197: Using labels, names, and text alternatives consistently for content that has the same functionality</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H30">H30: Providing link text that describes the purpose of a link for anchor elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- 3.2.4 Consistent Identification – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-consistent-functionality.html" title="Understanding success criterion 3.2.4: Consistent Identification">Understanding success criterion 3.2.4</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- Editors and content providers
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element isn't a 'a' tag with a name or id attribute, without an href attribute nor having an href attribute whose value is the # character followed by the content of the name or id attribute, continue; otherwise, the test is not applicable.
- If a text can be obtained via one of the following ways:
- the textual content of the element
- textual alternatives of graphic elements contained within the element
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G91">G91: Providing link text that describes the purpose of a link</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H30">H30: Providing link text that describes the purpose of a link for anchor elements</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- 2.4.9 Link Purpose (Link Only) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-link.html" title="Understanding success criterion 2.4.9: Link Purpose (Link Only)">Understanding success criterion 2.4.9</a>
- Developers and integrators
- If no such page is present in the site, continue; otherwise, the test is not applicable.
- If a search engine and a navigation menu are present in the site, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G63">G63: Providing a site map</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G64">G64: Providing a Table of Contents</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If such a page is present in the site, continue; otherwise, the test is not applicable.
- If, upon this page, the links outlining the general structure of the site lead to the pages described by those links, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G63">G63: Providing a site map</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Developers and integrators
- If such a page is present in the site, continue; otherwise, the test is not applicable.
- If at least one link, available from the home page of the site, points towards the site-map page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G63">G63: Providing a site map</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G65">G65: Providing a breadcrumb trail</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If the site has neither search engine nor a site map, continue; otherwise, the test is not applicable.
- If the element listed in the domain of application is present, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H59">H59: Using the link element and navigation tools</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If the group of elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the group of elements is present on at least on one other page of the site, continue; otherwise, the test is not applicable.
- If the current page in question is not the home page of the site, continue; otherwise, the test is not applicable.
- If the page in question is the home page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G61">G61: Presenting repeated components in the same relative order each time they appear</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F66">F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages</a>
- 3.2.3 Consistent Navigation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-consistent-locations.html" title="Understanding success criterion 3.2.3: Consistent Navigation">Understanding success criterion 3.2.3</a>
- Developers and integrators
- If the group of elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the group of elements is present on at least on one other page of the site, continue; otherwise, the test is not applicable.
- If the current page in question is not the home page of the site, continue; otherwise, the test is not applicable.
- If the page in question is the home page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G61">G61: Presenting repeated components in the same relative order each time they appear</a>
- 3.2.3 Consistent Navigation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-consistent-locations.html" title="Understanding success criterion 3.2.3: Consistent Navigation">Understanding success criterion 3.2.3</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- 'a' tags with href attributes
- area
- button
- input
- object
- embed
- select
- textarea
- any element with a specified tabindex
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the keyboard trajectory between the elements mentioned in the domain of application is logically ordered, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G59">G59: Placing the interactive elements in an order that follows sequences and relationships within the content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H4">H4: Creating a logical tab order through links, form controls, and objects</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F44">F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability</a>
- 2.4.3 Focus Order – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-order.html" title="Understanding success criterion 2.4.3: Focus Order">Understanding success criterion 2.4.3</a>
- Developers and integrators
- object
- embed
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If use of use of the element leads to a new window opening, continue; otherwise, the test is not applicable.
- If the content of the element alerts the user to the new window that will open, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F22">F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
- Developers and integrators
- a
- area
- If one of the elements mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows the downloading of a document, continue; otherwise, the test is not applicable.
- If the document format is indicated in the element's text, or if it is provided by addition information given in one of the following ways:
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the element's title attribute's content
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- Developers and integrators
- a
- area
- If one of the elements mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows the downloading of a document, continue; otherwise, the test is not applicable.
- If the document size is indicated in the element's text, or if it is provided by addition information given in one of the following ways:
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the element's title attribute's content
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- Developers and integrators
- a
- area
- If one of the elements mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element allows the downloading of a document, continue; otherwise, the test is not applicable.
- If the language of the document is different to the language of the text of the element used to download the document, continue; otherwise, the test is not applicable.
- If the language of the document is indicated in the element's text, or if it is provided by addition information given in one of the following ways:
- the content of its parent element, if we are dealing with a p or li
- the content of a header (an Hx tag) immediately preceding the element
- the associated table header (th) content in the case that we are dealing with data in a table cell (td)
- the content of parent list elements where we have lists (ul,ol,dl) arranged in a treelike way
- the element's title attribute's content
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H33">H33: Supplementing link text with the title attribute</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- Developers and integrators
- Editors and content providers
- If the element listed in the domain of application is present at least twice in the page, continue; otherwise, the test is not applicable.
- If the link is part of an important grouping (navigation, repeated content, tool zone, etc.), continue; otherwise, the test is not applicable.
- If the link is contained by a parent element, along with the other links of the same group, without being mixed with links of a different grouping, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H50">H50: Using map to group links</a>
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If an anchor is defined for the element by at least one of the following techniques:
- the presence of a non-empty id attribute on the element itself
- the presence of an 'a' element, with a non-empty name or id attribute, being the immediately preceding element of the same level
- the presence of an 'a' element, with a non-empty name or id attribute, being the first child of the element
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H50">H50: Using map to group links</a>
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a non-empty 'a' element gives access to the anchor, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G1">G1: Adding a link at the top of each page that goes directly to the main content area</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G123">G123: Adding a link at the beginning of a block of repeated content to go to the end of the block</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G124">G124: Adding links at the top of the page to each area of the content</a>
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element leads or gives access to a group of links that are important, continue; otherwise, the test is not applicable.
- If the link element in question leads to the specified location, and provided that keyboard navigation can be easily continued from that point on, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G53">G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence</a>
- 2.4.3 Focus Order – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-order.html" title="Understanding success criterion 2.4.3: Focus Order">Understanding success criterion 2.4.3</a>
- Developers and integrators
- If the element listed in the domain of application is present at least twice in the page, continue; otherwise, the test is not applicable.
- If the element leads or gives access to a group of links that are important, continue; otherwise, the test is not applicable.
- If the link element in question leads to the specified location, and provided that keyboard navigation can be easily continued from that point on, the test is successful; otherwise, it fails.
- If the order of all such elements in the page source is always the same, the test is successful; otherwise, it fails. </ol>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F66">F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages</a>
- 3.2.3 Consistent Navigation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-consistent-locations.html" title="Understanding success criterion 3.2.3: Consistent Navigation">Understanding success criterion 3.2.3</a>
- Developers and integrators
- If no search engine is present in the site, continue; otherwise, the test is not applicable.
- If a site map and a navigation menu are present in the site, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G161">G161: Providing a search function to help users find content</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- Developers and integrators
- If a group of pages exists in the site, continue; otherwise, the test is not applicable.
- If there are links facilitating navigation within this group of pages, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G64">G64: Providing a Table of Contents</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G125">G125: Providing links to navigate to related Web pages</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G126">G126: Providing a list of links to all other Web pages</a>
- 2.4.5 Multiple Ways – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-mult-loc.html" title="Understanding success criterion 2.4.5: Multiple Ways">Understanding success criterion 2.4.5</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the page currently open is indicated in the navigation menu, via a special formatting of the item, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G128">G128: Indicating current location within navigation bars</a>
- 2.4.8 Location – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-location.html" title="Understanding success criterion 2.4.8: Location">Understanding success criterion 2.4.8</a>
- Graphic designers and ergonomics experts
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the CSS style applied to the element uses the content property, continue; otherwise, the test is not applicable.
- If this CSS property generates content that is not information bearing, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F3">F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F87">F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If a block's associated CSS styles are deactivated, without loss of comprehension and with not disturbance to the logical relations of surrounding blocks, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G59">G59: Placing the interactive elements in an order that follows sequences and relationships within the content</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F1">F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS</a>
- 1.3.2 Meaningful Sequence – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-sequence.html" title="Understanding success criterion 1.3.2: Meaningful Sequence">Understanding success criterion 1.3.2</a>
- 2.4.3 Focus Order – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-order.html" title="Understanding success criterion 2.4.3: Focus Order">Understanding success criterion 2.4.3</a>
- Developers and integrators
- background
- background-image
- list
- list-style-image
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the background image of the element conveys information, continue; otherwise, the test is not applicable.
- If the information contained by the image is readable when:
- styles are deactivated
- images are deactivated
- styles and images are deactivated
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F3">F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F24">F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is not used in order to visually separate letters contained in a single word, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C8">C8: Using CSS letter-spacing to control spacing within a word</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F32">F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word</a>
- 1.3.2 Meaningful Sequence – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-sequence.html" title="Understanding success criterion 1.3.2: Meaningful Sequence">Understanding success criterion 1.3.2</a>
- Developers and integrators
- Editors and content providers
- background
- background-color
- font
- color
- list
- list-style-image
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is used to define a text color or a background color (perhaps via a background image), continue; otherwise, the test is not applicable.
- If the html element for which a background color has been specified also has a defined text color (directly or by css inheritance), or vice-versa, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F24">F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa</a>
- 1.4.3 Contrast (Minimum) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-contrast.html" title="Understanding success criterion 1.4.3: Contrast (Minimum)">Understanding success criterion 1.4.3</a>
- 1.4.6 Contrast (Enhanced) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast7.html" title="Understanding success criterion 1.4.6: Contrast (enhanced)">Understanding success criterion 1.4.6</a>
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
- Developers and integrators
- img
- object
- embed
- applet
- inputs of type image
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element contains text, continue; otherwise, the test is not applicable.
- If the element was defined in accordance with a style guide whose publication came after that of the RGAA, continue; otherwise, the test is not applicable.
- If the element is not a logo or purely decorative, continue; otherwise, the test is not applicable.
- If the page contains no mechanism by which non-text elements can be replaced by CSS stylized text, continue; otherwise, the test is not applicable.
- If the element uses a format that would be impossible to reproduce using CSS, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G140">G140: Separating information and structure from presentation to enable different presentations</a>
- 1.4.5 Images of Text – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-text-presentation.html" title="Understanding success criterion 1.4.5: Images of Text">Understanding success criterion 1.4.5</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- img
- object
- embed
- applet
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element contains text, continue; otherwise, the test is not applicable.
- If the element is not a logo or purely decorative, continue; otherwise, the test is not applicable.
- If the element uses a format that would be impossible to reproduce using CSS, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C22">C22: Using CSS to control visual presentation of text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C30">C30: Using CSS to replace text with images of text and providing user interface controls to switch</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G140">G140: Separating information and structure from presentation to enable different presentations</a>
- 1.4.9 Images of Text (No Exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-text-images.html" title="Understanding success criterion 1.4.9: Images of Text (No Exception)">Understanding success criterion 1.4.9</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- basefont
- blink
- center
- font
- marquee
- s
- strike
- tt
- u
- align
- alink
- background
- basefont
- bgcolor
- border
- color
- link
- text
- vlink
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G140">G140: Separating information and structure from presentation to enable different presentations</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 1.4.5 Images of Text – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-text-presentation.html" title="Understanding success criterion 1.4.5: Images of Text">Understanding success criterion 1.4.5</a>
- 1.4.9 Images of Text (No Exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-text-images.html" title="Understanding success criterion 1.4.9: Images of Text (No Exception)">Understanding success criterion 1.4.9</a>
- Developers and integrators
- a
- abbr
- acronym
- address
- area
- bdo
- blockquote
- button
- caption
- cite
- code
- dd
- dfn
- dir
- dl
- dt
- em
- fieldset
- form
- h1 to h6
- input
- ins
- kbd
- label
- legend
- li
- menu
- ol
- pre or after unbroken spaces
- q
- samp
- select
- strong
- sub
- sup
- th
- var
- ul
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is not used for presentation purposes only, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G115">G115: Using semantic elements to mark up structure</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F43">F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- link
- alink
- vlink
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is used to style links, continue; otherwise, the test is not applicable.
- If the element does not allow the user to distinguish links only by color, continue; otherwise, the test is not applicable.
- If the contrast ratio between link-text color and the color of adjacent text is greater than or equal to 3 and provided another distinction other than color is available (bold face, underlining, icon, etc.), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G183">G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F73">F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision</a>
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- outline
- outline-color
- outline-style
- outline-width
- If one of the properties mentioned in the domain of application is used in the page, continue; otherwise, the test is not applicable.
- If this property is not used in order to delete the visual effects of elements under focus, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C15">C15: Using CSS to change the presentation of a user interface component when it receives focus</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G165">G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F78">F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator</a>
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
- 2.4.7 Focus Visible – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-visible.html" title="Understanding success criterion 2.4.7: Focus Visible">Understanding success criterion 2.4.7</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the text of the element is not justified (aligned to the right and left at the same time), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C19">C19: Specifying alignment either to the left OR right in CSS</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G169">G169: Aligning text on only one side</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G172">G172: Providing a mechanism to remove full justification of text</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F88">F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins)</a>
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F69">F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured</a>
- 1.4.4 Resize text – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-scale.html" title="Understanding success criterion 1.4.4: Resize text">Understanding success criterion 1.4.4</a>
- Developers and integrators
- pt (point)
- pc (pica)
- px (pixel)
- cm (centimeter)
- mm (millimeter)
- in (inches)
- If one of the values mentioned in the domain of application is present in the style sheet, continue; otherwise, the test is not applicable.
- If the CSS property using this value is that of font-size or font, continue; otherwise, the test is not applicable.
- If this property is used provide formatting for a form element (input, textarea, select, button), continue; otherwise, the test is not applicable.
- If the CSS property using this value is not engaged for the media types screen, projection, handheld or tv, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F80">F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200%</a>
- 1.4.4 Resize text – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-scale.html" title="Understanding success criterion 1.4.4: Resize text">Understanding success criterion 1.4.4</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If in full screen mode there is a horizontal scroll bar, continue; otherwise, the test is not applicable.
- If a mechanism allowing for layout changes enables the user to display the content without the scroll bar, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C24">C24: Using percentage values in CSS for container sizes</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C26">C26: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text</a>
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element has a width less than or equal to 80 characters (40 glyphs for Chinese, Japanese ou Korean) or if the width can be reduced to 80 characters or less when the user resizes the browser window, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C20">C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H87">H87: Not interfering with the user agent's reflow of text as the viewing window is narrowed</a>
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
- Developers and integrators
- line-height
- padding
- margin
- If one of the elements listed in the domain of application is present in the page (or style sheet), continue the test; otherwise, the test is not applicable.
- If the element is used to define the spacing between lines of text or paragraphs, continue; otherwise, the test is not applicable.
- If the value of the spacing between lines is greater than 1.5 times the font size and if the value of the spacing between the paragraphs is again 1.5 times greater than that between the lines, or if a mechanism allowing for the increase of this spacing is present, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C21">C21: Specifying line spacing in CSS</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G188">G188: Providing a button on the page to increase line spaces and paragraph spaces</a>
- 1.4.8 Visual Presentation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-visual-presentation.html" title="Understanding success criterion 1.4.8: Visual Presentation">Understanding success criterion 1.4.8</a>
- Developers and integrators
- Graphic designers and ergonomics experts
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the CSS style applied to the element employs the display:none or visibility:hidden properties, continue; otherwise, the test is not applicable.
- If the element does not need to be read by screen reading devices, or if it becomes readable via a user interaction on the page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/C7">C7: Using CSS to hide a portion of the link text</a>
- 2.4.4 Link Purpose (In Context) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-refs.html" title="Understanding success criterion 2.4.4: Link Purpose (In Context)">Understanding success criterion 2.4.4</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code updates a non-text element in at least one of the following situations:
- in the page content
- in an iframe
- in a frame
- If after each update, the alternative of the non-text element has likewise been updated, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F20">F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If event manager is not used on an "a", area, button or input type button, submit, reset, file, image, password, radio, checkbox, continue; otherwise, the test is not applicable.
- If the activation of the event manager brings forward some new information, continue; otherwise, the test is not applicable.
- If the HTML element in which the onclick event is used also listens for the onkeypress event, and furnishes the same information as a result of onkeypress, or if another HTML element, usable without these events and providing the same information, is also present in the page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G90">G90: Providing keyboard-triggered event handlers</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR2">SCR2: Using redundant keyboard and mouse event handlers</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR20">SCR20: Using both keyboard and other device-specific functions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR29">SCR29: Adding keyboard-accessible actions to static HTML elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR35">SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons</a>
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
- Developers and integrators
- onmousedown
- onmouseup
- onmouseover
- onmouseout
- onfocus
- onblur
- onkeydown
- onkeyup
- If one of the elements listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the activation of the event manager brings forward some new information, continue; otherwise, the test is not applicable.
- If the HTML element containing the event manager also listens for the following events:
- onmousedown / onkeydown
- onmouseup / onkeyup
- onmouseover / onfocus
- onmouseout / onblur
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G90">G90: Providing keyboard-triggered event handlers</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR2">SCR2: Using redundant keyboard and mouse event handlers</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR20">SCR20: Using both keyboard and other device-specific functions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR29">SCR29: Adding keyboard-accessible actions to static HTML elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR35">SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F54">F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function</a>
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript provokes a non-solicited alert or if it updates the page content without any user action having occurred, continue; otherwise, the test is not applicable.
- If the alert or the update is not due to an event or situation that is sudden or urgent and which requires an immediate action in order to preserve health, security or order, continue; otherwise, the test is not applicable.
- If the user can deactivate or activate at will the alert or update, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G75">G75: Providing a mechanism to postpone any updating of content</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G76">G76: Providing a mechanism to request an update of the content instead of updating automatically</a>
- 2.2.4 Interruptions – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-postponed.html" title="Understanding success criterion 2.2.4: Interruptions">Understanding success criterion 2.2.4</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code brings about a change of context (change of the user-agent, displacement of focus, update or creation of content which is semantically significant for the page, form validation) in the page after a user action, continue; otherwise, the test is not applicable.
- If the user is warned in advance of the type of contextual changes that will follow the action, by at least one of the following means:
- textual notification
- the use of a validation button (input type image, submit, button), explicitly confirming the change of context
- the use of a link, accessible by mouse and keyboard, (and not activated simply by the act of focus on the element), explicitly validating the change of context
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G13">G13: Describing what will happen before a change to a form control that causes a change of context to occur is made</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G80">G80: Providing a submit button to initiate a change of context</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G107">G107: Using "activate" rather than "focus" as a trigger for changes of context</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H32">H32: Providing submit buttons</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H84">H84: Using a button with a select element to perform an action</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR19">SCR19: Using an onchange event on a select element without causing a change of context</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F9">F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F36">F36: Failure of Success Criterion 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F37">F37: Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the status of a radio button, check box or select list is changed</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F76">F76: Failure of Success Criterion 3.2.2 due to providing instruction material about the change of context by change of setting in a user interface element at a location that users may bypass</a>
- 3.2.1: On Focus – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-receive-focus.html" title="Understanding success criterion 3.2.1: On Focus">Understanding success criterion 3.2.1</a>
- 3.2.2 On Input – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-unpredictable-change.html" title="Understanding success criterion 3.2.2: On Input">Understanding success criterion 3.2.2</a>
- 3.2.5 Change on Request – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-no-extreme-changes-context.html" title="Understanding success criterion 3.2.5: Change on Request">Understanding success criterion 3.2.5</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code updates or creates content following a user action, continue; otherwise, the test is not applicable.
- If the updated or generated content contains all the attributes and elements necessary to guarantee its accessibility, continue; otherwise, the test is not applicable.
- If the updated or generated content (or a link pointing to it) is placed just after the element that provoked the change, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR26">SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR27">SCR27: Reordering page sections using the Document Object Model</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR37">SCR37: Creating Custom Dialogs in a Device Independent Way</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F85">F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order</a>
- 2.4.3 Focus Order – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-order.html" title="Understanding success criterion 2.4.3: Focus Order">Understanding success criterion 2.4.3</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If an interaction with the element (mouseclick, arrival or departure of the focus on the element) provokes an action (form validation, page access, new browser window, generation of content, etc.), continue; otherwise, the test is not applicable.
- If this element is an 'a' tag, area, button, or input of type button, submit, reset, file, image, password, radio, checkbox, select, or if an element of this type is present in the page source for the purposes of effecting an identical action, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F42">F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F59">F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code makes use of an event manager with no universal equivalent or that relies on a device specific property, continue; otherwise, the test is not applicable.
- If the javascript code is necessary in order to access information, continue; otherwise, the test is not applicable.
- If the information made available by the javascript is also available by means of an accessible alternative, either in the same page or from the page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F54">F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function</a>
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.1.3 Keyboard (no exception) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-all-funcs.html" title="Understanding success criterion 2.1.3: Keyboard (no exception)">Understanding success criterion 2.1.3</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code is not employed to take the focus away from an element the moment focus is given to that element, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F55">F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received</a>
- 2.1.1 Keyboard – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/keyboard-operation-keyboard-operable.html" title="Understanding success criterion 2.1.1: Keyboard">Understanding success criterion 2.1.1</a>
- 2.4.7 Focus Visible – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-visible.html" title="Understanding success criterion 2.4.7: Focus Visible">Understanding success criterion 2.4.7</a>
- 3.2.1: On Focus – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/consistent-behavior-receive-focus.html" title="Understanding success criterion 3.2.1: On Focus">Understanding success criterion 3.2.1</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If this task needs to be accomplished with in a limited time, continue; otherwise, the test is not applicable.
- If the task really needs to be completed in real-time, or if the time limit cannot be removed without fundamentally changing the information or functionalities involved, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G5">G5: Allowing users to complete an activity without any time limit</a>
- 2.2.3 No Timing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-no-exceptions.html" title="Understanding success criterion 2.2.3: No Timing">Understanding success criterion 2.2.3</a>
- Developers and integrators
- If one of the elements mentioned in the domain of application is used in the site, continue; otherwise, the test is not applicable.
- If there is a mechanism by which the session might expire or close without this being solicited by the user, continue; otherwise, the test is not applicable.
- If the data already entered by the user before the expiration or closure of the session is conserved and available to the user upon reconnection,, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G105">G105: Saving data so that it can be used after a user re-authenticates</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G181">G181: Encoding user data as hidden or encrypted data in a re-authorization page</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F12">F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism for saving user's input and re-establishing that information upon re-authentication</a>
- 2.2.5 Re-authenticating – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/time-limits-server-timeout.html" title="Understanding success criterion 2.2.5: Re-authenticating">Understanding success criterion 2.2.5</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code is necessary for transmission of the page's information, continue; otherwise, the test is not applicable.
- If the content available via the javascript does not allow for an access at the same informational level as a piece of textual content of the page, continue; otherwise, the test is not applicable.
- If the content is not aimed uniquely at a computing environment where the activation of javascript is obligatory, continue; otherwise, the test is not applicable.
- If an alternative to the javascript code is present by means in at least one of the following ways:
- in a noscript tag
- by use of non-obtrusive javascript code giving access to the alternative via an 'a' element, an area or directly in the page content when javascript is deactivated,
- through the use of a server side scripting language
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F19">F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- If javascript is used in the page, continue; otherwise, the test is not applicable.
- If the javascript code generates or updates content in the page, without or without user interaction, continue; otherwise, the test is not applicable.
- If the updated or generated content contains all the attributes and elements necessary to guarantee its accessibility and notably the use of DOM functions whenever possible, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/SCR21">SCR21: Using functions of the Document Object Model (DOM) to add content to a page</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G134">G134: Validating Web pages</a>
- 4.1.1 Parsing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-parses.html" title="Understanding success criterion 4.1.1: Parsing">Understanding success criterion 4.1.1</a>
- Developers and integrators
- If declaration is present in the page, continue; otherwise, the test is not applicable.
- If declaration is situated before the html tag, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G192">G192: Fully conforming to specifications</a>
- 4.1.1 Parsing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-parses.html" title="Understanding success criterion 4.1.1: Parsing">Understanding success criterion 4.1.1</a>
- Developers and integrators
- If the declaration is present in the page, continue; otherwise, the test is not applicable.
- If the declaration is well-formed syntactically, in accord with the W3C's recommended list of DTDs, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H74">H74: Ensuring that opening and closing tags are used according to specification</a>
- 4.1.1 Parsing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-parses.html" title="Understanding success criterion 4.1.1: Parsing">Understanding success criterion 4.1.1</a>
- Developers and integrators
- If a DTD is declared in the page, continue; otherwise, the test is not applicable.
- If the page is served formally as being text/html and is not valid according to the declared DTD, continue; otherwise, the test is not applicable.
- If the validation errors do not concern the nesting of the tags in the document's structure, and if they do not concern the document's tags and attributes themselves, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G134">G134: Validating Web pages</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G192">G192: Fully conforming to specifications</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H74">H74: Ensuring that opening and closing tags are used according to specification</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H88">F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F62">F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F70">F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F77">F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID</a>
- 4.1.1 Parsing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-parses.html" title="Understanding success criterion 4.1.1: Parsing">Understanding success criterion 4.1.1</a>
- Developers and integrators
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H88">F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID</a>
- 4.1.1 Parsing – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-parses.html" title="Understanding success criterion 4.1.1: Parsing">Understanding success criterion 4.1.1</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G88">G88: Providing descriptive titles for Web pages</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H25">H25: Providing a title using the title element</a>
- 2.4.2 Page Titled – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-title.html" title="Understanding success criterion 2.4.2: Page Titled">Understanding success criterion 2.4.2</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If element's content allows for the easy identification of the pages function, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G88">G88: Providing descriptive titles for Web pages</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H25">H25: Providing a title using the title element</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F25">F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents</a>
- 2.4.2 Page Titled – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-title.html" title="Understanding success criterion 2.4.2: Page Titled">Understanding success criterion 2.4.2</a>
- Developers and integrators
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the HTML element that contains the text segment, or one another tag that is higher up in the page hierarchy, has a non-empty lang attribute (or an xml:lang for XML or XHTML 1.1), containing the correct language code for the page, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H57">H57: Using language attributes on the html element</a>
- 3.1.1 Language of Page – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-doc-lang-id.html" title="Understanding success criterion 3.1.1: Language of Page">Understanding success criterion 3.1.1</a>
- Developers and integrators
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H69">H69: Providing heading elements at the beginning of each section of content</a>
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- Developers and integrators
- h1
- h2
- h3
- h4
- h5
- h6
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the content of the element clearly identifies the information that follows, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G130">G130: Providing descriptive headings</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H42">H42: Using h1-h6 to identify headings</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 2.4.6 Headings and Labels – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-descriptive.html" title="Understanding success criterion 2.4.6: Headings and Labels">Understanding success criterion 2.4.6</a>
- Developers and integrators
- Editors and content providers
- h2
- h3
- h4
- h5
- h6
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- We consider the element H with level 'n' and write Hn. If, in the order of the page's source code, the closest antecedent header of this element is at level 'n', 'n-1' or 'n+x' (where x greater than or equal to 4), the test is successful; otherwise, it fails. QED
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H42">H42: Using h1-h6 to identify headings</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the content described in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the content could benefit from a hierarchical structure beyond the H1 level, continue; otherwise, the test is not applicable.
- If the content is structured via the correct use of page headers (h1 to h6), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G141">G141: Organizing a page using headings</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H69">H69: Providing heading elements at the beginning of each section of content</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F2">F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 2.4.10 Section Headings – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-headings.html" title="Understanding success criterion 2.4.1:0 Section Headings">Understanding success criterion 2.4.10 </a>
- Developers and integrators
- Editors and content providers
- If two text segments (be they different or identical) are present in the page, continue; otherwise, the test is not applicable.
- If the text segments are visually arranged using list like markings (-, >, #, *, image or background image representing a list marker, etc.), continue; otherwise, the test is not applicable.
- If the text segments are regrouped under a list structure (the ul element) with the li element being used for each text segment, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H48">H48: Using ol, ul and dl for lists or groups of links</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F2">F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If two text segments (be they different or identical) are present in the page, continue; otherwise, the test is not applicable.
- If the text segments require an ordered presentation continue; otherwise, the test is not applicable.
- If the text segments are regrouped under an ordered list structure (the ol element) with the li element being used for each text segment, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H48">H48: Using ol, ul and dl for lists or groups of links</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F2">F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If each dd element is preceded by a dt element, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H40">H40: Using definition lists</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the text segment is a citation, continue; otherwise, the test is not applicable.
- If the text segment is tagged using the q element for a short quote or the blockquote element for a citation in paragraph form, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H49">H49: Using semantic markup to mark emphasized or special text</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F2">F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If a text segment listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If at least on the first occurrence (with respect to the order of the page source code) of a text segment constituting an abbreviated term the user does not have access to the expanded version of the abbreviation by one of the following mechanisms :
- the expanded version of the abbreviation is given in an adjacent text segment
- the text segment serves also as a link to the expanded version of the abbreviation
- the text segment is a link the title attribute of which contains the expanded version of the abbreviation
- a glossary providing the definition of the abbreviation is available on the site
- If at least the first occurrence of the text segment in question is contained by an abbr element which itself has a non-empty title attribute, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G55">G55: Linking to definitions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G70">G70: Providing a function to search an online dictionary</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G97">G97: Providing the first use of an abbreviation immediately before or after the expanded form</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H28">H28: Providing definitions for abbreviations by using the abbr and acronym elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H60">H60: Using the link element to link to a glossary</a>
- 3.1.4 Abbreviations – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-located.html" title="Understanding success criterion 3.1.4: Abbreviations">Understanding success criterion 3.1.4</a>
- Developers and integrators
- Editors and content providers
- If a text segment listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If at least on the first occurrence (with respect to the order of the page source code) of a text segment constituting an abbreviated term the user does not have access to the expanded version of the acronym by one of the following mechanisms :
- the expanded version of the acronym is given in an adjacent text segment
- the text segment serves also as a link to the expanded version of the acronym
- the text segment is a link the title attribute of which contains the expanded version of the acronym
- a glossary providing the definition of the acronym is available on the site
- If at least the first occurrence of the text segment in question is contained by an acronym element which itself has a non-empty title attribute, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G55">G55: Linking to definitions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G70">G70: Providing a function to search an online dictionary</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G97">G97: Providing the first use of an abbreviation immediately before or after the expanded form</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H28">H28: Providing definitions for abbreviations by using the abbr and acronym elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H60">H60: Using the link element to link to a glossary</a>
- 3.1.4 Abbreviations – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-located.html" title="Understanding success criterion 3.1.4: Abbreviations">Understanding success criterion 3.1.4</a>
- Developers and integrators
- Editors and content providers
- If the element listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the title attribute's content provides the expanded version of the abbreviation, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G55">G55: Linking to definitions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G70">G70: Providing a function to search an online dictionary</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G97">G97: Providing the first use of an abbreviation immediately before or after the expanded form</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H28">H28: Providing definitions for abbreviations by using the abbr and acronym elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H60">H60: Using the link element to link to a glossary</a>
- 3.1.4 Abbreviations – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-located.html" title="Understanding success criterion 3.1.4: Abbreviations">Understanding success criterion 3.1.4</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the title attribute's content provides the expanded version of the acronym, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G55">G55: Linking to definitions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G70">G70: Providing a function to search an online dictionary</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G97">G97: Providing the first use of an abbreviation immediately before or after the expanded form</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H28">H28: Providing definitions for abbreviations by using the abbr and acronym elements</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H60">H60: Using the link element to link to a glossary</a>
- 3.1.4 Abbreviations – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-located.html" title="Understanding success criterion 3.1.4: Abbreviations">Understanding success criterion 3.1.4</a>
- Developers and integrators
- Editors and content providers
- a
- area
- object
- embed
- applet
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the work document indicated by the element is available in an accessible version by at least one of the following solutions:
- a natively accessible version (especially concerning the alternatives to images, hierarchical titles, lists, forms, data tables, language and reading order)
- an alternative version in html format, and accessible
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G10">G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G135">G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F15">F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 1.3.2 Meaningful Sequence – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-sequence.html" title="Understanding success criterion 1.3.2: Meaningful Sequence">Understanding success criterion 1.3.2</a>
- 2.4.1 Bypass Blocks – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-skip.html" title="Understanding success criterion 2.4.1: Bypass Blocks">Understanding success criterion 2.4.1</a>
- 2.4.3 Focus Order – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/navigation-mechanisms-focus-order.html" title="Understanding success criterion 2.4.3: Focus Order">Understanding success criterion 2.4.3</a>
- 3.1.1 Language of Page – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-doc-lang-id.html" title="Understanding success criterion 3.1.1: Language of Page">Understanding success criterion 3.1.1</a>
- 4.1.2 Name, role and value – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/ensure-compat-rsv.html" title="Understanding success criterion 4.1.2: Name, role and value ">Understanding success criterion 4.1.2</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element contains one or more text segments which can be readily identified as being headers for columns or lines in the table, continue; otherwise, the test is not applicable.
- If each of these text segments is contained within a th element, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H51">H51: Using table markup to present tabular information</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the header cells (th) for the rows have a scope attribute with value 'row' or if the header cells (th) for the columns have a scope attribute with value 'col' or if the header cells (th) have a non-empty id attribute and the data-cells (td) that correspond to a given header cell contain a header attribute whose value corresponds to the id attributes of the associated header cells (th), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H63">H63: Using the scope attribute to associate header cells and data cells in data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the header cells (th) have a non-empty id attribute and the data-cells (td) that correspond to a given header cell contain a header attribute whose value corresponds to the id attributes of the associated header cells (th), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H43">H43: Using id and headers attributes to associate data cells with header cells in data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the has no summary attribute or if the summary attribute is empty, (summary=""), and if the element contains none of the following:
- th
- caption
- thead
- tfoot
- colgroup
- scope
- headers
- axis
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F46">F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element is not used in order to format visually columns or a data table, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F33">F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F34">F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F48">F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- 1.3.2 Meaningful Sequence – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-sequence.html" title="Understanding success criterion 1.3.2: Meaningful Sequence">Understanding success criterion 1.3.2</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the sequential reading of the table content (cell by cell, in the order given in the page source) maintains the same logical associations that appear on the screen, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F49">F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized </a>
- 1.3.2 Meaningful Sequence – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-sequence.html" title="Understanding success criterion 1.3.2: Meaningful Sequence">Understanding success criterion 1.3.2</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a caption element is present, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H39">H39: Using caption elements to associate data table captions with data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element has a summary attribute, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H73">H73: Using the summary attribute of the table element to give an overview of data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If a non-empty caption element is present, or if there is content placed immediately the table in the page source and this functions as a title, continue; otherwise, the test is not applicable.
- If the content of the caption element, or the content of the element serving as a title for the table enable the user to deduce the function or the content of the table, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H39">H39: Using caption elements to associate data table captions with data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If the element mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the element has a non-empty summary attribute, continue; otherwise, the test is not applicable.
- If the summary attribute's content explains the organization of the table data, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H73">H73: Using the summary attribute of the table element to give an overview of data tables</a>
- 1.3.1 Info and Relationships – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html" title="Understanding success criterion 1.3.1: Info and Relationships">Understanding success criterion 1.3.1</a>
- Developers and integrators
- Editors and content providers
- If a text segment listed in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the text segment constitutes a language change, with respect to the main language of the page, or to that of the content of its parent element, continue; otherwise, the test is not applicable.
- If the text segment is not a proper noun, a word/group of words from an indeterminate language, a word/group of words that could be identified when pronounced aloud in the language of the immediate context, or a past word/group of words from the language of the immediate context, continue; otherwise, the test is not applicable.
- If the text segment the only content of a preceding and containing HTML element that has a correctly filled in lang attribute (or xml:lang for XML or XHTML 1.1), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H58">H58: Using language attributes to identify changes in the human language </a>
- 3.1.2 Language of Parts – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-other-lang-id.html" title="Understanding success criterion 3.1.2: Language of Parts">Understanding success criterion 3.1.2</a>
- Developers and integrators
- Editors and content providers
- alt
- summary
- content for meta elements
- label for option elements
- value
- name for frame and iframe elements
- title
- standby for object elements
- If one of the attributes mentioned in the domain of application is present in the page, continue; otherwise, the test is not applicable.
- If the content of this attribute implies a change of language with respect to the main language of the page, or to that of the parent element of the element containing the attribute in question, continue; otherwise, the test is not applicable.
- If this attributes content is not a proper noun, a word/group of words from an indeterminate language, a word/group of words that could be identified when pronounced aloud in the language of the immediate context, or a past word/group of words from the language of the immediate context, continue; otherwise, the test is not applicable.
- If the HTML element containing the attribute or the immediately preceding element contains a correctly filled in lang attribute (or xml:lang for XML or XHTML 1.1), the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H58">H58: Using language attributes to identify changes in the human language </a>
- 3.1.2 Language of Parts – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-other-lang-id.html" title="Understanding success criterion 3.1.2: Language of Parts">Understanding success criterion 3.1.2</a>
- Developers and integrators
- Editors and content providers
- applet
- embed
- object
- all javascript code used in a page or generating one of the preceding elements
- If one of the elements listed in the domain of application is present in the page, continue the test; otherwise, the test is not applicable.
- If the element has an alternative version, continue; otherwise, the test is not applicable.
- If the information put at the user's disposition in the alternative version is equivalent to that in the main version (both visual information -- text on the screen, visual actions, attitudes, visibly obvious emotions, gestures, scene changes-- as well as sound information--pronounced speech, noises, musical elements, intonations speaker changes, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G69">G69: Providing an alternative for time based media</a>
- 1.2.1 Audio-only and Video-only (Prerecorded)– <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-av-only-alt.html" title="Understanding success criterion 1.2.1: Audio-only and Video-only (Prerecorded)">Understanding success criterion 1.2.1</a>
- 1.2.3 Audio Description or Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-audio-desc.html" title="Understanding success criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)">Understanding success criterion 1.2.3</a>
- 1.2.8 Media Alternative (Prerecorded) – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/media-equiv-text-doc.html" title="Understanding success criterion 1.2.8: Media Alternative (Prerecorded) ">Understanding success criterion 1.2.8</a>
- Developers and integrators
- Editors and content providers
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the text segment is in habitual, or very context specific, including, for example, the use of jargon, continue the test; otherwise, the test is not applicable.
- If the text segment is not made explicit in the page by at least one of the following solutions:
- a dfn element
- a definition list
- the clarification of the text segment elsewhere in the page content
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G55">G55: Linking to definitions</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G112">G112: Using inline definitions</a>
- 3.1.3 Unusual Words – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-idioms.html" title="Understanding success criterion 3.1.3: Unusual Words">Understanding success criterion 3.1.3</a>
- Developers and integrators
- Editors and content providers
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the text segment employs a syntax which does not permit easy comprehension (i.e. is cryptic), continue; otherwise, the test is not applicable.
- If the cryptic text segment has an alternate text, by way of a title attribute, or via a neighboring text segment which itself is clear and not of a cryptic nature, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/H86">H86: Providing text alternatives for ASCII art, emoticons, and leetspeak</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F71">F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F72">F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative</a>
- 1.1.1 Non-text content – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/text-equiv-all.html" title="Understanding success criterion 1.1.1: Non-text content">Understanding success criterion 1.1.1</a>
- Developers and integrators
- Editors and content providers
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the comprehension of certain words comprising the text segment could pose a problem during reading, continue; otherwise, the test is not applicable.
- If the phonetic transcription of these difficult words is present, adjacent to them, or if a link points towards such transcriptions, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G62">G62: Providing a glossary</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G120">G120: Providing the pronunciation immediately following the word</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G121">G121: Linking to pronunciations</a>
- 3.1.6 Pronunciation – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-pronunciation.html" title="Understanding success criterion 3.1.6: Pronunciation">Understanding success criterion 3.1.6</a>
- Editors and content providers
- img
- inputs of type image
- applet
- object
- embed
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays zones whose shape or position conveys information, continue; otherwise, the test is not applicable.
- If the information conveyed by their form or position is accessible by other means, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G96">G96: Providing textual identification of items that otherwise rely only on sensory information to be understood</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G111">G111: Using color and pattern</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F14">F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F26">F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information</a>
- 1.3.3 Sensory Characteristics – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-understanding.html" title="Understanding success criterion 1.3.3: Sensory Characteristics">Understanding success criterion 1.3.3</a>
- 1.4.1 Color use – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/visual-audio-contrast-without-color.html" title="Understanding success criterion 1.4.1: Color use">Understanding success criterion 1.4.1</a>
- Developers and integrators
- Editors and content providers
- img
- inputs of type image
- applet
- object
- embed
- If one of the elements listed in the domain of application is present or used in the page, continue; otherwise, the test is not applicable.
- If the element displays text graphically or has a non-empty alt attribute, continue; otherwise, the test is not applicable.
- If the graphic text, or its alternative, mentions a shape or position and also makes reference to page or site content, continue; otherwise, the test is not applicable.
- If the graphic text, or its alternative, allow the identification of the aforementioned page or site content by another means than shape or position, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G96">G96: Providing textual identification of items that otherwise rely only on sensory information to be understood</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F14">F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location</a>
- 1.3.3 Sensory Characteristics – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-understanding.html" title="Understanding success criterion 1.3.3: Sensory Characteristics">Understanding success criterion 1.3.3</a>
- Developers and integrators
- Editors and content providers
- If a text segment matching the description is present in the page, continue; otherwise, the test is not applicable.
- If the text segment mentions a shape or a position and makes reference to page or site content, continue; otherwise, the test is not applicable.
- If the text segment allows identification of this content by other means than shape or position, the test is successful; otherwise, it fails.
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G96">G96: Providing textual identification of items that otherwise rely only on sensory information to be understood</a>
- <a href="http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/F14">F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location</a>
- 1.3.3 Sensory Characteristics – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-understanding.html" title="Understanding success criterion 1.3.3: Sensory Characteristics">Understanding success criterion 1.3.3</a>
- Developers and integrators
- Editors and content providers
- If a text segment is present in the page, continue; otherwise, the test is not applicable.
- If the comprehension of the text segment requires a level of education exceeding that of someone who has passed 9 years in education (beginning from the first year of schooling), after the deletion of proper nouns and titles, continue; otherwise, the test is not applicable.
- If at least one of the following content types or an additional version that does not require a reading level beyond that obtained after 9 years of schooling, is available:
- visual illustrations, symbols or images facilitating the comprehension of content
- a version in French sign language
- an audio version of the text segment
- a summary, written in such a way so as not to require a reading level beyond that obtained at the beginning of secondary school
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G79">G79: Providing a spoken version of the text</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G86">G86: Providing a text summary that requires reading ability less advanced than the upper secondary education level</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G103">G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G153">G153: Making the text easier to read</a>
- <a href="http://www.w3.org/TR/WCAG20-TECHS/G160">G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content</a>
- 3.1.5 Reading Level – <a href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/meaning-supplements.html" title="Understanding success criterion 3.1.5: Reading Level">Understanding success criterion 3.1.5</a>
- Editors and content providers
</ol></div>
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
</div>
Applies to:
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
Applies to:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
The 'a" element
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
Any page summarizing the general architecture of the site via hypertext links.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Any page summarizing the general architecture of the site via hypertext links.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Any page summarizing the general architecture of the site via hypertext links.
Test procedure
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Any list of 'a' tags showing the path from the home page of the site to the current page.
Test procedure
If this list of links is present in the page, the test is successful; otherwise, it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
Applies to:
Any group of elements used for navigation in the site or in the page.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Any group of elements used for navigation in the site or in the page.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Any group of elements used for navigation in the site or in the page.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
Test procedure
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
Applies to:
or any javascript code used in the page.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
Test procedure
<Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
or any javascript code used in the page.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
The 'a' element.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
Any HTML element containing an important grouping (navigation, repeated content, tool zone, etc.) and identified by an anchor.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
Any HTML element containing an important grouping (navigation, repeated content, tool zone, etc.) and identified by an anchor.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
The 'a' element.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
Applies to:
The 'a' element.
Test procedure
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
</div>
Applies to:
Site search engine.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
Groups of pages.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
Applies to:
All navigation menus.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
7.1 [Visual Presentation]1: No information bearing content is generated via the CSS
Applies to:
Any element to which style (CSS) attributes are applied, by whatever means (inline, stylesheet, etc.) including via javascript.
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.2 [Visual Presentation]2: No change to the possible interpretation of a block of information in the event that the CSS is deactivated
Applies to:
Any block of information (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.3 [Visual Presentation]3: Readability of information displayed as page background via the CSS is retained when the styles are deactivated
Applies to:
Any element having an associated background image declared via CSS using one of the following properties:
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.4 [Visual Presentation]4: No spaces are used for separating the letters in a word
Applies to:
Any typographical space or empty element used to simulate a space.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.5 [Visual Presentation]5: No text color is specified without a background color also being specified and vice-versa
Applies to:
The following CSS properties:
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
7.6 [Visual Presentation]6: Possibility of replacing non text elements with equivalent text elements stylized accordingly by the CSS
Applies to:
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
7.7 [Visual Presentation]7: Possibility of replacing non text elements with equivalent text elements stylized accordingly by the CSS (without exceptions)
Applies to:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
7.8 [Visual Presentation]8: The page is free of HTML page-layout tags or attributes
Applies to:
or attributes:
Test procedure
If none of the aforementioned elements or attributes are present in the page, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.9 [Visual Presentation]9: The page is free of any HTML elements used solely for page layout purposes
Applies to:
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.10 [Visual Presentation]10: Links are visually distinct from surrounding text
Applies to:
Any CSS selector targeting the 'a' element and any of following attributes:
used on the body element.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.11 [Visual Presentation]11: Focus effects on links have not been removed
Applies to:
The following CSS properties:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
7.12 [Visual Presentation]12: The page is free of text justification
Applies to:
Any element visually constituting a text block.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
7.13 [Visual Presentation]13: Document legibility is not adversely affected by increased text character size
Applies to:
The whole document.
Test procedure
If, when a user has not modified the default font size of the browser, the document remains readable with no information loss, even with the text size magnified to 200%, the test is successful, if not it fails.
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
7.14 [Visual Presentation]14: The page is free of styles using absolute unit values or pixels for character sizes in form elements
Applies to:
Any CSS property containing a non-zero value expressed in:
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
7.15 [Visual Presentation]15: The page is free of horizontal scroll bars, even on full screen displays
Applies to:
Any element visually constituting a text block.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
7.16 [Visual Presentation]16: Width of text blocks
Applies to:
Any element visually constituting a text block.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
7.17 [Visual Presentation]17: Interline and inter-paragraph spacing
Applies to:
The following CSS properties:
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
Applies to:
Any element to which is applied styles, whether they come via a style attribute, an inline style declaration, an external style sheet or javascript code.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.1 [Scripts]1: Updating of elements that are alternatives to non-text elements
Applies to:
All javascript code in the page.
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.2 [Scripts]2: Non-dependence on the onclick event manager
Applies to:
Any HTML element that can receive focus and that has employs the onclick event or a javascript equivalent.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.3 [Scripts]3: No specific device dependence for event managers
Applies to:
Any HTML element having at least one of the following event attributes:
or a javascript equivalent.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.4 [Scripts]4: Possibility of turning off unsolicited alerts and automatic updates in a page
Applies to:
All javascript code in the page.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
8.5 [Scripts]5: The page is free of changes in context based on user input but without explicit validation or warning
Applies to:
All javascript code in the page.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.6 [Scripts]6: Tabulation order of dynamically updated content in javascript
Applies to:
All javascript code in the page.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.7 [Scripts]7: Correct use of the role of an element
Applies to:
Any HTML element.
Test procedure
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.8 [Scripts]8: Provision of an alternative to javascript code when that code is device-dependent or contains non-universal event managers
Applies to:
All javascript code in the page.
Test procedure
Test level
Difficult
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.9 [Scripts]9: The page is free of any javascript whose effect would be to inhibit keyboard focus on an element
Applies to:
All javascript code in the page.
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.10 [Scripts]10: Absence of time limits for completing tasks
Applies to:
All tasks requiring user interaction (reading, interface manipulation, navigation, data entry, etc.).
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
8.11 [Scripts]11: No information loss upon the expiration of an authenticated session
Applies to:
All authenticated server side sessions.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
8.12 [Scripts]12: Provision of an alternative to javascript
Applies to:
All javascript code in the page.
Test procedure
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
8.13 [Scripts] Accessibility of dynamic javascript content
Applies to:
All javascript code in the page.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.1 [Standards]1: Provision of a declared DTD
Applies to:
The !DOCTYPE declaration
Test procedure
If the declaration is present in the page, the test is successful; if not, it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.2 [Standards]2: Correct placement of the declared DTD
Applies to:
The !DOCTYPE declaration.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.3 [Standards]3: Correct syntax of the declared DTD
Applies to:
The !DOCTYPE declaration.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.4 [Standards]4: HTML / XHTML validity with respect to the declared DTD
Applies to:
All HTML or XHTML pages
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.5 [Standards]5: The page is free of obsolete components with respect to the W3C specifications used
Applies to:
All W3C specified components.
Test procedure
As long as none of the components in question is obsolete with respect to the W3C specifications used, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.6 [Standards]6: Provision of a page title
Applies to:
The title element.
Test procedure
If the title tag is present in the page, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.7 [Standards]7: Relevance of the page title
Applies to:
The :: element title.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
9.8 [Standards]8: Explicit mention of the page's language
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.1 [Structure]1: Provision of at least one top level header (H1)
Applies to:
The h1 element.
Test procedure
If the element mentioned in the domain of application is present in the page, the test is successful, if not it fails.
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.2 [Structure]2: Relevance of page header content
Applies to:
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.3 [Structure]3: Continuity of the hierarchy of page headers
Applies to:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.4 [Structure]4: Provision of a complete hierarchy of page headers
Applies to:
All information bearing content in the page.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.5 [Structure]5: The page is free of fake (simulated) lists
Applies to:
Any text segment.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.6 [Structure]6: Systematic use of true ordered list structures for enumerated lists
Applies to:
Any text segment.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.7 [Structure]7: Correct tagging for definition lists
Applies to:
The dl element .
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.8 [Structure]8: Correct tagging of quotations
Applies to:
Any text segment.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
10.9 [Structure]9: Correct tagging of abbreviations present in the page
Applies to:
Any text segment constituting an abbreviation (a truncated word, or a sequence of words, reduced by elimination of certain words, or a series of words reduced by taking the initial letter of each), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
10.10 [Structure]10: Correct tagging of acronyms present in the page
Applies to:
Any text segment constituting un acronym (truncation of a series of words whereby the first letter of each contributes one letter to a string which itself can be pronounced as a word), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
10.11 [Structure]11: Relevance of an abbreviation's declared meaning
Applies to:
Any abbr element having a non-empty title attribute
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
10.12 [Structure]12: Relevance of an acronym's declared meaning
Any abbr
Test procedure
Applies to:
Any acronym element having a non-empty title attribute.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
10.13 [Structure] Accessibility of documents that are offered for download
Applies to:
or javascript code pointing to a work document.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.1 [Tables]11: Provision of th tags to indicate header lines and columns in data-tables
Applies to:
Any table element identified as a data-table.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.2 [Tables]2: Relation between the headers (th) and the data-cells (td) associated with them in a data-table through use of the id and headers or scope attributes
Applies to:
Any table element identified as a data-table and having one header row or header column (th) or a header row and a header column.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.3 [Tables]3: Relation between the headers (th) and the data-cells (td) associated with them in a complex data-table through use of the id and headers attributes
Applies to:
Any table element identified as a data-table, having at least two header columns (th) or two header rows (th) separated by rows or columns of content.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.4 [Tables]4: Tables used for layout purposes do not contain elements particular to data-tables
Applies to:
Any table element identified as a layout table.
Test procedure
Test level
Easy
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.5 [Tables]5: Text characters are not used in the formatting of data-tables or column layouts
Applies to:
Any unbroken sequence of characters or any sequence of typographic spaces in a pre element.
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.6 [Tables]6: Correct linearization of layout tables
Applies to:
Any table element identified as a layout table.
Test procedure
Test level
Medium
WCAG techniques
No WCAG technique is associated with this test.
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.7 [Tables]7: Provision of a title for each data-table
Applies to:
Any table element identified as a data-table.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.8 [Tables]8: Provision of a summary for each data-table
Applies to:
Any table element identified as a data-table.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.9 [Tables]9: Relevance of the table's title to its content
Applies to:
Any table element identified as a data-table.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
11.10 [Tables]10: Relevance of the table's summary to its content
Applies to:
Any table element identified as a data-table.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.1 [Texts]1: Language changes in the text are indicated
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript or style sheets.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.2 [Texts]2: Indications of language changes are provided as attributes in HTLM elements
Applies to:
All values of the attributes:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AA
This checkpoint concerns:
12.3 [Texts]3: Synchronization and equivalence of information made available in an alternative version
Applies to:
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.4 [Texts] Availability of necessary complementary information via links or definitions
Applies to:
Any text segment.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
12.5 [Texts]5: Absence of cryptic syntax to make references to the site's own content
Applies to:
Any text segment.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.6 [Texts]6: Availability, where necessary, of phonetic transcriptions for words
Applies to:
Any text segment.
Test procedure
Test level
Difficult
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA
This checkpoint concerns:
12.7 [Texts]7: Provision of a means of information transmission other than shape or position in non-text elements
Applies to:
or javascript code generating any of these elements.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.8 [Texts]8: Provision of an alternate means of identifying content which is referred to in a non-text element with regard to the content's shape or position
Applies to:
or javascript code generating any of these elements.
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.9 [Texts]9: Provision of an alternate means for identifying content which is referred to textually with respect to its shape or position
Applies to:
Any text segment (word, group of words, sentence, text block), whether contained within an HTML element or not, or generated by javascript or style sheets, and mentioning a shape or a position .
Test procedure
Test level
Medium
WCAG techniques
WCAG SC Failure
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level A
This checkpoint concerns:
12.10 [Texts]10: Use of clear and simple concise writing style, universally comprehensible
Applies to:
Any text segment.
Test procedure
Test level
Easy
WCAG techniques
WCAG SC Failure
No WCAG check-point corresponds to this test.
WCAG success criteria
Links in this section point to the document Understanding WCAG 2.0.
Corresponding WCAG level
Level AAA