Mapping of WCAG 1.0 checkpoints to WCAG 2.0 success criteria

This mapping shows where the WCAG 1.0 checkpoints appear in the 23 November 2005 Working Draft@@ April 2006 Last Call 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 Last Call 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.

Definitions

deprecated (technique or checkpoint)
(technique or checkpoint that is) considered harmful in WCAG 2.0
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 Understanding WCAG 2.0 or as an optional technique in a Techniques Document)
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. Checkpoints must be mapped to an entity [success criterion?] or to an advisory item in Understanding WCAG 2.0.

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. SC 1.1.1 - 1.1.5 (level 1):
  1. For 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. For live audio-only and live video-only, conform to success criterion 1.1.5.
  2. For non-text content that is functional, 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 video-only content, text alternatives at least identify the purpose of the content with a descriptive label.
 SC 1.1.1 (level 1):

For all non-text content, one of the following is true:

  • If non-text content presents information or responds to user input, text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then the text alternative at least identifies the purpose of the non-text content.
  • If non-text content is multimedia; live audio-only or live video-only content; a test or exercise that must use a particular sense; or is primarily intended to create a specific sensory experience; then text alternatives at least identify the non-text content with a descriptive text label. (For multimedia, see also, Guideline 1.2 Provide synchronized alternatives for multimedia .)
  • If the purpose of non-text content is to confirm that content is being operated by a person rather than a computer, different forms are provided to accommodate multiple disabilities. [[new]]
  • If non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by assistive technology.
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. SC 1.3.2 (level 1)
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. SC 1.3.2 (level 1)
Any information that is conveyed by color is visually evident without color.
4.1: Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). SC 3.1.2 (level 2)
The natural language of each foreign passage or phrase in the content can be programmatically determined.
SC 3.1.2 (level 2)
The natural language of each passage or phrase in the Web unit 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. This is baseline-dependentbaseline-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. 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. SC 2.3.1 (level 1): When content violates either the general flash threshold or the red flash threshold, users are warned in a way that they can avoid it.
SC 2.3.2 (level 2): Content does not violate general flash threshold or red flash threshold. SC 2.3.1 (level 1): Content does not violate the general flash threshold or the red flash threshold.
14.1: Use the clearest and simplest language appropriate for a site's content. Some of the Level 3 Success Criteria in GL 3.1Level 3 Success Criteria in GL 3.1 aid in making content understandable. There is no direct mapping.@@id for 3.1 Level 3
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: SC 1.1.1 - 1.1.3 (level 1):
  1. For 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.
 SC 1.1.1 (level 1):

For all non-text content, one of the following is true:

  • If non-text content presents information or responds to user input, text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then the text alternative at least identifies the purpose of the non-text content.
  • If non-text content is multimedia; live audio-only or live video-only content; a test or exercise that must use a particular sense; or is primarily intended to create a specific sensory experience; then text alternatives at least identify the non-text content with a descriptive text label. (For multimedia, see also, Guideline 1.2 Provide synchronized alternatives for multimedia .)
  • If the purpose of non-text content is to confirm that content is being operated by a person rather than a computer, different forms are provided to accommodate multiple disabilities. [[new]]
  • If non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by assistive technology.
 With regard to keyboard access: SC 2.1.1 (level 1), 2.4.52.4.4 (level 2), 4.2.1 (level 1).
SC 2.1.1 (level 1)SC 2.1.1 (level 1):
All functionality of the content is operable in a non time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
SC 2.4.5 (level 2)SC 2.4.4 (level 2):
Each programmatic reference to another delivery unit or to another location in the same delivery unit, is associated with text describing the destination. Each link is programmatically associated with text from which its purpose can be determined.
SC 4.2.1 (level 1)SC 4.2.1 (level 1):
If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
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: SC 1.1.1- 1.1.3 (level 1):
  1. For 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. For live audio-only and live video-only, conform to success criterion 1.1.5.
  2. For non-text content that is functional, 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.
 SC 1.1.1 (level 1):

