Mapping of WCAG 1.0 checkpoints to WCAG 2.0 success criteria

This mapping shows where the WCAG 1.0 checkpoints appear in the 30 June 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. The working group seeks comments on this format as a way to educate people on migrating from WCAG 1.0 to WCAG 2.0.

Definitions

deprecated (technique or checkpoint)
(technique or checkpoint that is) considered harmful in WCAG 2.0 (“things we don't want people to do anymore”; 4 August 2005 teleconference)
not required (technique or checkpoint)
(technique or checkpoint that is) not required for conformance to WCAG 2.0 but that may appear in advisory information (for example in the Guide Document or as an optional technique in a Techniques Document) (“things that WCAG 2.0 does not require for conformance, but may still appear in advisory”; 4 August 2005 teleconference)
mapping document
document that should indicate when a WCAG 1.0 Checkpoint is required by WCAG 2.0 and if a WCAG 1.0 Checkpoint is sufficient to satisfy a WCAG 2.0 Success Criterion. It should note if an item appears in advisory information if it is not required. (11 August 2005 teleconference) Checkpoints must be mapped to an entity [success criterion?] or to an advisory item in the Guide Document. (11 August 2005 teleconference)

Priority 1 checkpoints

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. GL 1.1 Level 1 SC:
  1. For all non-text content that is used to convey information, text alternatives identify the non-text content and convey the same information. For multimedia, provide a text-alternative that identifies the multimedia.
  2. For functional non-text content, text alternatives serve the same purpose as the non-text content. If text alternatives can not serve the same purpose as the functional non-text content, text alternatives identify the purpose of the functional non-text content.
  3. For non-text content that is intended to create a specific sensory experience, text alternatives at least identify the non-text content with a descriptive label.
  4. Non-text content that is not functional, is not used to convey information, and does not create a specific sensory experience is implemented such that it can be ignored by assistive technology.
  5. For live audio-only or live video-only content, text alternatives at least identify the purpose of the content with a descriptive label.
For scripts, applets, plug-ins, frames, this is baseline dependent.
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.
What about ASCII art?ASCII art is non-text content Note 1
2.1: Ensure that all information conveyed with color is also available without color, for example from context or markup. GL 1.3 Level 1 SC 2
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). GL 3.1 Level 2 SC 1
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. GL 2.4 Level 3 SC 1
When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content.

 For any technologies (style sheets) not in the specified baseline, the following are true:
  • The Web content still conforms using user agents that only support the technologies that are in the baseline (i.e. the use of technologies that are not in the baseline does not "break" access to the Web content by user agents that don't support those technologies.)
  • All content and functionality are available using only the technologies in the specified baseline.
 This is baseline-dependent:
  • if style sheets are in your baseline, WCAG 1.0 checkpoint 6.1 is not required;
  • if stylesheet are not in your baseline, then WCAG 1.0 checkpoint 6.1 is required at Level 1 (as it maps to Guideline 1.3 L1)
6.2: Ensure that equivalents for dynamic content are updated when the dynamic content changes. Text alternatives are addressed in GL 1.1, 1.2, and 4.2. If providing a text equivalent for content and that content changes, then the text alternative must also be changed or else you don't conform to GL 1.1, 1.2, and 4.2 anymore.
[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. GL 2.3 Level 1 SC 1: Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance
 GL 2.3 Level 2 SC 1:
Content does not violate Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash.
14.1: Use the clearest and simplest language appropriate for a site's content. GL 3.1 Level 3 contains some SC that aid in making content understandable. There is no direct mapping.
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: GL 1.1 Level 1 SC1-3:
  1. For all non-text content that is used to convey information, text alternatives identify the non-text content and convey the same information. For multimedia, provide a text-alternative that identifies the multimedia.
  2. For functional non-text content, text alternatives serve the same purpose as the non-text content. If text alternatives can not serve the same purpose as the functional non-text content, text alternatives identify the purpose of the functional non-text content.
  3. For non-text content that is intended to create a specific sensory experience, text alternatives at least identify the non-text content with a descriptive label.
 With regard to keyboard access: GL 2.1 Level 1 SC 1, GL 2.4 Level 2 SC 4, GL 4.2 Level 1 SC 1.
 GL 2.1 Level 1 SC 1:
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface.
GL 2.4 Level 2 SC4:
The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined.
GL 4.2 Level 1 SC 1:
If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria. 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. Bugzilla issue 1484
With regard to text alternatives: GL 1.1 Level 1 SC1-3:
  1. For all non-text content that is used to convey information, text alternatives identify the non-text content and convey the same information. For multimedia, provide a text-alternative that identifies the multimedia.
  2. For functional non-text content, text alternatives serve the same purpose as the non-text content. If text alternatives can not serve the same purpose as the functional non-text content, text alternatives identify the purpose of the functional non-text content.
  3. For non-text content that is intended to create a specific sensory experience, text alternatives at least identify the non-text content with a descriptive label.
 With regard to keyboard access: GL 2.1 Level 1 SC 1, GL 2.4 Level 2 SC 4, GL 4.2 Level 1 SC 1.
 GL 2.1 Level 1 SC 1:
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface.
GL 2.4 Level 2 SC4:
The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined.
GL 4.2 Level 1 SC 1:
If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria. 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. GL 1.3 Level 1 SC 1:
Structures within the content can be programmatically determined.
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. GL 1.3 Level 1 SC 1:
Structures within the content can be programmatically determined.
And if you use frames (Priority 1) WCAG 2.0 Success Criteria
12.1: Title each frame to facilitate frame identification and navigation. GL 2.4 Level 1 SC 1:
Navigational features can be programmatically identified. GL 2.4 Level 2 SC 4:
3. Delivery units have descriptive titles
The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined.

Note 2 Mapping pending on action item
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:
  • The Web content still conforms using user agents that only support the technologies that are in the baseline (i.e. the use of technologies that are not in the baseline does not "break" access to the Web content by user agents that don't support those technologies.)
  • All content and functionality are available using only the technologies in the specified baseline.
GL 4.2 Level 1 SC1:
If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.
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. GL 1.2 Level 1 SC 2:
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. GL 1.2 Level 1 SC 1:
Captions are provided for prerecorded multimedia.
GL 1.2 Level 1 SC 2:
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. GL 4.2 Level 1 SC
  1. If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.
  2. Content using baseline technologies or non-baseline technologies, must meet the following criteria:
    1. Content that violates international health and safety standards for general flash or red flash is marked in a way that the user can avoid its appearance.
    2. If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.

Priority 2 checkpoints

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]. GL 1.4 Level 2 SC 1:
Text and diagrams that are presented over a background image, color, or text have a contrast greater than X1 where the whiter element is at least Y1 as measured by _____.
GL 1.4 Level 2 SC2:
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.
GL 1.4 Level 3 SC 1:
Text is not presented over any background (image, text, color or pattern), or if any background is present, the contrast between the text and the background is greater than X2.
3.1: When an appropriate markup language exists, use markup rather than images to convey information. GL 1.3 Advisory
May map to GL 4.1 (Use technologies according to specification), pending reformulation.
3.2: Create documents that validate to published formal grammars. GL 4.1
3.3: Use style sheets to control layout and presentation. 1.3 Advisory, also in HTML and CSS Techniques
GL 1.3 Level 3 SC1:
When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.
May map to GL 4.1 (Use technologies according to specification), pending reformulation.
May map to advisory items for GL 1.3 in the Guide Document.
3.4: Use relative rather than absolute units in markup language attribute values and style sheet property values. None. User agent issue Note: action item to explore whether there should or shouldn't be a SC about scaling of fonts and other presentational elements.
3.5 Use header elements to convey document structure and use them according to specification. GL 1.3 Level 1 SC1:
Structures within the content can be programmatically determined.

GL 4.1
3.6: Mark up lists and list items properly. GL 1.3 Level 1 SC 1:
Structures within the content can be programmatically determined.

GL 4.1
3.7: Mark up quotations. Do not use quotation markup for formatting effects such as indentation. GL 1.3 Level 1 SC1 :
Structures within the content can be programmatically determined.

potentiallyGL 4.1
6.5: Ensure that dynamic content is accessible or provide an alternative presentation or page. Anything allowed by the baseline must meet all the applicable success criteria.

For any technologies not in the specified baseline, the following are true:
  • The Web content still conforms using user agents that only support the technologies that are in the baseline (i.e. the use of technologies that are not in the baseline does not "break" access to the Web content by user agents that don't support those technologies.)
  • All content and functionality are available using only the technologies in the specified baseline.
 GL 4.2 Level 1 SC 1:
If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria. [V]
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). GL 2.2 Level 2 SC1:
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. GL 2.2 Level 1 SC 1:
Content is designed so that time-outs are not an essential part of interaction, or at least one of the following is true for each time-out that is a function of the content:
  • the user is allowed to deactivate the time-out or;
  • the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;
  • the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond or;
  • the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible or;
  • the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.
GL 3.2 Level 3 SC 2:
Changes of context are initiated only by user action.
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. GL 2.2 Level 1 SC 1:
Content is designed so that time-outs are not an essential part of interaction, or at least one of the following is true for each time-out that is a function of the content:
  • the user is allowed to deactivate the time-out or;
  • the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;
  • the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond or;
  • the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible or;
  • the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.
 GL 3.2 Level 3 SC2:
Changes of context are initiated only by user action.
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. GL 3.2 Level 2 SC:
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.

GL 3.2 Level 3 SC 2:
Changes of context are initiated only by user action.
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. Relates to GL 4.1 but should not map to a level 1 criterion.
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 the Guide Document (good practice that is encouraged as appropriate).
13.1: Clearly identify the target of each link. GL 2.4 Level 2 SC 4:
The destination of each programmatic reference to another delivery unit is identified through words or phrases that either occur in text or can be programmatically determined.
13.2: Provide metadata to add semantic information to pages and sites. Technique that can be used to achieve some guidelines but not required for conformance. 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). GL 2.4 Level 2 SC 1:
More than one way is available to locate content within a set of delivery units.
GL 2.4 Level 3 SC 2:
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. GL 3.2 Level 2 SC:
1. Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated.
4. Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.
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). GL 1.3 Level 3 SC 1:
When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.
5.4: If a table is used for layout, do not use any structural markup for the purpose of visual formatting. GL 4.1
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. GL 1.3 Level 1 SC 1:
Structures within the content can be programmatically determined.
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).
Note 4
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. Mapping pending action item regarding implicit labels and positioning of labels.
12.4: Associate labels explicitly with their controls. GL 4.2 Level 1 SC 4:
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. GL 2.1 Level 1 SC 1:
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface.
Note: device independent event handlers are not explicitly required.
7.3: Until user agents allow users to freeze moving content, avoid movement in pages. GL 2.2 Level 3 SC 1:
Except for real-time events, timing is not an essential part of the event or activity presented by the content. GL 2.2 Level 2 SC 2:
Moving or time-based content can be paused by the user. Note: The "until user agents" clause has been satisfied, so it is no long 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.] Anything allowed by the baseline must meet all the applicable success criteria.

