W3C WAI

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 June 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

Checkpoint ID WCAG 2.0 Working Draft
(24 June 2003) WCAG 1.0 text-equiv Checkpoint: 1.1 [CORE] All non-text content that can be expressed in words has a text equivalent of the function or information that the non-text content was intended to convey. [was 1.1] media-equiv Checkpoint: 1.2 [CORE] Synchronized media equivalents are provided for time-dependent presentations. [was 1.2] content-structure-separation Checkpoint: 1.3 [CORE] Both [information/substance] and structure are separable from presentation. [was 1.3] unambiguous-decoding Checkpoint: 1.4 [CORE] All characters and words in the content can be unambiguously decoded. [was 1.6] N/A structure-emphasis Checkpoint: 1.5 [EXTENDED] Structure has been made perceivable to more people through presentation(s), positioning, and labels. [was 1.4] visual-audio-contrast Checkpoint: 1.6 [EXTENDED] Foreground content is easily differentiable from background for both auditory and visual default presentations. [was 1.5] keyboard-operation Checkpoint: 2.1 [CORE] All functionality is operable at a minimum through a keyboard or a keyboard interface. [was 2.1] time-limits Checkpoint: 2.2 [CORE] Users can control any time limits on their reading, interaction, or responses unless control is not possible due to nature of real time events or competition. [was 2.2] flicker Checkpoint: 2.3 [CORE] User can avoid experiencing screen flicker. [was 2.3] navigation-mechanisms Checkpoint: 2.4 [EXTENDED] Structure and/or alternate navigation mechanisms have been added to facilitate orientation and movement in content. [was 3.1 and 3.2] minimize-error Checkpoint: 2.5 [EXTENDED] Methods are provided to minimize error and provide graceful recovery. [was 3.5] language Checkpoint: 3.1 [CORE] Language of content can be programmatically determined.[was 1.6 partial] acronym-abbr-def Checkpoint: 3.2 [EXTENDED] The definition of abbreviations and acronyms can be unambiguously determined. [was 4.3] content-complexity Checkpoint: 3.3 [EXTENDED] Content is written to be no more complex than is necessary and/or supplement with simpler forms of the content. [was 4.1 and 4.2] consistent-behavior Checkpoint: 3.4 [EXTENDED] Layout and behavior of content is consistent or predictable, but not identical. [was 3.3 and 3.4] use-spec Checkpoint: 4.1 [CORE] Technologies are used according to specification [was 5.1] declare-technology Checkpoint: 4.2 [EXTENDED] Technologies that are relied upon by the content are declared and widely available.[was 5.2] technology-supports-access Checkpoint: 4.3 [EXTENDED] Technologies used for presentation and user interface support accessibility or alternate versions of the content are provided that do support accessibility.[was 5.3 and 5.4] N/A HTML Techniques N/A Core Techniques N/A Server-side Techniques

Issues


$Date: 2003/06/20 17:59:29 $ Ben Caldwell