WCAG 2.0 (Level AAA)

Abbreviation WCAG2-AAA
Long Name Web Content Accessibility Guidelines (WCAG), Version 2.0, Level AAA
Published Date 2006-06-19
URL http://www.w3.org/TR/WCAG20/#aaa
Status Enabled
Open To Public Yes


Checks


1.1 Text Alternatives: Provide text alternatives for all non-text content


Success Criteria 1.1.1 Non-text Content (A)


Element Error Type Description Check ID
applet Potential <code>applet</code> contains a text equivalent in the <code>alt</code> attribute of the <code>applet</code>. 23
applet Potential <code>applet</code> contains a text equivalent in the body of the <code>applet</code>. 25
area Known All <code>area</code> elements have an <code>alt</code> attribute. 64
area Potential Alt text for all <code>area</code> elements identifies the link destination. 65
embed Known All <code>embed</code> elements have an associated <code>noembed</code> element that contains a text equivalent to the <code>embed</code> element. 163
img Known All <code>img</code> elements have an <code>alt</code> attribute. 1
img Likely Alt text is not the same as the filename unless author has confirmed it is correct. 2
img Likely Image Alt text is short. 3
img Likely Alt text for all <code>img</code> elements is not placeholder text unless author has confirmed it is correct. 6
img Known Alt text for all <code>img</code> elements used as source anchors is not empty when there is no other text in the anchor. 7
img Potential A long description is used for each <code>img</code> element that does not have Alt text conveying the same information as the image. 8
img Potential Alt text for all <code>img</code> elements is the empty string ("") if the image is decorative. 16
img Potential Alt text for all <code>img</code> elements that are not used as source anchors conveys the same information as the image. 178
img Potential <code>title</code> attribute for all <code>img</code> elements is absent or the empty string ("") if the image is decorative. 239
input Known All <code>input</code> elements with a <code>type</code> attribute value of "image" have an <code>alt</code> attribute. 58
input Potential Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" identifies the purpose or function of the image. 59
input Likely Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" is less than 100 characters (English) or the user has confirmed that the Alt text is as short as possible. 60
input Likely Image used in <code>input</code> element - Alt text should not be placeholder text. 62
input Potential Alt text for all <code>input</code> elements with a <code>type</code> attribute value of "image" contains all non decorative text in the image. 193
input Known All <code>input</code> elements, except those with with a <code>type</code> attribute value of "image", do not have an <code>alt</code> attribute. 238
object Potential All <code>objects</code> contain a text equivalent of the <code>object</code>. 80

1.2 Time-based Media: Provide alternatives for time-based media


Success Criteria 1.2.1 Audio-only and Video-only (Prerecorded) (A)


Element Error Type Description Check ID
a Potential Sound file must have a text transcript. 17
a Likely Links to multimedia require a text transcript. 20
a Likely Links to multimedia have a link to text alternative. 145

Success Criteria 1.2.2 Captions (Prerecorded) (A)


None Found.

Success Criteria 1.2.3 Audio Description or Media Alternative (Prerecorded) (A)


Element Error Type Description Check ID
object Potential <code>object</code> link to multimedia file require equivalent alternatives (e.g., captions or auditory descriptions of the visual track). 146
object Potential <code>object</code> may require a long description. 160

Success Criteria 1.2.4 Captions (Live) (AA)


None Found.

Success Criteria 1.2.5 Audio Description (Prerecorded) (AA)


None Found.

Success Criteria 1.2.6 Sign Language (Prerecorded) (AAA)


None Found.

Success Criteria 1.2.7 Extended Audio Description (Prerecorded) (AAA)


None Found.

Success Criteria 1.2.8 Media Alternative (Prerecorded) (AAA)


None Found.

Success Criteria 1.2.9 Audio-only (Live) (AAA)


None Found.

1.3 Adaptable: Create content that can be presented in different ways without losing information or structure.


Success Criteria 1.3.1 Info and Relationships (A)