For all non-text content, one of the following is true:

  • If non-text content presents information or responds to user input, text alternatives serve the same purpose and present the same information as the non-text content. If text alternatives cannot serve the same purpose, then the text alternative at least identifies the purpose of the non-text content.
  • If non-text content is multimedia; live audio-only or live video-only content; a test or exercise that must use a particular sense; or is primarily intended to create a specific sensory experience; then text alternatives at least identify the non-text content with a descriptive text label. (For multimedia, see also, Guideline 1.2 Provide synchronized alternatives for multimedia .)
  • If the purpose of non-text content is to confirm that content is being operated by a person rather than a computer, different forms are provided to accommodate multiple disabilities. [[new]]
  • If non-text content is pure decoration, or used only for visual formatting, or if it is not presented to users, it is implemented such that it can be ignored by assistive technology.
 With regard to keyboard access: SC 2.1.1 (level 1), 2.4.52.4.4 (level 2), 4.2.1 (level 1).
SC 2.1.1 (level 1)SC 2.1.1 (level 1):
All functionality of the content is operable in a non time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
SC 2.4.5 (level 2)SC 2.4.4 (level 2):
Each programmatic reference to another delivery unit or to another location in the same delivery unit, is associated with text describing the destination. Each link is programmatically associated with text from which its purpose can be determined.
SC 4.2.1 (level 1)SC 4.2.1 (level 1):
If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
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. SC 1.3.1 (level 1):
Perceivable structures within the content can be programmatically determined. SC 1.3.1 (level 1):
Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies.
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. SC 1.3.1 (level 1):
Perceivable structures within the content can be programmatically determined. SC 1.3.1 (level 1):
Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies.
And if you use frames (Priority 1) WCAG 2.0 Success Criteria
12.1: Title each frame to facilitate frame identification and navigation. SC 2.4.1 (level 1):
Navigational features within the content can be programmatically determined.SC 4.1.2 (level 1):
For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.@@debatable mapping? OK if frames can be considered user interface components. However, 'Using the title attribute of the frame element' only maps to Level 2 success criteria in 2.4.
SC 2.4.5 (level 2)SC 2.4.4 (level 2):
Each programmatic reference to another delivery unit or to another location in the same delivery unit, is associated with text describing the destination. Each link is programmatically associated with text from which its purpose can be determined.
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.
SC 4.2.1 (level 1)SC 4.2.1 (level 1):
If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
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. SC 1.2.2 (level 1):
Audio descriptions of video are provided for prerecorded multimedia SC 1.2.2 (level 1):
Audio descriptions of video or a full multimedia text alternative including any interaction, 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. SC 1.2.1 (level 1)SC 1.2.1 (level 1):
Captions are provided for prerecorded multimedia.
SC 1.2.2 (level 1):
Audio descriptions of video are provided for prerecorded multimedia SC 1.2.2 (level 1):
Audio descriptions of video or a full multimedia text alternative including any interaction, 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. SC 4.2.1-4.2.2 (level 1)SC 4.2.1 (level 1) & SC 4.2.2 (level 1)
  1. If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.
  2. Content meets the following criteria even if the content uses a technology that is not in the chosen baseline:
    1. When content violates either the general flash threshold or the red flash threshold, users are warned in a way that they can avoid it.
    2. If the user can enter the content using the keyboard, then the user can exit the content using the keyboard.
  1. At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
  2. Content meets the following criteria even if the content uses a technology that is not in the chosen baseline:
    1. If content can be entered using the keyboard, then the content can be exited using the keyboard.
    2. Content conforms to success criterion 2.3.1 (general and red flash).

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]. SC 1.4.1 (level 2)SC 1.4.1 (level 2):
Text or diagrams, and their background, must have a luminosity contrast ratio of at least 5:1.
SC 1.4.3 (level 3) SC 1.4.3 (level 3):
Text or diagrams, and their background, must have a luminosity contrast ratio of at least 10:1.
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.0Understanding WCAG 2.0.
3.2: Create documents that validate to published formal grammars. SC 4.1.1 (level 1)SC 4.1.1 (level 1): Delivery unitsWeb units or authored components can be parsed unambiguously and the relationships in the resulting data structure are also unambiguous.
Note: Validating to published formal grammars is a stronger requirement than unambiguous parsing and is an optional technique for this success criterionoptional technique for this success criterion.@@exact URL
3.3: Use style sheets to control layout and presentation. SC 1.3.5 (level 3)SC 1.3.3 (level 1):
When content is arranged in a sequence that affects its meaning, that sequence can be programmatically determined.When the sequence of the content affects its meaning, that sequence can be programmatically determined.
Maps to several items in Understanding WCAG 2.0Understanding WCAG 2.0: CSS techniques for SC 1.3.1 (level 1)CSS techniques for SC 1.3.1 (level 1)(@@draft), CSS techniques for SC 1.3.2 (level 1)CSS techniques for SC 1.3.2 (level 1), and a client-side scripting technique for SC 1.3.5 (level 3)client-side scripting technique for SC 1.3.3 (level 1)(@@draft).
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. SC 1.3.1 (level 1):
Perceivable structures within the content can be programmatically determined. SC 1.3.1 (level 1):
Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies.
3.6: Mark up lists and list items properly. SC 1.3.1 (level 1):
Perceivable structures within the content can be programmatically determined. SC 1.3.1 (level 1):
Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies.
3.7: Mark up quotations. Do not use quotation markup for formatting effects such as indentation. SC 1.3.1 (level 1):
Perceivable structures within the content can be programmatically determined. SC 1.3.1 (level 1):
Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies.
6.5: Ensure that dynamic content is accessible or provide an alternative presentation or page. SC 4.2.1 (level 1)SC 4.2.1 (level 1):
If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
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). SC 2.2.2 (level 2)SC 2.2.2 (level 2):
Content does not blink for more than 3three seconds, or a method is available to stop anyall blinking content in the delivery unitWeb unit or authored component.
7.4: Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. SC 2.2.1 (level 1)SC 2.2.1 (level 1):
For each time-out that is a function of the content, at least one of the following is true:
  • 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 expiresand given at least 20 seconds to extend the time-out with a simple action (for example, "hit any key") and the user is allowed to extend the timeout at least 10 times 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.
