Mapping Between WCAG 1.0 and the WCAG 2.0 Working Draft

This mapping shows where the WCAG 1.0 checkpoints appear in the 11 March 2004 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. Guidelines and success criteria 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

Guideline ID WCAG 2.0 Working Draft
(11 March 2004) WCAG 1.0 text-equiv Guideline 1.1 For non-text content, provide text equivalents that serve the same purpose or convey the same information as the non-text content, except when the sole purpose of the non-text content is to create a specific sensory experience (for example, music and visual art) in which case a text label or description is sufficient. media-equiv Guideline 1.2 Provide synchronized media equivalents for time-dependent presentations. content-structure-separation Guideline 1.3 Ensure that information, functionality, and structure are separable from presentation. visual-contrast Guideline 1.4 In visual presentations, make it easy to distinguish foreground words and images from the background. audio-contrast Guideline 1.5 In auditory presentations, make it easy to distinguish foreground speech and sounds from background sounds. N/A keyboard-operation Guideline 2.1 Make all functionality operable via a keyboard or a keyboard interface. time-limits Guideline 2.2 Allow users to control time limits on their reading or interaction unless specific real-time events or rules of competition make such control impossible. flicker Guideline 2.3 Allow users to avoid content that could cause photosensitive epileptic seizures. navigation-mechanisms Guideline 2.4 Facilitate the ability of users to orient themselves and move within the content. minimize-error Guideline 2.5 Help users avoid mistakes and make it easy to correct them. meaning Guideline 3.1 Ensure that the meaning of content can be determined. consistent-behavior Guideline 3.2 Organize content consistently from "page to page" and make interactive components behave in predictable ways. use-spec Guideline 4.1 Use technologies according to specification. technology-supports-access Guideline 4.2 Ensure that user interfaces are accessible or provide an accessible alternative(s) N/A User Agent Issues - to be included in techniques N/A Checkpoints that could potentially be deprecated N/A No Match - not clear that this is needed.

$Date: 2004/03/12 16:00:14 $ Ben Caldwell