For any technologies not in the specified baseline, the following are true:
  • The Web content still conforms using user agents that only support the technologies that are in the baseline (i.e. the use of technologies that are not in the baseline does not "break" access to the Web content by user agents that don't support those technologies.)
  • All content and functionality are available using only the technologies in the specified baseline.
 GL 4.2 Level 1:
  1. If content does not meet all level 1 success criteria, then an alternate form is provided that does meet all level 1 success criteria.
  2. Content using baseline technologies or non-baseline technologies, must meet the following criteria:
    1. Content that violates international health and safety standards for general flash or red flash is marked in a way that the user can avoid its appearance.
    2. If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.
  3. The role, state, and value can be programmatically determined for every user interface component of the web content that accepts input from the user or changes dynamically in response to user input or external events.
  4. The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control.
  5. The states and values of content that can be changed via the user interface can also be changed programmatically.
  6. Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.
9.2: Ensure that any element that has its own interface can be operated in a device-independent manner. GL 2.1 Level 1 SC 1:
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface.
9.3: For scripts, specify logical event handlers rather than device-dependent event handlers. GL 2.1 Level 1 SC 1:
All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard interface.

Priority 3 checkpoints

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. GL 3.1 Level 3 SC 3:
A mechanism for finding the expanded form of acronyms and abbreviations is available.
4.3: Identify the primary natural language of a document. GL 3.1 Level 1 SC 1:
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. GL 2.4 Level 3 SC 1:
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. GL 2.1 No SC?
GL 2.4 No SC?
 Advisory item in the Guide Document.
 Note: accesskeys are no longer required for conformance to WCAG 2.0.
Note 6
10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. Deprecate 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.) Conformance scheme allows for this but it is not a requirement for conformance. 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 the Guide Document.
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 GL 2.4 Level 2 SC 1.
 Note 7