SC 3.2.5 (level 3)SC 3.2.5 (level 3):
Changes of context are initiated only by user request.
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. SC 3.2.5 (level 3)SC 3.2.5 (level 3):
Changes of context are initiated only by user request.
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. SC 3.2.1 (level 1):SC 3.2.1 (level 1):
 When any component receives focus, it does not cause a change of context.
SC 3.2.2 (level 2):SC 3.2.2 (level 1):
 Changing the setting of any input field does not automatically cause a change of context.Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order) unless the authored unit contains instructions before the control that describe the behavior.
SC 3.2.5 (level 3)SC 3.2.5 (level 3):
Changes of context are initiated only by user request.
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 baselinethe document Questions and Answers about Baseline and WCAG 2.0 provides advice about choosing appropriate technologies as related to baseline.
11.2: Avoid deprecated features of W3C technologies.  No longer required for conformance to WCAG 2.0.
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 Understanding WCAG 2.0 (good practice that is encouraged as appropriate). No technique for this seems to exist; Ordering the content in a meaningful sequence addresses something very different. Using h1-h6 to identify headings (for 1.3.1) comes close but does not match well enough. @TODO create optional technique.
13.1: Clearly identify the target of each link. SC 2.4.5 (level 2)SC 2.4.4 (level 2):
Each programmatic reference to another delivery unit or to another location in the same delivery unit, is associated with text describing the destination. Each link is programmatically associated with text from which its purpose can be determined.
SC 2.4.8 (level 3):
The purpose of each link can be programmatically determined from the 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. There are proposals for techniques with metadata for 3.1.5 (supplements), Using the link element and navigation tools (for 2.4.2); no relevant techniques yet for 4.2.
13.3: Provide information about the general layout of a site (e.g., a site map or table of contents). SC 2.4.2 (level 2)SC 2.4.2 (level 2):
More than one way is available to locate content within a set of delivery unitsWeb units where content is not the result of, or a step in, a process or task.
SC 2.4.8 (level 3)SC 2.4.7 (level 3):
Information about the user's location within a set of delivery unitsWeb units is available.
Might also map to an advisory item. No technique for this available. @todo create technique?
Note: this is a partial mapping.
13.4: Use navigation mechanisms in a consistent manner. SC 3.2.3 & 3.2.4 (level 2)SC 3.2.3 & 3.2.4 (level 2):
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. Navigational mechanisms that are repeated on multiple Web units within a set of Web units or other primary resources occur in the same relative order each time they are repeated unless a change is initiated by the user.
4. Components that have the same functionality in multiple delivery units within a set of delivery units areWeb units are identified 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). SC 1.3.5 (level 3)SC 1.3.3 (level 1):
When content is arranged in a sequence that affects its meaningWhen the sequence of the content affects its meaning, that sequence can be programmatically determined.
5.4: If a table is used for layout, do not use any structural markup for the purpose of visual formatting. SC 1.3.1 (level 1): Information and relationships conveyed through presentation can be programmatically determined and notification of changes to these is available to user agents, including assistive technologies. Especially:Failure due to using structural markup in a way that does not represent relationships in the content.@@exact URL in Understanding...
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 specificationnot defined in XHTML 1.1, the Working Draft of XFrames, or the Working Draft of XHTML 2.0). The longdesc attribute is still present in the Frames Module defined in XHTML Modularization.
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 Understanding WCAG 2.0.
Note: this mapping may change if a Success Criterion related to the positioning of labels is created (see action item 1 September 2005). No Success Criterion has been created for this (proposal rejected?); no technique is available.
12.4: Associate labels explicitly with their controls. SC 4.2.4 (level 1):
The label of each user interface control that accepts input from the user can be programmatically determined and is explicitly associated with the control. SC 4.1.2 (level 1):
For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.
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. SC 2.1.1 (level 1)SC 2.1.1 (level 1):
All functionality of the content is operable in a non time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.

