[guidelines] [linear checklist]
Copyright © 2005 W3C ® ( MIT , ERCIM , Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
The Web Content Accessibility Guidelines 2.0 Checklist serves as an appendix to Web Content Accessibility Guidelines 2.0 [WCAG20]. It lists all of the success criteria from WCAG 2.0 in a checkable list. The level of each success criterion is provided as well as a link to WCAG 2.0 for more information for each success criterion. For many readers, the Checklist provides a quick reference and overview to the information in WCAG 2.0.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This is a W3C First Public Working Draft of WCAG 2.0 Checklists. Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document will be published as a W3C Recommendation at the time that WCAG 2.0 becomes a W3C Recommendation. Since the Checklist is essential to many people's use of WCAG 2.0, the Web Content Accessibility Guidelines Working Group (WCAG WG) encourages feedback about this Working Draft. In particular, is the information presented clearly? Is this format an effective tool to help determine conformance to WCAG 2.0? Please use the WCAG 2.0 Checklist to a review a site and provide feedback about the usefulness of the Checklist for a review process. Please send comments about this document to the public-comments-wcag20@w3.org. The archives for this list are publicly available. Archives of the WCAG WG mailing list are also 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.
Per section 4 of the W3C Patent Policy, Working Group participants have 150 days from the title page date of this document to exclude essential claims from the W3C RF licensing requirements with respect to this document series. Exclusions are with respect to the exclusion reference document, defined by the W3C Patent Policy to be the latest version of a document in this series that is published no later than 90 days after the title page date of this document.
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.
Note: To reduce the length of this document, some normative information about success criteria 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. |
|
|
When information is conveyed by color, the color can be programmatically determined or the information is also conveyed through another means that does not depend on the user's ability to differentiate colors. |
|
|
Information that is conveyed by variations in presentation of text is also conveyed in text or the variations in presentation of text can be programmatically determined. |
|
|
Any information that is conveyed by color is visually evident when color is not available. |
|
|
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 |
---|---|---|
Satisfied | Success Criterion | Comments |
---|---|---|
|
If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria. |
|
|
Content using baseline technologies or non-baseline technologies, must meet the following criteria:
|
|
|
The role, state, and value can be programmatically determined for every user interface component of the web content that accepts input from the user or changes dynamically in response to user input or external events. |
|
|
The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control. |
|
|
The states and values of content that can be changed via the user interface can also be changed programmatically. |
|
|
Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined. |
|
|
Accessibility conventions of the markup or programming language (API's or specific markup) are used. |
|
|
Content implemented using technologies outside of baseline follows all WCAG requirements supported by the technology. |