WCAG 1.0 (Level AAA)

Abbreviation WCAG1-AAA
Long Name Web Content Accessibility Guidelines (WCAG), Version 1.0, Level AAA
Published Date 2004-03-17
URL http://www.w3.org/TR/WCAG10/#aaa
Status Enabled
Open To Public Yes


Checks


Priority 1


1.1 Provide a text equivalent for every non-text element.


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
applet Potential <code>applet</code> contains a text equivalent in the <code>alt</code> attribute of the <code>applet</code>. 23
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
area Likely <code>area</code> link to sound file must have text transcript. 66
img Known All <code>img</code> elements have an <code>alt</code> attribute. 1
img Likely Non-Decorative images must have Alt text. 4
img Likely Important images should not have spacer Alt text. 5
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 contains all text in the image unless the image text is decorative or appears elsewhere in the document. 11
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
object Potential <code>object</code> link to multimedia file must have text transcript. 77
object Known <code>object</code> must have a <code>title</code>. 78
object Known <code>object</code> must have a valid <code>title</code>. 79
object Potential All <code>objects</code> contain a text equivalent of the <code>object</code>. 80

1.2 Provide redundant text links for each active region of a server-side image map.


None Found.

1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.


None Found.

1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.


None Found.

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.


Element Error Type Description Check ID
applet Potential <code>applet</code> should not use color alone. 21
img Potential For all <code>img</code> elements, text does not refer to the image by color alone. 14
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

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).


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

5.1 For data tables, identify row and column headers.


Element Error Type Description Check ID
table Potential All data tables contain <code>th</code> elements. 136

6.1 Organize documents so they may be read without style sheets.


Element Error Type Description Check ID
all elements Likely Content must be readable when stylesheets are not applied. 109
link Potential Document must be readable when stylesheets are not applied. 97
script Likely Content must be readable when stylesheets are not applied (SCRIPT). 94

6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.


Element Error Type Description Check ID
applet Potential Text equivalents for <code>applet</code> must be updated if <code>applet</code> changes. 24
object Potential Text equivalents for <code>object</code> should be updated if <code>object</code> changes - (codebase). 74
object Potential Text equivalents for <code>object</code> should be updated if <code>object</code> changes - (classid). 127

6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.


Element Error Type Description Check ID
applet Potential <code>applet</code> contains a text equivalent in the body of the <code>applet</code>. 25
object Potential Content must be usable when <code>object</code> are disabled. 75
object Potential Content must be usable when <code>object</code>s are disabled. 128

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.


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

8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.


Element Error Type Description Check ID
applet Potential <code>applet</code> user interface must be accessible. 26
object Potential <code>object</code> user interface must be accessible - (codebase). 76
object Potential <code>object</code> user interface must be accessible - (classid). 129
script Potential User interface for <code>script</code> must be accessible. 89

9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.


Element Error Type Description Check ID
img Known All <code>img</code> elements with an <code>ismap</code> attribute have a valid <code>usemap</code> attribute. 12

11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.


None Found.

12.1 Title each frame to facilitate frame identification and navigation.


Element Error Type Description Check ID
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

14.1 Use the clearest and simplest language appropriate for a site's content.


None Found.

Priority 2


2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.


None Found.

3.1 When an appropriate markup language exists, use markup rather than images to convey information.


Element Error Type Description Check ID
img Potential All <code>img</code> elements with images containing math expressions have equivalent MathML markup. 135

3.2 Create documents that validate to published formal grammars.


Element Error Type Description Check ID
html Known Document validates to specification. 232

3.3 Use style sheets to control layout and presentation.


Element Error Type Description Check ID
basefont Known <code>basefont</code> must not be used. 176
font Known <code>font</code> must not be used. 177

3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.


None Found.

3.5 Use header elements to convey document structure and use them according to specification.


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 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

3.6 Mark up lists and list items properly.


Element Error Type Description Check ID
menu Likely <code>menu</code> items should not be used to format text. 70
ol Likely List items must not be used to format text. 81

3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.


Element Error Type Description Check ID
blockquote Potential <code>blockquote</code> must not be used for indentation. 100

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.