13.6: Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. GL 2.4 Level 2 SC 2:
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. GL 2.5 Level 3 SC
1. Additional context-relevant assistance is available for text input.
 Note: This checkpoint does not directly map to any WCAG 2.0 Success Criterion and is not required. Some aspects relate to 2.4 L2 SC 1 and 2.5 L3 SC 2 as well as advisory items in the Guide Document.
Note 8
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 the Guide Document.
 Note 9
13.9: Provide information about document collections (i.e., documents comprising multiple pages.) GL 2.4 Level 3 SC
2. Information about the user's location within a set of delivery units is available. This checkpoint is not in WCAG 2.0 but does relate to GL 2.4 Level 3 SC 2 and would appear in advisory items in the Guide Document.
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 the Guide Document.
 Note 10
14.2: Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. GL 3.1 Level 3 SC
5. When text requires reading ability at or above the upper secondary education level, one or more of the following supplements is available:
  • A text summary that requires reading ability no higher than primary education level.
  • Graphical illustrations of concepts or processes that must be understood in order to use the content.
  • A spoken version of the text content.
 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 GL 3.1 Level 3 SC 5.
14.3: Create a style of presentation that is consistent across pages. GL 3.2 Level 2 SC
1. Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated.
4. Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently.
GL 3.2 Level 3 SC
1. Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear.
Aspects of WCAG 1.0 Checkpoint 14.3 are required by WCAG 2.0 Guideline 3.2 L2 SC1, 3.2 L2 SC 4, and 3.2 L3 SC 1. There is no Success Criterion in WCAG 2.0 that is as broad as WCAG 1.0 Checkpoint 14.3, so aspects of it do not relate.
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. Deprecate 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 the Guide Document.
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. GL 1.3 advisory? This is no longer required for conformance.
5.6: Provide abbreviations for header labels. GL 2.4 Level 2 SC
Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed.
 This is no longer required for conformance, but a potentially useful technique. Note 11
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. Deprecate 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".]

