Checkpoints on applets and scripts - Checkpoint 6.3

Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.

Checkpoints on frames - Checkpoint 12.1

Title each frame to facilitate frame identification and navigation.

Checkpoints on image maps - Checkpoint 1.2

Provide redundant text links for each active region of a server-side image map.

Checkpoints on image maps - Checkpoint 9.1

Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Checkpoints on tables - Checkpoints 5.1 and 5.2

For data tables, identify row and column headers. For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.

General Checkpoints - Checkpoint 1.1

Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.

General Checkpoints - Checkpoint 14.1

Use the clearest and simplest language appropriate for a site's content.

General checkpoints - Checkpoint 2.1

Ensure that all information conveyed with color is also available without color, for example from context or markup.

General checkpoints - Checkpoint 4.1

Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

General checkpoints - Checkpoint 6.1

Organise documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.

General Checkpoints - Checkpoint 6.2

Ensure that equivalents for dynamic content are updated when the dynamic content changes.

General Checkpoints - Checkpoint 7.1

Until user agents allow users to control flickering, avoid causing the screen to flicker.

If you can't make it accessible - Checkpoint 11.4

If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.

Introduction to the Level A checkpoints

Conforming to the W3C Web Content Accessibility Guidelines will ensure that your site contains many features that will assist people with disabilities. These checkpoints cover the most difficult areas of web design and development that makes browsing a web site particularly difficult for people with disabilities.

Level A checkpoints and Non-Level A essential checkpoints

A listing of the Web Accessibility Initiative Level A checkpoints and Non-Level A essential checkpoints.

Non-Level A essential checkpoints - Checkpoint 10.1

Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.

Non-Level A essential checkpoints - Checkpoint 10.2

Use interim solutions. This is to ensure that people using magnifiers and those with cognitive disabilities can understand the required input for a particular field.

Non-Level A essential checkpoints - Checkpoint 12.4

Associate labels explicitly with their controls.

Non-Level A essential checkpoints - Checkpoint 13.1

Clearly identify the target of each link.

Non-Level A essential checkpoints - Checkpoint 3.2

Create documents that validate to published formal grammars.