Web Content Accessibility Guidelines 2.0 Checklist

Abstract

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.

Status of this Document

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

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.

Levels

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:
1. Achieve a minimum level of accessibility through markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies.
2. Can reasonably be applied to all Web resources.
Level 2 success criteria:
1. Achieve an enhanced level of accessibility through one or both of the following:
  1. markup, scripting, or other technologies that interact with or enable access through user agents, including assistive technologies
  2. the design of the content and presentation
2. Can reasonably be applied to all Web resources.
Level 3 success criteria:
1. Achieve additional accessibility enhancements for people with disabilities.
2. Are not applicable to all Web resources.

Checklist

Guideline 1.1: Provide text alternatives for all non-text content.

Satisfied

Success Criterion

Comments

1.1 L1 SC1:

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.

1.1 L1 SC2:

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

1.1 L1 SC3:

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.

1.1 L1 SC4:

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.

1.1 L1 SC5:

For live audio-only or live video-only content, text alternatives at least identify the purpose of the content with a descriptive label.

1.1 L3 SC1:

For prerecorded multimedia content, a combined transcript of captions and audio descriptions of video is available.

Guideline 1.2: Provide synchronized alternatives for multimedia.

Satisfied

Success Criterion

Comments

1.2 L1 SC1:

Captions are provided for prerecorded multimedia.

1.2 L1 SC2:

Audio descriptions of video are provided for prerecorded multimedia

1.2 L2 SC1:

Real-time captions are provided for live multimedia.

1.2 L3 SC1:

Sign language interpretation is provided for multimedia

1.2 L3 SC2:

Extended audio descriptions of video are provided for prerecorded multimedia.

1.2 L3 SC3:

Audio descriptions of video are provided for live multimedia.

Guideline 1.3: Ensure that information, functionality, and structure can be separated from presentation.

Satisfied

Success Criterion

Comments

1.3 L1 SC1:

Structures within the content can be programmatically determined.

1.3 L1 SC2:

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.

1.3 L2 SC1:

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.

1.3 L2 SC2:

Any information that is conveyed by color is visually evident when color is not available.

1.3 L3 SC1:

When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.

Guideline 1.4: Make it easy to distinguish foreground information from background images or sounds.

Satisfied

Success Criterion

Comments

1.4 L1 SC1:

Any text that is presented over a background image, color, or text can be programmatically determined.

1.4 L2 SC1:

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

1.4 L2 SC2:

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.

1.4 L2 SC3:

A mechanism is available to turn off background audio that plays automatically.

1.4 L3 SC1:

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.

1.4 L3 SC2:

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.

Guideline 2.1: Make all functionality operable via a keyboard interface.

Satisfied

Success Criterion

Comments

2.1 L1 SC1:

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.

2.1 L3 SC1:

All functionality of the content is designed to be operated through a keyboard interface.

Guideline 2.2: Allow users to control time limits on their reading or interaction.

Satisfied

Success Criterion

Comments

2.2 L1 SC1:

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:

the user is allowed to deactivate the time-out or;
the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;
the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond or;
the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible or;
the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.

2.2 L2 SC1:

Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit.

2.2 L2 SC2:

Moving or time-based content can be paused by the user.

2.2 L3 SC1:

Except for real-time events, timing is not an essential part of the event or activity presented by the content.

2.2 L3 SC2:

Non-emergency interruptions, such as the availability of updated content, can be postponed or suppressed by the user.

2.2 L3 SC3:

When an authenticated session has an inactivity timeout, the user can continue the activity without loss of data after re-authenticating.

Guideline 2.3: Allow users to avoid content that could cause seizures due to photosensitivity.

Satisfied

Success Criterion

Comments

2.3 L1 SC1:

Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance.

2.3 L2 SC1:

Content does not violate Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash.

2.3 L3 SC1:

Content does not violate Computer adapted spatial pattern thresholds or red flash.

Guideline 2.4: Provide mechanisms to help users find content, orient themselves within it, and navigate through it.

Satisfied

Success Criterion

Comments

2.4 L1 SC1:

Navigational features can be programmatically identified.

2.4 L2 SC1:

More than one way is available to locate content within a set of delivery units.

2.4 L2 SC2:

Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed.

2.4 L2 SC3:

Delivery units have descriptive titles

2.4 L2 SC4:

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.

2.4 L3 SC1:

When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content.