New Level 1 requirements in WCAG 2.0

Guideline 1.4

  1. 1.4 L1 SC1: Any text that is presented over a background image, color, or text can be programmatically determined.

Guideline 2.3

  1. 2.3 L1 SC1: Content that violates Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash is marked in a way that the user can avoid its appearance.

Guideline 2.4

  1. 2.4 L1 SC1: Navigational features can be programmatically identified.

Guideline 3.2

  1. 3.2 L1 SC1: Any change of context is implemented in a manner that can be programmatically determined.

Guideline 4.2

  1. 4.2 L1 SC3: The role, state, and value can be programmatically determined for every user interface component of the web content that accepts input from the user or changes dynamically in response to user input or external events.
  2. 4.2 L1 SC4: The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control.
  3. 4.2 L1 SC5: The states and values of content that can be changed via the user interface can also be changed programmatically.
  4. 4.2 L1 SC6: Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.

 

New Level 2 requirements in WCAG 2.0

Guideline 1.2

  1. 1.2 L2 SC1: Real-time captions are provided for live multimedia.

Guideline 1.3

  1. 1.3 L2 SC1: Information that is conveyed by variations in presentation of text is also conveyed when variations in presentation of text are not available, or can be programmatically determined.
  2. 1.3 L2 SC2: Any information that is conveyed through color is visually evident without having to interpret color. For example, the distinction can additionally be determined through context, characters, or symbols that accompany the color presentation, or through pattern differences such as dotted red vs. solid green lines in a graph.

Guideline 1.4

  1. 1.4 L2 SC2: 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.
  2. 1.4 L2 SC3: A mechanism is available to turn off background audio that plays automatically.

Guideline 2.2

  1. 2.2 L2 SC2: Moving or time-based content can be paused by the user.

Guideline 2.5

  1. 2.5L2 SC1: If an input error is detected, the error is identified and provided to the user in text.
  2. 2.5L2 SC2: If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the error is identified and the suggestions are provided to the user.
  3. 2.5L2 SC3: For forms that cause legal or financial transactions to occur, that modify or delete data in remote data storage systems, or that submit test responses, at least one of the following is true:
    1. Actions are reversible.
    2. Actions are checked for errors before going on to the next step in the process.
    3. The user is able to review and confirm or correct information before submitting it.