Note: device-independent event handlers are not explicitly required.
7.3: Until user agents allow users to freeze moving content, avoid movement in pages. SC 2.2.3 (level 2)SC 2.2.3 (level 2):
Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential.
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. @todo: update User Agent Support for Accessibility with this info?
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.] SC 4.2.1 - 4.2.5 (level 1):
  1. If content does not meet all level 1 success criteria, then an alternate version is available from the same URI that does meet all level 1 success criteria.
  2. Content meets the following criteria even if the content uses a technology that is not in the chosen baseline:
    1. When content violates either the general flash threshold or the red flash threshold, users are warned in a way that they can avoid it.
    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 content and properties of user interface elements that can be changed via the user interface can also be directly changed programmatically.
  6. Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined.
 SC 4.1.2 (level 1), SC 4.2.1 (level 1), SC 4.2.2 (level 1):
  • For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.
  • At least one version of the content meets all level 1 success criteria, but alternate version(s) that do not meet all level 1 success criteria may be available from the same URI.
  • Content meets the following criteria even if the content uses a technology that is not in the chosen baseline
    1. If content can be entered using the keyboard, then the content can be exited using the keyboard.
    2. Content conforms to success criterion 2.3.1 (general and red flash).
9.2: Ensure that any element that has its own interface can be operated in a device-independent manner. SC 2.1.1 (level 1)SC 2.1.1 (level 1):
All functionality of the content is operable in a non time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.
9.3: For scripts, specify logical event handlers rather than device-dependent event handlers. SC 2.1.1 (level 1)SC 2.1.1 (level 1):
All functionality of the content is operable in a non time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input.

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. SC 3.1.4 (level 2)SC 3.1.4 (level 2):
A mechanism for finding the expanded form of abbreviations is available.
4.3: Identify the primary natural language of a document. SC 3.1.1 (level 1)SC 3.1.1 (level 1):
The primary natural language or languages of the delivery unitWeb unit can be programmatically determined.
9.4: Create a logical tab order through links, form controls, and objects. SC 2.4.7 (level 3)SC 2.4.6 (level 3):
When a page or other delivery unitWeb unit or authored component is navigated sequentially, elementscomponents 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 Understanding WCAG 2.0: Providing access keys (optional technique for SC 2.4.1 (level 1)). Providing keyboard access to important links and form controls is empty..@@exact URL in Understanding...
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. No matching technique or failure.
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 Understanding WCAG 2.0. No matching technique or failure.
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 SC 2.4.2 (level 2)SC 2.4.2 (level 2). Technique not available; see How to Meet 2.4.2.
13.6: Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. SC 2.4.3 (level 2)SC 2.4.1 (level 1):
Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed.A mechanism is available to bypass blocks of content that are repeated on multiple Web units.
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 2.4.2 (level 2) and 2.5.4 (level 3) as well as advisory items in Understanding WCAG 2.0.
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 Understanding WCAG 2.0. Part of this maps to an optional technique for SC 2.4.5 (level 3). Starting section headings with unique information is only a draft.
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 SC 2.4.8 (level 3)SC 2.4.7 (level 3) and would appear in advisory items in Understanding WCAG 2.0.Map to items that are not covered by 2.4.7?
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 Understanding WCAG 2.0.No techniques or failures about ASCII art.
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 SC 3.1.5 (level 3)SC 3.1.5 (level 3).
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 3.2.3 (level 2)3.2.3 (level 2), 3.2.4 (level 2)3.2.4 (level 2). 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. 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 Understanding WCAG 2.0.
Note: this is no longer required because of advances in user agents. @todo: update User Agent Support for Accessibility?
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. However, in layout tables, the summary attribute must be omitted or empty. See Failure due to using th elements, caption elements, or non-empty summary attributes in layout tables for 1.3.1.@@exact URL in Understanding...
5.6: Provide abbreviations for header labels. This is no longer required for conformance, but a potentially useful technique.No matching techniques.
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".]No matching failure or other info.

