Checkpoint mapping between WCAG 1.0 and WCAG 2.0

This mapping shows where the WCAG 1.0 checkpoints appear in the WCAG 2.0 28 September 2000 working draft.


WCAG 2.0	WCAG 1.0
1.1 Ensure, by providing text equivalents to auditory and graphical presentations as necessary, that every component of a document, web page or multimedia presentation can be rendered as text in a standard character set.	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. [Priority 1] 1.2 Provide redundant text links for each active region of a server-side image map. [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. [Priority 1] 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. [Priority 3]
1.2 For any time-based multimedia presentation (e.g., a movie or animation), synchronize the text equivalents (e.g., captions of the audio track or descriptions of the video track) with the 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. [Priority 1]
2.1 Use markup languages properly and in accordance with specification.	3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2] 3.2 Create documents that validate to published formal grammars. [Priority 2] 11.2 Avoid deprecated features of W3C technologies. [Priority 2]
2.2 Use style languages, where available, to control layout and presentation. Where practicable, provide (or link to) multiple style sheets, each supporting a different output device.	3.3 Use style sheets to control layout and presentation. [Priority 2] 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2]
2.3 Where presentation is used to communicate distinctions of meaning or structure within the content, also define these distinctions in the markup or data model so that a user agent can create alternative presentations.	doesn't seem to be a WCAG 1.0 equivalent.
2.4 Use presentation (e.g. color or font changes) to enhance semantic distinctions but not as the only means to understand them.	2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1]
2.5 Use markup or a data model to provide logical structure to the content, together with any additional semantic distinctions that facilitate rendering of the content visually, auditorily, or tactually.	13.2 Provide metadata to add semantic information to pages and sites. [Priority 2] 5.1 For data tables, identify row and column headers. [Priority 1] 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. [Priority 1] 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] 3.6 Mark up lists and list items properly. [Priority 2] 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]
3.1 Use a consistent style of presentation that will facilitate comprehension of the content.	14.3 Create a style of presentation that is consistent across pages. [Priority 3]
3.2 Use color, styles, and graphics to emphasize the structure of the document.	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].
3.3 Divide large blocks of information into more manageable groups where natural and appropriate.	12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
3.4 Label blocks of information to help users identify structurally significant divisions within the content.	12.1 Title each frame to facilitate frame identification and navigation. [Priority 1] 12.4 Associate labels explicitly with their controls. [Priority 2]
3.5 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.	13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. [Priority 3]
3.6 Use the clearest and simplest language appropriate for a site's content.	14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1]
3.7 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the content.	14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3]
3.8 Provide an overview or summary of highly structured materials, such as tables and groups of user interface controls.	5.5 Provide summaries for tables. [Priority 3] 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2] 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]
3.9 Define key terms and provide expansions for abbreviations and acronyms, which should be identified using appropriate markup.	5.6 Provide abbreviations for header labels. [Priority 3] 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3]
3.10 Minimize content that will interfere with the user’s ability to focus.	7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1] 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). [Priority 2] 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2] 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2] 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. [Priority 2] 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. [Priority 2]
4.1 Provide clear and consistent navigation mechanisms throughout a document, application or site.	13.1 Clearly identify the target of each link. [Priority 2] 13.4 Use navigation mechanisms in a consistent manner. [Priority 2] 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3] 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3] 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). [Priority 3] 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3] 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3]
4.2 If search functions are provided by a web site, enable different types of searches for different skill levels and preferences.	13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. [Priority 3]
4.3 Avoid methods that interfere with navigation.	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). [Priority 2] 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]?? 13.10 Provide a means to skip over multi-line ASCII art. [Priority 3] (??it's a stretch and is based on changing this to "Provide methods to help w/navigation")
5.1 Associate an explicit label with each user interface control.	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. [Priority 2] 12.4 Associate labels explicitly with their controls. [Priority 2]
5.2 Logically group user interface controls.	12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
5.3 Use device-independent event handlers .	6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2] 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]
5.4 Design assistive-technology compatible user interfaces.	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. [Priority 2]
6.1 Make sure that web sites which take advantage of newer technologies continue to be usable when such technologies are turned off or not supported.	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. [Priority 1] 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [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. [Priority 1]
6.2 Avoid causing content to blink or flicker otherwise than under the control of the user.	7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1] 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). [Priority 2]
6.3 Avoid causing pages to be refreshed or updated automatically, otherwise than in response to a user's request.	7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2] 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2] 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. [Priority 2]
6.4 Where it is likely that some user agents will not support the data format or encoding in which the content is supplied, provide metadata, a transformation filter, a style sheet or other mechanism to enable the content to be processed by the user agent.	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. [Priority 1] 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2] 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. [Priority 3] 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3] (could create a transformation that inserts place-holding characters into the forms)

WCAG 1.0 checkpoints without a clear home

I did not assign the following WCAG 1.0 checkpoints to any WCAG 2.0 checkpoints because it was not clear where they fit.

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. [Priority 1]
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]
4.3 Identify the primary natural language of a document. [Priority 3]
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3]
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

I did assign the following WCAG 1.0 checkpoints to WCAG 2.0 checkpoints but it is not clear that these actually fit. Some could fit with slight changes in wording to a WCAG 2.0 checkpoint:

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]??
13.10 Provide a means to skip over multi-line ASCII art. [Priority 3] (??it's a stretch and is based on changing this to "Provide methods to help w/navigation")

Issues

At the face to face we agreed that for the first public draft checkpoints would inherit their priority from WCAG 1.0 checkpoints. In many cases, several WCAG 1.0 checkpoints of varying priority levels map to a single WCAG 2.0 checkpoint. How should we resolve the difference? Could this imply that we only prioritize at the technology-specific level?
There are several WCAG 1.0 checkpoints whose priority is under debate. Some of these became more obvious to me today. For example, Len has maintained for quite a while that WCAG 1.0 checkpoint 5.3 (do not use tables for layout unless makes sense when linearized) is not a P2 but a P1. When and how will we sort these out?
I realized at least one redundancy in WCAG 1.0 checkpoints that I had not noticed before. In one example, the new WCAG 2.0 checkpoint combines the redundant checkpoints. For example WCAG 2.0 checkpoint 5.3 says "Use device-independent event handlers." We said this twice in WCAG 1.0 with checkpoints 6.4 and 9.3.
There seem to be some redundancies in WCAG 2.0. In this list "old" refers to WCAG 1.0 checkpoints and "new" refers to WCAG 2.0 checkpoints.
- The old 7.1 and 7.2 appear in both the new 6.2 and 3.10.
- The old 7.4 and 7.5 appear in both the new 6.3 and 3.10.
- The old 12.3 appears in the new 3.3 and 5.2.
- The old 12.4 appears in the new 3.4 and 5.1.
- The old 7.3 appears in the new 3.10 and 6.3.
What should we do about this? I think we might be able to combine some of the WCAG 2.0 checkpoints, but some careful wording will be needed. For example, "avoid blinking and flickering" could be subsumed under "avoid things that distract the user" however this could stand on its own right because of the epilepsy issue. I like the wording "don't distract the user" yet that puts the rationale in the checkpoint. Is it clear that strictly separating rationale and and requirement is a bad thing?

$Date: 2000/11/08 08:27:11 $ Wendy Chisholm