New Level 3 requirements in WCAG 2.0

Guideline 1.1

  1. 1.1 L3 SC1: For prerecorded multimedia content, a combined transcript of captions and audio descriptions of video is available.

Guideline 1.2

  1. 1.2 L3 SC1: Sign language interpretation is provided for multimedia
  2. 1.2 L3 SC2: Extended audio descriptions of video are provided for prerecorded multimedia.
  3. 1.2 L3 SC3: Audio descriptions of video are provided for live multimedia.

Guideline 1.3

  1. 1.3 L3 SC1: When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically.

Guideline 1.4

  1. 1.4 L3 SC1: Text is not presented over any background (image, text, color or pattern), or if any background is present, the contrast between the text and the background is greater than X2.
  2. 1.4 L3 SC2: Audio content does not contain background sounds or the background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects.

Guideline 2.1

  1. 2.1 L3 SC1: All functionality of the content is designed to be operated through a keyboard interface.

Guideline 2.2

  1. 2.2 L3 SC2: Non-emergency interruptions, such as the availability of updated content, can be postponed or suppressed by the user.
  2. 2.2 L3 SC3: When an authenticated session has an inactivity timeout, the user can continue the activity without loss of data after re-authenticating.

Guideline 2.3

  1. 2.3 L3 SC1:Content does not violate Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash.

Guideline 2.5

  1. 2.5 L3 SC1: Additional context-relevant assistance is available for text input.

Guideline 3.1

  1. 3.1 L3 SC2: A mechanism is available for identifying specific definitions of words used in an unusual or restricted way, including idioms and jargon.
  2. 3.1 L3 SC4: Section titles are descriptive.

Notes

Note 1: ACTION: Wendy to open Bugzilla issue on definition and techniques for ASCII art. See 6 Jan, 2005 teleconference meeting minutes. The definition of non-text content was replaced with: “Content that is not represented by a Unicode character or sequence of Unicode characters. This includes ASCII Art which is a pattern of characters.” (28 July 2005 teleconference)

Note 2: We would like title to be a required attribute on frames so this would be covered by GL 4.2 Level 2. There are no plans to update HTML 4.x or XHTML 1.x. XHTML 2 uses xframes. We requested that title be required on xframes but this was rejected by the HTML working group.

Note 4: In the HTML Techniques, the use of longdesc on frames to describe the purpose and relationships is deprecated. If you can't use longdesc on frames to achieve this, then how can the relationship be programmatically determined as required by GL 1.3?

Note 6: Keyboard shortcuts are still open per discussion at 17 Feb, 2005, teleconference.

Note 7: At the 17 Feb, 2005, teleconference, it was suggested that this maps to GL 2.4 Level 2 SC 1. But this SC is talking about more than one way to locate content. Nav bars are one way to locate content. So it sounds like, in WCAG 1.0, we required a single navigation bar for triple-A conformance but in WCAG 2.0, we require multiple navigation mechanisms for double-A conformance!

Note 8: At the 17 Feb, 2005, teleconference, it was suggested that this also maps to GL 2.4 Level 2 SC 2. However, it's not clear whether GL 2.4 implies any requirements on the search "features". It just suggests that a search "function" is one method of providing multiple ways to locate site content.

Note 9: ACTION: Add a strategy under GL 3.1 Level 3 SC 3 for placing distinguishing information at the beginning of headings, paragraphs, lists, etc. But we have removed the "strategies" from 3.1 Level 3 so does this become "Not required"?

Note 10: At the 17 Feb, 2005, teleconference, it was suggested that the requirement for skipping ASCII art maps to both GL 1.1 Level 1 SC 4 and GL 2.4 Level 2 SC 3. But ASCII art can be non-text content that conveys information, so GL 1.1 Level 1 SC 4 would not apply in that case. However, the definition of non-text content does not currently include ASCII art.

Note 11: Table header information is only repetitive to screen reader users and the technique to abbreviate table headers is only useful when table headers are very verbose. It is possible that this should be advisory in certain cases but not required for conformance at any level.

$Date: 2005/07/26 17:41:15 $ Ben Caldwell.