New Level 1 requirements in WCAG 2.0

Guideline 2.3

  1. SC 2.3.1 (level 1): When content violates either the general flash threshold or the red flash threshold, users are warned in a way that they can avoid it.SC 2.3.1 (level 1): Content does not violate the general flash threshold or the red flash threshold.

Guideline 1.3

  1. SC 1.3.2 (level 1): Any information that is conveyed by color is visually evident without color.
  2. SC 1.3.3 (level 1): When the sequence of the content affects its meaning, that sequence can be programmatically determined.

Guideline 2.4

  1. SC 2.4.1 (level 1): Navigational features within the content can be programmatically determined.

Guideline 2.5

  1. SC 2.5.1 (level 1)SC 2.5.1 (level 1): If an input error is detected, the error is identified and described to the user in text.

Guideline 4.1

  1. SC 4.1.1 (level 1)SC 4.1.1 (level 1): Delivery unitsWeb units or authored components can be parsed unambiguously and the relationships in the resulting data structure are also unambiguous.
  2. SC 4.1.2 (level 1): For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies.

Guideline 4.2

  1. SC 4.2.3 (level 1): 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. SC 4.2.4 (level 1): 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. SC 4.2.5 (level 1): The content and properties of user interface elements that can be changed via the user interface can also be directly changed programmatically.
  4. SC 4.2.6 (level 1): 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. SC 1.2.3 (level 2): Audio descriptions of video are provided for prerecorded multimedia.
  2. SC 1.2.3 (level 2)SC 1.2.4 (level 2): Real-time captionsCaptions are provided for live multimedia.

