W3CWAI

Checkpoint Mapping Between WCAG 1.0 and the WCAG 2.0 Working Draft

This mapping shows where the WCAG 1.0 checkpoints appear in the 24 April 2003 Working Draft. The WCAG 2.0 Working Draft is prepared by the Web Content Accessibility Guidelines Working Group (WCAG WG) to show how more generalized (less HTML-specific) WCAG checkpoints might read. The Working Draft is not based on consensus of the WCAG Working Group nor has it gone through W3C process. Checkpoints in the WCAG 2.0 Working Draft in no way supersede the checkpoints in WCAG 1.0.

The Web Content Accessibility Guidelines Working Group is working carefully to enable organizations and individuals that are currently using WCAG 1.0 (which remains stable and referenceable at this time) to ensure that they will eventually be able to make a smooth transition to WCAG 2.0.

change column layoutChange column layout

WCAG 2.0 Working Draft
(24 April 2003) WCAG 1.0 Checkpoint 1.1 For all non-text content that can be expressed in words, provide a text equivalent of the function or information the non-text content was intended to convey. Checkpoint 1.2 Provide synchronized media equivalents for time-dependent presentations. Checkpoint 1.3 Make all content and structure available independently of presentation. Checkpoint 1.4 Emphasize structure through presentation(s), positioning, and labels. Checkpoint 1.5 Ensure that foreground content is easily differentiable from background for both auditory and visual presentations. Checkpoint 1.6 Provide information needed for unambiguous decoding of the characters and words in the content. Checkpoint 2.1 Ensure that all of the functionality is operable at a minimum through a keyboard or keyboard interface. Checkpoint 2.2 Allow users to control any time limits on their reading, interaction or responses unless control is not possible due to the nature of real-time events or competition. Checkpoint 2.3 Avoid causing the screen to flicker. Checkpoint 3.1 Provide structure within content. Checkpoint 3.2 Provide multiple methods to explore sites that are more than two layers deep. Checkpoint 3.3 Use consistent but not necessarily identical presentation. Checkpoint 3.4 Provide consistent and predictable responses to user actions. Checkpoint 3.5 Provide methods to minimize error and provide graceful recovery. Checkpoint 4.1 Write clearly. Checkpoint 4.2 Supplement text with non-text content. Checkpoint 4.3 Annotate complex, abbreviated, or unfamiliar information with summaries and definitions. Checkpoint 5.1 Use technologies according to specification. Checkpoint 5.2 Ensure that technologies relied upon by the content are declared and widely available. Checkpoint 5.3 Choose technologies that are designed to support accessibility. Checkpoint 5.4 Ensure that user interfaces are accessible or provide an accessible alternative. HTML Techniques Core Techniques Server-side Techniques

Issues


$Date: 2003/04/28 17:22:26 $ Ben Caldwell