Copyright © 2005 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This is a W3C Working Draft produced by the Web Content Accessibility Guidelines Working Group (WCAG WG). It serves as an appendix to WCAG 2.0 Web Content Accessibility Guidelines 2.0 [WCAG20] and provides a checklist of all success criterion from the guidelines.
This document is for review by the WCAG WG and is subject to change without notice. This document has no formal standing within W3C. Please consult the group's home page and the W3C technical reports index for information about the latest publications by this group.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
Send comments about this document to the Web Content Accessibility Guidelines Working Group mailing list. The archives for this list are publicly available.
This document was produced under the 5 February 2004 W3C Patent Policy. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing [and excluding] a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy.
This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG WG are discussed in the Working Group charter. The WCAG WG is part of the WAI Technical Activity.
This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR/.
Note: To reduce the length of this document, some normative information about success criterion does not appear in the checklist below. Please refer to the Guidelines document for additional information.
Level 1 success criteria:
Achieve a minimum level of accessibility through markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies
Can reasonably be applied to all Web resources.
Level 2 success criteria:
Achieve an enhanced level of accessibility through one or both of the following:
markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies
the design of the content and presentation
Can reasonably be applied to all Web resources.
Level 3 success criteria:
Achieve additional accessibility enhancements for people with disabilities.
Are not applicable to all Web resources.
Satisfied | Success Criterion | Comments |
---|---|---|
For all non-text content that is used to convey information, text alternatives identify the non-text content and convey the same information. For multimedia, provide a text-alternative that identifies the multimedia. | ||
For functional non-text content, text alternatives serve the same purpose as the non-text content. If text alternatives can not serve the same purpose as the functional non-text content, text alternatives identify the purpose of the functional non-text content | ||
For non-text content that is intended to create a specific sensory experience, text alternatives at least identify the non-text content with a descriptive label. | ||
Non-text content that is not functional, is not used to convey information, and does not create a specific sensory experience is implemented such that it can be ignored by assistive technology. | ||
For live audio-only or live video-only content, text alternatives at least identify the purpose of the content with a descriptive label. | ||
For prerecorded multimedia content, a combined transcript of captions and audio descriptions of video is available. |
Satisfied | Success Criterion | Comments |
---|---|---|
Captions are provided for prerecorded multimedia. | ||
Audio descriptions of video are provided for prerecorded multimedia | ||
Real-time captions are provided for live multimedia. | ||
Sign language interpretation is provided for multimedia | ||
Extended audio descriptions of video are provided for prerecorded multimedia. | ||
Audio descriptions of video are provided for live multimedia. |
Satisfied | Success Criterion | Comments |
---|---|---|
Structures within the content can be programmatically determined. | ||
Information that is conveyed by color is also conveyed when color is not available, or can be programmatically determined. | ||
Information that is conveyed by variations in presentation of text is also conveyed when variations in presentation of text are not available, or can be programmatically determined. | ||
Any information that is conveyed through color is visually evident without having to interpret color. For example, the distinction can additionally be determined through context, characters, or symbols that accompany the color presentation, or through pattern differences such as dotted red vs. solid green lines in a graph. | ||
When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically. |
Satisfied | Success Criterion | Comments |
---|---|---|
Any text that is presented over a background image, color, or text can be programmatically determined. | ||
Text and diagrams that are presented over a background image, color, or text have a contrast greater than X1 where the whiter element is at least Y1 as measured by _____. | ||
Text that is presented over a background pattern of lines which are within 500% +/- of the stem width of the characters or their serifs must have a contrast between the characters and the lines that is greater than X2, where the whiter element is at least Y2. | ||
A mechanism is available to turn off background audio that plays automatically. | ||
Text is not presented over any background (image, text, color or pattern), or if any background is present, the contrast between the text and the background is greater than X2. | ||
Audio content does not contain background sounds or the background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects. |
Satisfied | Success Criterion | Comments |
---|---|---|
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface. | ||
All functionality of the content is designed to be operated through a keyboard interface. |
Satisfied | Success Criterion | Comments |
---|---|---|
Content is designed so that time-outs are not an essential part of interaction, or at least one of the following is true for each time-out that is a function of the content:
| ||
Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit. | ||
Moving or time-based content can be paused by the user. | ||
Except for real-time events, timing is not an essential part of the event or activity presented by the content. | ||
Non-emergency interruptions, such as the availability of updated content, can be postponed or suppressed by the user. | ||
When an authenticated session has an inactivity timeout, the user can continue the activity without loss of data after re-authenticating. |
Satisfied | Success Criterion | Comments |
---|---|---|
Content that violates international health and safety standards for general flash or red flash is marked in a way that the user can avoid its appearance. | ||
Content does not violate international health and safety standards for general flash or red flash. | ||
Content does not violate international health and safety standards for spatial pattern thresholds or red flash. |
Satisfied | Success Criterion | Comments |
---|---|---|
More than one way is available to locate content within a set of delivery units. | ||
Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed. | ||
Delivery units have descriptive titles | ||
The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined. | ||
When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content. | ||
Information about the user's location within a set of delivery units is available. |
Satisfied | Success Criterion | Comments |
---|---|---|
The primary natural language or languages of the delivery unit can be programmatically determined. | ||
The natural language of each foreign passage or phrase in the content can be programmatically determined. | ||
A mechanism is available for finding definitions for all words in text content. | ||
A mechanism is available for identifying specific definitions of words used in an unusual or restricted way, including idioms and jargon. | ||
A mechanism for finding the expanded form of acronyms and abbreviations is available. | ||
Section titles are descriptive. | ||
When text requires reading ability at or above the upper secondary education level, one or more of the following supplements is available:
|
Satisfied | Success Criterion | Comments |
---|---|---|
Any change of context is implemented in a manner that can be programmatically determined. | ||
Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated. | ||
When any component receives focus, it does not cause a change of context. | ||
Changing the setting of any input field does not automatically cause a change of context . | ||
Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently. | ||
Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear. | ||
Changes of context are initiated only by user action. |
Satisfied | Success Criterion | Comments |
---|---|---|
SGML-based delivery units are well-formed. | ||
Non-SGML-based delivery units are formatted according to their content type specification. | ||
Except where the author has documented that a specification was violated for user agent compatibility (including compatibility with assistive technology), the content has:
|
Satisfied | Success Criterion | Comments |
---|---|---|
For any technologies not in the specified baseline, the following are true:
| ||
Any programmatic user interface components of the content conform to at least the default set of conformance requirements of the UAAG 1.0 at Level A plus the sets of requirements (a) through (i) (below) that apply. If the custom user interfaces cannot be made accessible, an alternative solution is provided that meets WCAG 2.0 (including this provision) to the level claimed.
| ||
Accessibility conventions of the markup or programming language (API's or specific markup) are used. |