Guideline 1.3

  1. SC 1.3.3 (level 2)SC 1.3.4 (level 2): Information that is conveyed by variations in presentation of text is also conveyed in text or the variations in presentation of text can be programmatically determined.
  2. SC 1.3.4 (level 2): Any information that is conveyed by color is visually evident when color is not available. SC 1.3.5 (level 2): Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components.

Guideline 1.4

  1. SC 1.4.2 (level 2) SC 1.4.2 (level 2): A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio.

Guideline 2.2

  1. SC 2.2.3 (level 2)SC 2.2.3 (level 2): Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential.

Guideline 2.4

  1. SC 2.4.4 (level 2)SC 2.4.3 (level 2): Delivery unitsWeb units have titles.

Guideline 2.5

  1. SC2.5.2 (level 2)SC2.5.2 (level 2): 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 suggestions are provided to the user.
  2. SC 2.5.3 (level 2)SC 2.5.3 (level 2): 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 input 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.

Guideline 3.2

  1. SC 3.2.2 (level 2): Changing the setting of any input field does not automatically cause a change of context .

Guideline 4.2

  1. SC 4.2.3 (level 2): At least one version of the content meets all level 2 success criteria, but alternate version(s) that do not meet all level 2 success criteria may be available from the same URI.

New Level 3 requirements in WCAG 2.0

Guideline 1.1

  1. SC 1.1.6 (level 3): For prerecorded multimedia, a combined document containing captions intermixed with audio description transcripts is available.

Guideline 1.2

  1. SC 1.2.4 (level 3)SC 1.2.5 (level 3): Sign language interpretation is provided for multimedia.
  2. SC 1.2.5 (level 3) SC 1.2.6 (level 3) : Extended audio descriptions of video are provided for prerecorded multimedia.
  3. SC 1.2.7 (level 3): For prerecorded multimedia, a full multimedia text alternative including any interaction is provided.

Guideline 1.3

  1. SC 1.3.5 (level 3): When content is arranged in a sequence that affects its meaning, that sequence can be programmatically determined.
  2. SC 1.3.6 (level 3): Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components.

Guideline 1.4

  1. SC 1.4.3 (level 3)SC 1.4.3 (level 3): Text or diagrams, and their background, must have a luminosity contrast ratio of at least 10:1.
  2. SC 1.4.4 (level 3)SC 1.4.4 (level 3): Audio content does not contain background sounds, background sounds can be turned off, 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. SC 2.1.2 (level 3)SC 2.1.2 (level 3): All functionality of the content is designed to be operatedoperable in a non time-dependent manner through a keyboard interface.

Guideline 2.2

  1. SC 2.2.4 (level 3)SC 2.2.4 (level 3): Except for real-time events, timing is not an essential part of the event or activity presented by the content.
  2. SC 2.2.5 (level 3)SC 2.2.5 (level 3): Interruptions, such as updated content, can be postponed or suppressed by the user, except thoseinterrupations involving an emergency.
  3. SC 2.2.6 (level 3)SC 2.2.6 (level 3): When an authenticated session has an inactivity timeoutexpires, the user can continue the activity without loss of data after re-authenticating.

Guideline 2.3

  1. SC 2.3.2 (level 3): Web units do not contain any compontents that flash more than three times in any one second period.

Guideline 2.4

  1. SC 2.4.6 (level 3)SC 2.4.5 (level 3): Titles and, headings and labels are descriptive.

Guideline 2.5

  1. SC 2.5.4 (level 3)SC 2.5.4 (level 3): Context-sensitive help is available for text input.

Guideline 3.1

  1. SC 3.1.3 (level 3)SC 3.1.3 (level 3): A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
  2. SC 3.1.6 (level 3): A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation.

Guideline 4.2

  1. SC 4.2.7 (level 3)SC 4.2.4 (level 3): Content implemented using technologies outside of the chosen baseline satisfies all level 1 and 2 WCAG requirements supported by the technologies.