2.4 L3 SC2:

Information about the user's location within a set of delivery units is available.

Guideline 2.5: Help users avoid mistakes and make it easy to correct them.

Satisfied

Success Criterion

Comments

2.5 L2 SC1:

If an input error is detected, the error is identified and provided to the user in text.

2.5 L2 SC2:

If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the error is identified and the suggestions are provided to the user.

2.5 L2 SC3:

For forms that cause legal or financial transactions to occur, that modify or delete data in remote data storage systems, or that submit test responses, at least one of the following is true:

Actions are reversible.
Actions are checked for errors before going on to the next step in the process.
The user is able to review and confirm or correct information before submitting it.

2.5 L3 SC1:

Additional context-relevant assistance is available for text input.

Guideline 3.1: Make text content readable and understandable.

Satisfied

Success Criterion

Comments

3.1 L1 SC1:

The primary natural language or languages of the delivery unit can be programmatically determined.

3.1 L2 SC1:

The natural language of each foreign passage or phrase in the content can be programmatically determined.

3.1 L3 SC1:

A mechanism is available for finding definitions for all words in text content.

3.1 L3 SC2:

A mechanism is available for identifying specific definitions of words used in an unusual or restricted way, including idioms and jargon.

3.1 L3 SC3:

A mechanism for finding the expanded form of acronyms and abbreviations is available.

3.1 L3 SC4:

Section titles are descriptive.

3.1 L3 SC5:

When text requires reading ability at or above the upper secondary education level, one or more of the following supplements is available:

A text summary that requires reading ability no higher than primary education level.
Graphical illustrations of concepts or processes that must be understood in order to use the content.
A spoken version of the text content.

Guideline 3.2: Make the placement and functionality of content predictable.

Satisfied

Success Criterion

Comments

3.2 L1 SC1:

Any change of context is implemented in a manner that can be programmatically determined.

3.2 L2 SC1:

Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated.

3.2 L2 SC2:

When any component receives focus, it does not cause a change of context.

3.2 L2 SC3:

Changing the setting of any input field does not automatically cause a change of context .

3.2 L2 SC4:

Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.

3.2 L3 SC1:

Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear.

3.2 L3 SC2:

Changes of context are initiated only by user request.

Guideline 4.2: Ensure that user interfaces are accessible or provide an accessible alternative(s)

Satisfied

Success Criterion

Comments

4.2 L1 SC1:

If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.

4.2 L1 SC2:

Content using baseline technologies or non-baseline technologies, must meet the following criteria:

Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance.
If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.

4.2 L1 SC3:

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.

4.2 L1 SC4:

The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control.

4.2 L1 SC5:

The states and values of content that can be changed via the user interface can also be changed programmatically.

4.2 L1 SC6:

Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.

4.2 L2 SC1:

Accessibility conventions of the markup or programming language (API's or specific markup) are used.

4.2 L3 SC1:

Content implemented using technologies outside of baseline follows all WCAG requirements supported by the technology.

Web Content Accessibility Guidelines 2.0 Checklist

Editor's Draft 9 August 2005

Abstract

Status of this Document

Levels

Checklist

Appendix A References

Satisfied	Success Criterion	Comments
	1.1 L1 SC1: 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.
	1.1 L1 SC2: 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
	1.1 L1 SC3: 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.
	1.1 L1 SC4: 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.
	1.1 L1 SC5: For live audio-only or live video-only content, text alternatives at least identify the purpose of the content with a descriptive label.
	1.1 L3 SC1: For prerecorded multimedia content, a combined transcript of captions and audio descriptions of video is available.

Satisfied	Success Criterion	Comments
	1.2 L1 SC1: Captions are provided for prerecorded multimedia.
	1.2 L1 SC2: Audio descriptions of video are provided for prerecorded multimedia
	1.2 L2 SC1: Real-time captions are provided for live multimedia.
	1.2 L3 SC1: Sign language interpretation is provided for multimedia
	1.2 L3 SC2: Extended audio descriptions of video are provided for prerecorded multimedia.
	1.2 L3 SC3: Audio descriptions of video are provided for live multimedia.

Satisfied	Success Criterion	Comments
	1.3 L1 SC1: Structures within the content can be programmatically determined.
	1.3 L1 SC2: 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.
	1.3 L2 SC1: 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.
	1.3 L2 SC2: Any information that is conveyed by color is visually evident when color is not available.
	1.3 L3 SC1: When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.

Satisfied	Success Criterion	Comments
	1.4 L1 SC1: Any text that is presented over a background image, color, or text can be programmatically determined.
	1.4 L2 SC1: 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 _____.
	1.4 L2 SC2: 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.
	1.4 L2 SC3: A mechanism is available to turn off background audio that plays automatically.
	1.4 L3 SC1: 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.
	1.4 L3 SC2: 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
	2.1 L1 SC1: 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.
	2.1 L3 SC1: All functionality of the content is designed to be operated through a keyboard interface.

Satisfied	Success Criterion	Comments
	2.2 L1 SC1: 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: the user is allowed to deactivate the time-out or; the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or; the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond or; the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible or; the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.
	2.2 L2 SC1: Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit.
	2.2 L2 SC2: Moving or time-based content can be paused by the user.
	2.2 L3 SC1: Except for real-time events, timing is not an essential part of the event or activity presented by the content.
	2.2 L3 SC2: Non-emergency interruptions, such as the availability of updated content, can be postponed or suppressed by the user.
	2.2 L3 SC3: 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
	2.3 L1 SC1: Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance.
	2.3 L2 SC1: Content does not violate Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash.
	2.3 L3 SC1: Content does not violate Computer adapted spatial pattern thresholds or red flash.

Satisfied	Success Criterion	Comments
	2.4 L1 SC1: Navigational features can be programmatically identified.
	2.4 L2 SC1: More than one way is available to locate content within a set of delivery units.
	2.4 L2 SC2: Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed.
	2.4 L2 SC3: Delivery units have descriptive titles
	2.4 L2 SC4: 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.
	2.4 L3 SC1: When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content.
	2.4 L3 SC2: Information about the user's location within a set of delivery units is available.

Satisfied	Success Criterion	Comments
	2.5 L2 SC1: If an input error is detected, the error is identified and provided to the user in text.
	2.5 L2 SC2: If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the error is identified and the suggestions are provided to the user.
	2.5 L2 SC3: For forms that cause legal or financial transactions to occur, that modify or delete data in remote data storage systems, or that submit test responses, at least one of the following is true: Actions are reversible. Actions are checked for errors before going on to the next step in the process. The user is able to review and confirm or correct information before submitting it.
	2.5 L3 SC1: Additional context-relevant assistance is available for text input.

Satisfied	Success Criterion	Comments
	3.1 L1 SC1: The primary natural language or languages of the delivery unit can be programmatically determined.
	3.1 L2 SC1: The natural language of each foreign passage or phrase in the content can be programmatically determined.
	3.1 L3 SC1: A mechanism is available for finding definitions for all words in text content.
	3.1 L3 SC2: A mechanism is available for identifying specific definitions of words used in an unusual or restricted way, including idioms and jargon.
	3.1 L3 SC3: A mechanism for finding the expanded form of acronyms and abbreviations is available.
	3.1 L3 SC4: Section titles are descriptive.
	3.1 L3 SC5: When text requires reading ability at or above the upper secondary education level, one or more of the following supplements is available: A text summary that requires reading ability no higher than primary education level. Graphical illustrations of concepts or processes that must be understood in order to use the content. A spoken version of the text content.

Satisfied	Success Criterion	Comments
	3.2 L1 SC1: Any change of context is implemented in a manner that can be programmatically determined.
	3.2 L2 SC1: Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated.
	3.2 L2 SC2: When any component receives focus, it does not cause a change of context.
	3.2 L2 SC3: Changing the setting of any input field does not automatically cause a change of context .
	3.2 L2 SC4: Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.
	3.2 L3 SC1: Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear.
	3.2 L3 SC2: Changes of context are initiated only by user request.

Satisfied	Success Criterion	Comments
	4.2 L1 SC1: If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.
	4.2 L1 SC2: Content using baseline technologies or non-baseline technologies, must meet the following criteria: Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance. If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.
	4.2 L1 SC3: 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.
	4.2 L1 SC4: The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control.
	4.2 L1 SC5: The states and values of content that can be changed via the user interface can also be changed programmatically.
	4.2 L1 SC6: Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.
	4.2 L2 SC1: Accessibility conventions of the markup or programming language (API's or specific markup) are used.
	4.2 L3 SC1: Content implemented using technologies outside of baseline follows all WCAG requirements supported by the technology.