Element Error Type Description Check ID
body Potential Table markup is used for all tabular information. 241
body Potential All visual lists are marked. 248
body Potential Unicode right-to-left marks or left-to-right marks are used whenever the HTML bidirectional algorithm produces undesirable results. 270
body Potential All changes in text direction are marked using the <code>dir</code> attribute. 271
caption Potential Table captions identify the table. 242
form Known All radio button groups are marked using <code>fieldset</code> and <code>legend</code> elements. 168
form Known All checkbox groups are marked using <code>fieldset</code> and <code>legend</code> elements. 247
input Known All <code>input</code> elements, <code>type</code> of "text", have an explicitly associated label. 57
input Known All <code>input</code> elements, <code>type</code> of "password", have an explicitly associated <code>label</code>. 118
input Known All <code>input</code> elements, <code>type</code> of "checkbox", have an explicitly associated <code>label</code>. 119
input Known All <code>input</code> elements, <code>type</code> of "file", have an explicitly associated <code>label</code>. 120
input Known All <code>input</code> elements, <code>type</code> of "radio", have an explicitly associated <code>label</code>. 121
input Potential All <code>input</code> elements, <code>type</code> of "password", have a label that is positioned close to the control. 122
input Potential All <code>input</code> elements, <code>type</code> of "checkbox", have a label that is positioned close to the control. 123
input Potential All <code>input</code> elements, <code>type</code> of "file", have a label that is positioned close to the control. 124
input Potential All <code>input</code> elements, <code>type</code> of "radio", have a label that is positioned close to the control. 125
input Known All <code>input</code> elements, <code>type</code> of "radio", have a <code>label</code> containing text. 204
input Known All <code>input</code> elements, <code>type</code> of "checkbox", have a <code>label</code> containing text. 206
input Known All <code>input</code> elements, <code>type</code> of "password", have a <code>label</code> containing text. 207
input Potential All <code>input</code> elements, <code>type</code> of "text", have a label that is positioned close to the control. 211
input Known All <code>input</code> elements, <code>type</code> of "text", have a <code>label</code> containing text. 213
input Known All <code>input</code> elements, <code>type</code> of "file", have a <code>label</code> containing text. 216
p Likely All <code>p</code> elements are not used as headers. 82
pre Potential <code>pre</code> element should not be used to create tabular layout. 154
select Known All <code>select</code> elements have an explicitly associated <code>label</code>. 91
select Known All <code>select</code> elements have a label that contains text. 208
select Potential All <code>select</code> elements have a label that is positioned close to the control. 209
table Potential All complex data tables have a summary. 111
table Known All data <code>table</code> summaries contain text. 112
table Known All layout <code>tables</code> have an empty <code>summary</code> attribute or no <code>summary</code> attribute. 114
table Known All layout tables do not contain <code>caption</code> elements. 115
table Potential All data tables contain <code>th</code> elements. 136
table Potential All layout tables do not contain <code>th</code> elements. 137
table Potential All data tables contain a <code>caption</code> unless the table is identified within the document. 151
table Potential All data table summaries describe navigation and structure of the table. 203
table Potential Use <code>thead</code> to group repeated table headers, <code>tfoot</code> for repeated table footers, and <code>tbody</code> for other groups of rows. 230
table Potential Use <code>colgroup</code> and <code>col</code> elements to group columns. 231
table Known Table summaries do not duplicate the table captions. 243
table Known Data tables that contain both row and column headers use the <code>scope</code> attribute to identify cells. 244
table Known Data tables that contain more than one row/column of headers use the <code>id</code> and <code>headers</code> attributes to identify cells. 245
textarea Known All <code>textarea</code> elements have an explicitly associated label. 95
textarea Potential All <code>textarea</code> elements have a label that is positioned close to control. 96
textarea Known All <code>textarea</code> elements have a <code>label</code> containing text. 212

Success Criteria 1.3.2 Meaningful Sequence (A)


None Found.

Success Criteria 1.3.3 Sensory Characteristics (A)


Element Error Type Description Check ID
body Potential All text references do not use shape, size, or relative position alone. 250
table Potential All layout <code>tables</code> make sense when linearized. 133

