State of Connecticut Web Site Accessibility Committee ConneCT - Your Key to Accessibility

Home | Policy | About | Status Reports | Meetings | Membership | Listserv | Resources | Tools | Tutorials | Forms | News | Search | Site Map

Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0
Priority 1 Checkpoints

Purpose of this page

This document is a supplement to the Proposed Changes to the State of Connecticut Web Site Accessibility Policy. It was created so that interested readers could easily find and review a list of W3C WCAG Priority 1 checkpoints. The content on this page was copied from the Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 , which is copyrighted material.

This page is not intended to be a permanent link or resource on this site. It will only reside here during the review process.

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.
2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.
4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
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.
6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.
7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.
14.1 Use the clearest and simplest language appropriate for a site's 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.
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.
And if you use tables (Priority 1)
5.1 For data tables, identify row and column headers.
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.
And if you use frames (Priority 1)
12.1 Title each frame to facilitate frame identification and navigation.
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.
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.
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.
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.


This page was updated on: Thursday May 05, 2005

HTML 4.01 - Follow this link to view the page validation results|Valid CSS - Follow this link to view the page validation results