Element Error Type Description Check ID
table Potential All layout tables do not contain <code>th</code> elements. 137

6.4 For scripts and applets, ensure that event handlers are input device-independent.


Element Error Type Description Check ID
all elements Known All <code>onclick</code> event handlers have an associated <code>onkeypress</code> event handler. 102
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

6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.


Element Error Type Description Check ID
frameset Known <code>frameset</code> must have a <code>noframes</code> section. 35
noframes Potential NOFRAMES section must contain text equivalent of FRAMES section. 36

7.2 Until user agents allow users to control blinking, avoid causing content to blink.


Element Error Type Description Check ID
blink Known <code>blink</code> element is not used. 27

7.3 Until user agents allow users to freeze moving content, avoid movement in pages.


Element Error Type Description Check ID
marquee Known <code>marquee</code> element is not used. 69

7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.


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

7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically.


Element Error Type Description Check ID
meta Known Auto-redirect must not be used. 71

9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.


None Found.

9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.


None Found.

10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.


Element Error Type Description Check ID
a Likely Anchor should not open new window without warning. 18
area Likely <code>area</code> should not open new window without warning. 68

10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.


Element Error Type Description Check ID
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
textarea Potential All <code>textarea</code> elements have a label that is positioned close to control. 96

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.


None Found.

11.2 Avoid deprecated features of W3C technologies.


None Found.

12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.


Element Error Type Description Check ID
frameset Likely Relationship between <code>frames</code> must be described. 34

12.3 Divide large blocks of information into more manageable groups where natural and appropriate.


None Found.

12.4 Associate labels explicitly with their controls.


Element Error Type Description Check ID
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 "radio", have an explicitly associated <code>label</code>. 121
select Known All <code>select</code> elements have an explicitly associated <code>label</code>. 91
textarea Known All <code>textarea</code> elements have an explicitly associated label. 95

13.1 Clearly identify the target of each link.


Element Error Type Description Check ID
a Potential Link text is meaningful when read out of context. 19
a Likely Suspicious link text. 173

13.2 Provide metadata to add semantic information to pages and sites.


Element Error Type Description Check ID
head Known Document contains a <code>title</code> element. 50
html Known Content must have an <code>address</code> for author. 143
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

13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).


None Found.

13.4 Use navigation mechanisms in a consistent manner.


None Found.

Priority 3


1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.


Element Error Type Description Check ID
img Known All links in all client side image-maps are duplicated within the document. 13

4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.


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

4.3 Identify the primary natural language of a document.


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

5.5 Provide summaries for tables.


Element Error Type Description Check ID
table Potential All complex data tables have a summary. 111
table Known All data <code>table</code> summaries contain text. 112
table Likely All data <code>table</code> summaries are greater than 10 printable characters (English). 113
table Known All layout <code>tables</code> have an empty <code>summary</code> attribute or no <code>summary</code> attribute. 114

9.4 Create a logical tab order through links, form controls, and objects.


Element Error Type Description Check ID
input Known All <code>input</code> elements, <code>type</code> of "text", have a valid tab index. 138
input Known All <code>input</code> elements, <code>type</code> of "radio", have a valid tab index. 139
input Known All <code>input</code> elements, <code>type</code> of "password", have a valid tab index. 140
input Known All <code>input</code> elements, <code>type</code> of "checkbox", have a valid tab index. 141
input Known All <code>input</code> elements, <code>type</code> of "file", have a valid tab index. 142

10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.


None Found.

10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.


None Found.

10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.


Element Error Type Description Check ID
a Known Include non-link, printable characters (surrounded by spaces) between adjacent links. 134

11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)


None Found.

13.10 Provide a means to skip over multi-line ASCII art.


Element Error Type Description Check ID
pre Likely ASCII art should have a skipover link. 84

13.5 Provide navigation bars to highlight and give access to the navigation mechanism.


None Found.

13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.


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

13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.


None Found.

13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.


None Found.

13.9 Provide information about document collections (i.e., documents comprising multiple pages.).


None Found.

14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.


None Found.

14.3 Create a style of presentation that is consistent across pages.


None Found.


English | German | Italiano


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