This mapping shows where the WCAG 1.0 checkpoints appear in the 23 November 2005 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.
Editorial Note: There are several issues and action items outstanding on this
mapping. It has not yet been updated to reflect recent changes to success criterion, numbering, updates to definitions, or changes in levels that have been incorporated in the 23 November 2005 working draft.
In General (Priority 1) | WCAG 2.0 Success Criteria |
---|---|
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. |
For scripts, applets and objects, alternative versions are covered under GL 4.2, and labels under GL 1.1. Images used as bullets are also covered in GL 1.3 with regard to CSS usage. For framesets, noframes is no longer required.For video, alternatives (beyond labels) are covered under GL 1.2. ASCII art is non-text content |
2.1: Ensure that all information conveyed with color is also available without color, for example from context or markup. |
When information is conveyed by color, the color can be programmatically determined or the information is also conveyed through another means that does not depend on the user's ability to differentiate colors. |
4.1: Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). |
The natural language of each foreign passage or phrase in the content can be programmatically determined. Note: identification of the language for individual words is no longer required. |
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. | Text alternatives are addressed in
[add bug: need to figure out if alternatives changing when content changes needs to be made explicit (in WCAG 2.0)] |
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) | WCAG 2.0 Success Critera |
1.2: Provide redundant text links for each active region of a server-side image map. |
With regard to text alternatives:
If content does not meet all level 1 success criteria, then an alternate Note: server-side image maps are not keyboard accessible. |
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. |
With regard to text alternatives:
All of the functionality of the content If content does not meet all level 1 success criteria, then an alternate Note: server-side image maps are not keyboard accessible. |
And if you use tables (Priority 1) | WCAG 2.0 Success Criteria |
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) | WCAG 2.0 Success Criteria |
12.1: Title each frame to facilitate frame identification and navigation. |
Navigational features within the content can be programmatically |
And if you use applets and scripts (Priority 1) | WCAG 2.0 Success Criteria |
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. |
For any technologies (scripts, applets, or other programmatic objects) not in the specified baseline, the following are true:
If content does not meet all level 1 success criteria, then an alternate Note: action item for new wording. |
And if you use multimedia (Priority 1) | WCAG 2.0 Success Criteria |
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. |
Audio descriptions of video are provided for prerecorded multimedia |
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. |
Captions are provided for prerecorded multimedia. Audio descriptions of video are provided for prerecorded multimedia |
And if all else fails (Priority 1) | WCAG 2.0 Success Criteria |
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. |
|
In General (Priority 2) | WCAG 2.0 Success Criteria |
---|---|
2.2: Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. |
Text that is presented over a background pattern of lines which are within 500% +/- of the stem width of the characters or their serifs must have a contrast between the characters and the lines that is greater than X2, where the whiter element is at least Y2. |
3.1: When an appropriate markup language exists, use markup rather than images to convey information. | GL 1.3 Advisory Note: There is no optional technique for this in Understanding WCAG 2.0. May map to GL 4.1 (Use technologies according to specification), pending reformulation. |
3.2: Create documents that validate to published formal grammars. | Note: Validating to published formal grammars is a stronger requirement than unambiguous parsing and is an optional technique for this success criterion. |
3.3: Use style sheets to control layout and presentation. |
When content is arranged in a sequence that affects its meaning, that sequence can be programmatically determined May map to GL 4.1 (Use technologies according to specification), pending reformulation. |
3.4: Use relative rather than absolute units in markup language attribute values and style sheet property values. | Note: action item to explore whether there should or shouldn't be a SC about scaling of fonts and other presentational elements. [Nothing about relative or absolute units in Understanding WCAG 2.0.] |
3.5 Use header elements to convey document structure and use them according to specification. |
GL 4.1 |
3.6: Mark up lists and list items properly. |
GL 4.1 |
3.7: Mark up quotations. Do not use quotation markup for formatting effects such as indentation. |
potentially GL 4.1 |
6.5: Ensure that dynamic content is accessible or provide an alternative presentation or page. |
If content does not meet all level 1 success criteria, then an alternate |
7.2: Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). |
Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit. |
7.4: Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. |
Changes of context are initiated only by user |
7.5: Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. |
Changes of context are initiated only by user |
10.1: Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. |
2. When any component receives focus, it does not cause a change of context. 3. Changing the setting of any input field does not automatically cause a change of context. SC 3.2.2 (level 2): Changing the setting of any input field does not automatically cause a change of context . Changes of context are initiated only by user |
11.1: Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. |
No longer required for conformance to WCAG 2.0. Note: advice to authors about choosing appropriate technologies as related to baseline. |
11.2: Avoid deprecated features of W3C technologies. | |
12.3: Divide large blocks of information into more manageable groups where natural and appropriate. |
No longer required for conformance to WCAG 2.0. This checkpoint can map to advisory information for GL 3.1 in |
13.1: Clearly identify the target of each link. |
|
13.2: Provide metadata to add semantic information to pages and sites. | This is no longer required for conformance, but could be a technique for satisfying certain success criteria in Guidelines 2.4, 4.2, or 1.3. |
13.3: Provide information about the general layout of a site (e.g., a site map or table of contents). |
More than one way is available to locate content within a set of delivery units where content is not the result of, or a step in, a process or task. Information about the user's location within a set of delivery units is available. Might also map to an advisory item. Note: this is a partial mapping. |
13.4 Use navigation mechanisms in a consistent manner. |
3. Components that are repeated on multiple delivery units within a set of delivery units occur in the same relative order each time they are repeated. 4. Components that have the same functionality in multiple delivery units within a set of delivery units are |
And if you use tables (Priority 2) | WCAG 2.0 Success Criteria |
5.3: Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). |
When content is arranged in a sequence that affects its meaning, that sequence can be |
5.4: If a table is used for layout, do not use any structural markup for the purpose of visual formatting. | |
And if you use frames (Priority 2) | WCAG 2.0 Succes Criteria |
12.2: Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. |
This is no longer required for conformance (because the longdesc attribute type on the frame element type
has not been supported and is likely to disappear from the XHTML specification).
|
And if you use forms (Priority 2) | WCAG 2.0 Success Criteria |
10.2: Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. | Advisory item in Note: this mapping may change if a Success Criterion related to the positioning of labels is created (see action item 1 September 2005). |
12.4: Associate labels explicitly with their controls. |
The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control. |
And if you use applets and scripts (Priority 2) | WCAG 2.0 Success Criteria |
6.4: For scripts and applets, ensure that event handlers are input device-independent. |
All of the functionality of the content Note: device independent event handlers are not explicitly required. |
7.3: Until user agents allow users to freeze moving content, avoid movement in pages. |
Note: The "until user agents" clause has been satisfied, so it is no longer necessary to avoid movement altogether, as long as authors don't do anything to interfere with the user's ability to pause the content. |
8.1: Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] |
|
9.2: Ensure that any element that has its own interface can be operated in a device-independent manner. |
All of the functionality of the content |
9.3: For scripts, specify logical event handlers rather than device-dependent event handlers. |
All of the functionality of the content |
In General (Priority 3) | WCAG 2.0 Success Criteria |
---|---|
4.2: Specify the expansion of each abbreviation or acronym in a document where it first occurs. |
A mechanism for finding the expanded form of |
4.3: Identify the primary natural language of a document. |
The primary natural language or languages of the delivery unit can be programmatically determined. |
9.4: Create a logical tab order through links, form controls, and objects. |
When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content. |
9.5: Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. |
Advisory item in Note: accesskeys are no longer required for conformance to WCAG 2.0. |
10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. |
Advisory item in Guide Document. Note: this technique is no longer needed for user agents but may be useful for people with cognitive disabilities. |
11.3: Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) |
This checkpoint does not map to any WCAG 2.0 success criterion, though certain aspects may map to certain success criteria or to advisory items in a |
13.5: Provide navigation bars to highlight and give access to the navigation mechanism. |
This checkpoint is not required by any success criterion in WCAG 2.0.
It is a possible strategy to address |
13.6: Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. |
Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed. Note: In WCAG 2.0 it only relates to groups that are repeated on multiple delivery units. |
13.7: If search functions are provided, enable different types of searches for different skill levels and preferences. |
Note: This checkpoint does not directly map to any WCAG 2.0 Success Criterion and is not required.
Some aspects relate to |
13.8: Place distinguishing information at the beginning of headings, paragraphs, lists, etc. |
This checkpoint is not required by any Success Criterion in WCAG 2.0.
It may be useful to map it to advisory items in |
13.9: Provide information about document collections (i.e., documents comprising multiple pages.) |
This checkpoint is not in WCAG 2.0 but does relate to |
13.10: Provide a means to skip over multi-line ASCII art. |
This technique is not required by any Success Criterion in WCAG 2.0.
ASCII art is considered non-text content and would map to an advisory item in |
14.2: Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. |
This checkpoint is not required by any WCAG 2.0 Success Criterion.
It is a strategy that can be used to address WCAG 2.0 |
14.3: Create a style of presentation that is consistent across pages. |
Aspects of WCAG 1.0 Checkpoint 14.3 are required by WCAG 2.0 Guideline
|
And if you use images and image maps (Priority 3) | WCAG 2.0 Success Criteria |
1.5: Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. |
WCAG 1.0 Checkpoint 1.5 is not required by any Success Criterion in WCAG 2.0.
It might appear as a repair technique in conjunction with an advisory item in Note: this is no longer required because of advances in user agents. |
And if you use tables (Priority 3) | WCAG 2.0 Success Criteria |
5.5: Provide summaries for tables. | This is no longer required for conformance. |
5.6: Provide abbreviations for header labels. | This is no longer required for conformance, but a potentially useful technique. |
10.3: Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. | WCAG 1.0 Checkpoint 10.3 is no longer required for conformance to WCAG 2.0. |
And if you use forms (Priority 3) | WCAG 2.0 Success Criteria |
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. | Deprecate. [Was "deprecated" understood in the way defined in the 4 August teleconference? If not, it should be "not required".] |