1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.


Success Criteria 1.4.1 Use of Colour (A)


Element Error Type Description Check ID
body Known The luminosity contrast ratio between text and background color is at least 5:1. 221
body Known The luminosity contrast ratio between link text and background color is at least 5:1. 222
body Known The luminosity contrast ratio between active link text and background color is at least 5:1. 223
body Known The luminosity contrast ratio between visited link text and background color is at least 5:1. 224
body Known All text colors or no text colors are set. 252
img Potential The luminosity contrast ratio between text and background color in all images is at least 5:1. 251
input Potential <code>input</code> should not use color alone. 55
object Potential <code>object</code> must not use color alone. 73
script Potential Color alone should not be used in the <code>script</code>. 86

Success Criteria 1.4.2 Audio Control (A)


None Found.

Success Criteria 1.4.3 Contrast (Minimum) (AA)


None Found.

Success Criteria 1.4.4 Resize text (AA)


Element Error Type Description Check ID
b Known <code>b</code> (bold) element is not used. 116
basefont Known <code>basefont</code> must not be used. 176
font Known <code>font</code> must not be used. 177
i Known <code>i</code> (italic) element is not used. 117

Success Criteria 1.4.5 Images of Text (AA)


Element Error Type Description Check ID
img Potential Alt text for all <code>img</code> elements contains all text in the image unless the image text is decorative or appears elsewhere in the document. 11

Success Criteria 1.4.6 Contrast (Enhanced) (AAA)


Element Error Type Description Check ID
a Known Visited link text colour must provide high contrast with its background colour. 307
a Known Active link text colour must provide high contrast with its background colour. 308
a Known Selected link text colour must provide high contrast with its background colour. 309
a Known The contrast between the colour of link text and its background is not sufficient to meet WCAG2.0 Level AAA. 310
all elements Known Text colour must provide high contrast with its background colour 306
img Potential The luminosity contrast ratio between text and background color in all images is at least 10:1. 253

Success Criteria 1.4.7 Low or No Background Audio (AAA)


None Found.

Success Criteria 1.4.8 Visual Presentation (AAA)


None Found.

Success Criteria 1.4.9 Images of Text (No Exception) (AAA)


None Found.

2.1 Keyboard Accessible: Make all functionality available from a keyboard.


Success Criteria 2.1.1 Keyboard (A)


Element Error Type Description Check ID
all elements Potential All <code>ondblclick</code> event handlers have corresponding keyboard-specific functions. 103
all elements Known All <code>onmousedown</code> event handlers have an associated <code>onkeydown</code> event handler. 104
all elements Potential All <code>onmousemove</code> event handlers have corresponding keyboard-specific functions. 105
all elements Known All <code>onmouseout</code> event handlers have an associated <code>onblur</code> event handler. 106
all elements Known All <code>onmouseover</code> event handlers have an associated <code>onfocus</code> event handler. 107
all elements Known All <code>onmouseup</code> event handlers have an associated <code>onkeyup</code> event handler. 108
object Potential <code>object</code> user interface must be accessible - (codebase). 76
script Potential User interface for <code>script</code> must be accessible. 89

Success Criteria 2.1.2 No Keyboard Trap (A)


Element Error Type Description Check ID
applet Potential <code>applet</code> provides a keyboard mechanism to return focus to the parent window. 258
embed Potential <code>embed</code> provides a keyboard mechanism to return focus to the parent window. 260
object Potential <code>object</code> provides a keyboard mechanism to return focus to the parent window. 259

Success Criteria 2.1.3 Keyboard (No Exception) (AAA)


None Found.

2.2 Enough Time: Provide users enough time to read and use content.


Success Criteria 2.2.1 Timing Adjustable (A)


Element Error Type Description Check ID
meta Known Meta refresh is not used with a time-out. 72

Success Criteria 2.2.2 Pause, Stop, Hide (A)


Element Error Type Description Check ID
blink Known <code>blink</code> element is not used. 27
marquee Known <code>marquee</code> element is not used. 69
meta Known Auto-redirect must not be used. 71

