Web checklist

1.1a

Text alternatives. All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

1.1b

Non-text content. A descriptive label is provided for time-based media, including live audio-only and live video-only content. Non-text content that is used to confirm that content is being accessed by a person rather than a computer is available in different forms to accommodate multiple disabilities.

1.1c

Image maps. Client-side image maps are used and alternative text is provided for image map hot spots. Equivalent text links are provided if a server-side image map is used.

1.2a

Captions. Captions are provided for prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

1.2b

Audio and video (prerecorded). An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

1.2c

Live multimedia. Captions are provided for live multimedia.

1.2 AA

Requirements to meet Web checklist guideline 1.2 WCAG 2.0 Level AA.

1.3a

Information and relationships. Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

1.3b

Removed: This checkpoint is now covered by Guideline 1.4a.

1.3c

Meaningful sequence. When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

1.3d

Forms. Form element labels can be programmatically determined.

1.3e

Tables. Table cells and relationships between cells can be programmatically determined.

1.3f

Cascading style sheets. Web pages are readable without requiring style sheets.

1.3g

Sensory characteristics. Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

1.4a

Use of color. Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

1.4b

Audio control. If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

1.4 AA

Requirements to meet Web checklist guideline 1.4 WCAG 2.0 Level AA.

2.1a

Keyboard. All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

2.1b

Scripts. Scripts are keyboard accessible. If the content affected by scripting is not accessible, an alternative is provided.

2.1c

Applets, plug-ins, and non-HTML content. A link is provided to a directly accessible applet, plug-in or other application. Alternate content is provided for those applets, plug-ins or other applications that are not directly accessible.

2.1d

No keyboard trap. If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys, the user is advised of the method for moving focus away.

2.2a

Adjust time response. The user is allowed to turn off, adjust or extend all time limits that are not a real-time, essential or 20 hour exception.

2.2b

Pause, stop, hide. The user is allowed to pause, stop, or hide moving, blinking, scrolling, or auto-updating information unless it is an essential part of an activity.

2.3a

Flashing Content or below threshold. Web pages do not contain anything that flashes more than two times in any one second period, or the flash is below the general flash and red flash thresholds.

2.4a

Navigational features. A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

2.4b

Navigate to main content. Methods are provided for skipping over navigation links to get to the main content of the page.

2.4c

Frames. A title and an accessible frame source are provided for each frame.

2.4d

Page titles. Web pages have titles that describe topic or purpose.

2.4e

Focus order. If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

2.4f

Link purpose. The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

2.4 AA

Requirements to meet Web checklist guideline 2.4 WCAG 2.0 Level AA.

3.1a

Language of page. The default human language of each Web page can be programmatically determined.

3.1 AA

Requirements to meet Web checklist guideline 3.1 WCAG 2.0 Level AA.

3.2a

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

3.2b

On input. Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

3.2 AA

Requirements to meet Web checklist guideline 3.2 WCAG 2.0 Level AA.

3.3a

Error identification. If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

3.3b

Labels or instructions. Labels or instructions are provided when content requires user input.

3.3 AA

Requirements to meet Web checklist guideline 3.3 WCAG 2.0 Level AA.

4.1a

Parsing. In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

4.1b

Name, role, value. For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

4.2a

Text-only page. If accessibility cannot be accomplished in any other way, a text-only page with equivalent information or functionality is provided.

4.2b

Accessibility-supported technologies only. Use accessibility supported technologies. Any information or functionality that is implemented in technologies that are not accessibility supported must also be available via technologies that are accessibility supported.