Web Content Accessibility Guidelines 1.0

Checklist of Checkpoints

Priority 1 checkpoints

In General (Priority 1)

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.

WHV compliance: All images have an alt tag. Images are for presentation or enhanced navigation only.

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

WHV compliance: Colour is not used to convey information of web pages. It is only used for presentation of text.

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

WHV compliance: English is the only language used on the site.

6.1 Organize 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.

WHV compliance: No content is generated though style sheets. They are used for presentation of fonts and bulleted lists only.

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

WHV compliance: No applets or objects exist on site. The Noscript element exists on all pages to replace navigation if menu script is disabled.

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

WHV compliance: No flickering has been coded.

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

WHV compliance: Clear and simple language has been used in site content.

And if you use images and image maps (Priority 1)

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

WHV compliance: No server-side image maps exist on the site.

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.

WHV compliance: No image maps exist on the site.

And if you use tables (Priority 1)

5.1 For data tables, identify row and column headers.

WHV compliance: Tables have been used for layout only.

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

WHV compliance: Tables have been used for layout only.

And if you use frames (Priority 1)

12.1 Title each frame to facilitate frame identification and navigation.

WHV compliance: No frames exist on the site.

And if you use applets and scripts (Priority 1)

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.

WHV compliance: The Noscript element exists on all pages to replace navigation if menu script is disabled.

And if you use multimedia (Priority 1)

1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.

WHV compliance: No audio content exists on site.

1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.

WHV compliance: No multimedia content exists on site.

And if all else fails (Priority 1)

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.

WHV compliance: Not applicable.

Go to Site policies introductory page.