Success Criteria 2.2.3 No Timing (AAA)


None Found.

Success Criteria 2.2.4 Interruptions (AAA)


None Found.

Success Criteria 2.2.5 Re-authenticating (AAA)


None Found.

2.3 Seizures: Do not design content in a way that is known to cause seizures.


Success Criteria 2.3.1 Three Flashes or Below Threshold (A)


Element Error Type Description Check ID
applet Potential <code>applets</code> cause screen flicker. 22
img Potential All <code>img</code> elements have associated images that do not flicker. 10
object Potential All <code>objects</code> do not flicker. 30
script Potential <code>script</code> should not cause screen flicker. 87

Success Criteria 2.3.2 Three Flashes (AAA)


None Found.

2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.


Success Criteria 2.4.1 Bypass Blocks (A)


Element Error Type Description Check ID
body Potential A "skip to content" link appears on all pages with blocks of material prior to the main document. 28
body Potential All groups of links with a related purpose are marked. 262
frame Known All <code>frames</code> have a <code>title</code> attribute. 31
frame Potential All <code>frame</code> <code>titles</code> identify the purpose or function of the <code>frame</code>. 32
pre Likely ASCII art should have a skipover link. 84

Success Criteria 2.4.10 Section Headings (AAA)


Element Error Type Description Check ID
body Potential Each section of content is marked with a <code>header</code> element. 261

Success Criteria 2.4.2 Page Titled (A)


Element Error Type Description Check ID
head Known Document contains a <code>title</code> element. 50
title Known <code>title</code> contains text. 51
title Likely <code>title</code> is short. 52
title Likely <code>title</code> is not placeholder text. 53
title Potential <code>title</code> describes the document. 54

Success Criteria 2.4.3 Focus Order (A)


None Found.

Success Criteria 2.4.4 Link Purpose (In Context) (A)


Element Error Type Description Check ID
a Potential Link text is meaningful when read out of context. 19
a Known Each source anchor contains text. 174
a Potential All source anchors contain text that identifies the link destination. 197

Success Criteria 2.4.5 Multiple Ways (AA)


Element Error Type Description Check ID
body Potential Sites must have a site map. 184

Success Criteria 2.4.6 Headings and Labels (AA)


Element Error Type Description Check ID
h1 Known The header following an <code>h1</code> is <code>h1</code> or <code>h2</code>. 37
h1 Potential All <code>h1</code> elements are not used for formatting. 42
h2 Known The header following an <code>h2</code> is <code>h1</code>, <code>h2</code> or <code>h3</code>. 38
h2 Potential All <code>h2</code> elements are not used for formatting. 43
h3 Known The header following an <code>h3</code> is <code>h1</code>, <code>h2</code>, <code>h3</code> or <code>h4</code>. 39
h3 Potential All <code>h3</code> elements are not used for formatting. 44
h4 Known The header following an <code>h4</code> is <code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code> or <code>h5</code>. 40
h4 Potential All <code>h4</code> elements are not used for formatting. 45
h5 Known The header following an <code>h5</code> is <code>h6</code> or any header less than <code>h6</code>. 41
h5 Potential All <code>h5</code> elements are not used for formatting. 46
h6 Potential All <code>h6</code> elements are not used for formatting. 47

Success Criteria 2.4.7 Focus Visible (AA)


None Found.

Success Criteria 2.4.8 Location (AAA)


Element Error Type Description Check ID
body Potential The document contains a breadcrumb trail if it is part of a collection. 266

Success Criteria 2.4.9 Link Purpose (Link Only) (AAA)


None Found.

3.1 Readable: Make text content readable and understandable


Success Criteria 3.1.1 Language of Page (A)


Element Error Type Description Check ID
html Known Document has required <code>lang</code> attribute(s). 48
html Known Document has valid language code. 49
html Known Reading order direction is marked using the html element's <code>dir</code> attribute if the document's primary language is read right to left. 273

Success Criteria 3.1.2 Language of Parts (AA)


