Web Content Accessibility Guidelines 2.0 Checklist

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.

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.

1.3 L1 SC1:

Structures within the content can be programmatically determined.

1.3 L1 SC2:

Information that is conveyed by color is also conveyed when color is not available, or can be programmatically determined.

1.3 L2 SC1:

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.

1.3 L2 SC2:

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.

1.3 L3 SC1:

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

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.

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.

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.

2.3 L1 SC1:

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.

2.3 L2 SC1:

Content does not violate international health and safety standards for general flash or red flash.

2.3 L3 SC1:

Content does not violate international health and safety standards for spatial pattern thresholds or red flash.

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.

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:

1. A text summary that requires reading ability no higher than primary education level.

2. Graphical illustrations of concepts or processes that must be understood in order to use the content.

3. A spoken version of the text content.

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

4.1 L1 SC1:

SGML-based delivery units are well-formed.

4.1 L1 SC2:

Non-SGML-based delivery units are formatted according to their content type specification.

4.1 L2 SC1:

Except where the author has documented that a specification was violated for user agent compatibility (including compatibility with assistive technology), the content has:

1. passed validity tests for the version of the technology in use (whether it be conforming to a schema, Document Type Definition (DTD), or other tests described in the specification), and

2. used technology features as defined in the specification.

4.2 L1 SC1:

For any technologies not in the specified baseline, the following are true:

1. The Web content still conforms using user agents that only support the technologies that are in the baseline (i.e. the use of technologies that are not in the baseline does not "break" access to the Web content by user agents that don't support those technologies.)

2. All content and functionality are available using only the technologies in the specified baseline.

4.2 L1 SC2:

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.

1. If the application renders visual text, it should conform to the VisualText checkpoints.

2. If the application renders images, it should conform to the Image checkpoints.

3. If the application renders animations, it should conform to the Animation checkpoints.

4. If the application renders video, it should conform to the Video checkpoints.

5. If the application renders audio, it should conform to the Audio checkpoints.

6. If the application performs its own event handling, it should conform to the Events checkpoints.

7. If the application implements a selection mechanism, it should conform to the Selection checkpoints.

8. The application should support keyboard access per UAAG 1.0 checkpoints 1.1 and 6.7.

9. If the application implements voice or pointer input, it should conform to the Input Modality checkpoints.

4.2 L2 SC1:

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