Element Error Type Description Check ID
body Potential Words and phrases not in the document's primary language are marked. 110

Success Criteria 3.1.3 Unusual Words (AAA)


Element Error Type Description Check ID
body Potential Provide a reference to a glossary. 179

Success Criteria 3.1.4 Abbreviations (AAA)


Element Error Type Description Check ID
body Potential Abbreviations must be marked with <code>abbr</code> element. 98
body Potential Acronyms must be marked with <code>acronym</code> element. 99

Success Criteria 3.1.5 Reading Level (AAA)


None Found.

Success Criteria 3.1.6 Pronunciation (AAA)


None Found.

3.2 Predictable: Make Web pages appear and operate in predictable ways.


Success Criteria 3.2.1 On Focus (A)


Element Error Type Description Check ID
body Potential Loading the web page does not cause a new window to open. 275

Success Criteria 3.2.2 On Input (A)


Element Error Type Description Check ID
select Likely All <code>select</code> elements do not cause an extreme change in context. 92

Success Criteria 3.2.3 Consistent Navigation (AA)


Element Error Type Description Check ID
body Potential Repeated components appear in the same relative order each time they appear. 276
form Potential The tab order specified by <code>tabindex</code> attributes follows a logical order. 265
frameset Potential Repeated blocks of content appear in the same <code>frame</code> within the <code>frameset</code>. 263

Success Criteria 3.2.4 Consistent Identification (AA)


Element Error Type Description Check ID
blockquote Potential <code>blockquote</code> must not be used for indentation. 100
body Potential Use the <code>blockquote</code> element to mark up block quotations. 131
ol Likely List items must not be used to format text. 81

Success Criteria 3.2.5 Change on Request (AAA)


Element Error Type Description Check ID
all elements Potential Change of context occurs only by user activation unless a warning is provided. 274

3.3 Input Assistance: Help users avoid and correct mistakes.


Success Criteria 3.3.1 Error Identification (A)


Element Error Type Description Check ID
form Potential All form submission error messages identify any empty required fields. 267

Success Criteria 3.3.2 Labels or Instructions (A)


Element Error Type Description Check ID
body Known Each <code>input</code> element has only one associated <code>label</code>. 187
form Potential All <code>form</code> fields that are required are indicated to the user as required. 246
input Known Each label associated with an <code>input</code> element contains text. 188
input Potential Each label describes its asssociated <code>input</code> element. 189
input Potential All <code>input</code> elements, <code>type</code> of "file", have a <code>label</code> that describes the purpose or function of the control. 205
input Potential All <code>input</code> elements, <code>type</code> of "password", have a <code>label</code> that describes the purpose or function of the control. 217
input Potential All <code>input</code> elements, <code>type</code> of "text", have a <code>label</code> that describes the purpose or function of the control. 218
input Potential All <code>input</code> elements, <code>type</code> of "checkbox", have a <code>label</code> that describes the purpose or function of the control. 219
input Potential All <code>input</code> elements, <code>type</code> of "radio", have a <code>label</code> that describes the purpose or function of the control. 220
select Potential All <code>select</code> elements have a label that describes the purpose or function of the control. 210

Success Criteria 3.3.3 Error Suggestion (AA)


Element Error Type Description Check ID
form Potential All form submission error messages provide assistance in correcting the error. 268

Success Criteria 3.3.4 Error Prevention (Legal, Financial, Data) (AA)


Element Error Type Description Check ID
form Potential Form submission data is presented to the user before final acceptance for all irreversable transactions. 269

Success Criteria 3.3.5 Help (AAA)


None Found.

Success Criteria 3.3.6 Error Prevention (All) (AAA)


Element Error Type Description Check ID
form Potential Information deleted using a web page can be recovered. 272

4.1 Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.


Success Criteria 4.1.1 Parsing (A)


Element Error Type Description Check ID
body Known <code>id</code> attributes must be unique. 185

Success Criteria 4.1.2 Name, Role, Value (A)


None Found.


English | German | Italiano


Web site engine's code is copyright © 2011
Inclusive Design Institute
Web Service API