This section is informative.
This mapping shows how the WCAG 1.0 checkpoints relate to the WCAG 2.0 Last Call Working Draft released 27 April 2006. Note that WCAG 2.0 is still a draft and the WCAG 2.0 Guidelines and success criteria 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 a stable and referenceable document) to ensure that they will be able to make a smooth transition to WCAG 2.0 when it is released.
| 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. |
1.1.1 For all non-text content, one of the following is true: (Level 1)
For scripts, applets, and objects, alternative versions are covered under Guideline 4.2, and labels under Guideline 1.1 (See also SC 2.4.6 (Level 3) and SC 4.1.2 (Level 1).). Images used as bullets are also covered in Guideline 1.3 with regard to CSS usage. For framesets, |
| 2.1: Ensure that all information conveyed with color is also available without color, for example from context or markup. |
1.3.2 Any information that is conveyed by color is also visually evident without color. (Level 1) |
| 4.1: Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). |
3.1.2 The natural language of each passage or phrase in the Web unit can be programmatically determined. (Level 2) Note: This requirement does not apply to individual words or phrases that have become part of the primary language of the content. 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-dependent:
|
| 6.2: Ensure that equivalents for dynamic content are updated when the dynamic content changes. | Text alternatives are addressed in Guideline 1.1, 1.2, and 4.2. If providing a text alternative for content and that content changes, then the text alternative must also be changed or else you don't conform to Guideline 1.1, 1.2, and 4.2 anymore. |
| 7.1: Until user agents allow users to control flickering, avoid causing the screen to flicker. |
2.3.1 Content does not violate the general flash threshold or the red flash threshold. (Level 1) 2.3.2 Web units do not contain any components that flash more than three times in any 1-second period. (Level 3) |
| 14.1: Use the clearest and simplest language appropriate for a site's content. |
Some of the Level 3 success criteria in Guideline 3.1 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: 1.1.1 For all non-text content, one of the following is true: (Level 1)
With regard to keyboard access: 2.1.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. (Level 1) Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. 2.4.4 Each link is programmatically associated with text from which its purpose can be determined. (Level 2) 4.2.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. (Level 1) 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: 1.1.1 For all non-text content, one of the following is true: (Level 1)
With regard to keyboard access: 2.1.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. (Level 1) Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. 2.4.4 Each link is programmatically associated with text from which its purpose can be determined. (Level 2) 4.2.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. (Level 1) 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. |
1.3.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. (Level 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. |
1.3.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. (Level 1) |
| And if you use frames (Priority 1) | WCAG 2.0 Success Criteria |
| 12.1: Title each frame to facilitate frame identification and navigation. |
2.4.1 A mechanism is available to bypass blocks of content that are repeated on multiple Web units. (Level 1) 2.4.4 Each link is programmatically associated with text from which its purpose can be determined. (Level 2) 4.1.2 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. (Level 1) |
| 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:
4.2.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. (Level 1) 4.2.3 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. (Level 2) |
| 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. |
1.2.2 Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia. (Level 1) |
| 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. |
1.2.1 Captions are provided for prerecorded multimedia. (Level 1) 1.2.2 Audio descriptions of video, or a full multimedia text alternative including any interaction, are provided for prerecorded multimedia. (Level 1) 1.2.3 Audio descriptions of video are provided for prerecorded multimedia. (Level 2) 1.2.4 Captions are provided for live multimedia. (Level 2) 1.2.6 Extended audio descriptions of video are provided for prerecorded multimedia. (Level 3) |
| 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. |
4.2.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. (Level 1) 4.2.2 Content meets the following criteria even if the content uses a technology that is not in the chosen baseline: (Level 1)
|
| 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]. |
1.4.1 Text or diagrams, and their background, have a luminosity contrast ratio of at least 5:1. (Level 2) 1.4.3 Text or diagrams, and their background, have a luminosity contrast ratio of at least 10:1. (Level 3) |
| 3.1: When an appropriate markup language exists, use markup rather than images to convey information. |
This is baseline-dependent. The guidance on choosing an appropriate baseline will include information about the advantages of technologies with accessibility features. This also maps to sufficient techniques on using semantic markup listed in How to Meet Success Criterion 1.3.1 (level 1) and How to Meet Success Criterion 1.3.4 (level 2). |
| 3.2: Create documents that validate to published formal grammars. |
4.1.1 Web units or authored components can be parsed unambiguously, and the relationships in the resulting data structure are also unambiguous. (Level 1) Note: Validating to published formal grammars is a stronger requirement than unambiguous parsing required by Success Criterion 4.1.1 but is one of the sufficient techniques for this success criterion. Refer to How to Meet Success Criterion 4.1.1 |
| 3.3: Use style sheets to control layout and presentation. |
1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined. (Level 1) Maps to several items in Understanding WCAG 2.0: CSS techniques for SC 1.3.1 (level 1), CSS techniques for SC 1.3.2 (level 1), and a client-side scripting technique for SC 1.3.3 (level 1). |
| 3.4: Use relative rather than absolute units in markup language attribute values and style sheet property values. |
This maps to an advisory technique (Using readable fonts) for Guideline 1.4. |
| 3.5 Use header elements to convey document structure and use them according to specification. |
1.3.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. (Level 1) |
| 3.6: Mark up lists and list items properly. |
1.3.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. (Level 1) |
| 3.7: Mark up quotations. Do not use quotation markup for formatting effects such as indentation. |
1.3.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. (Level 1) 1.3.4 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. (Level 2) |
| 6.5: Ensure that dynamic content is accessible or provide an alternative presentation or page. |
4.2.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. (Level 1) 4.2.3 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. (Level 2) |
| 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). |
2.2.2 Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web unit or authored component. (Level 2) Note: For requirements related to flickering or flashing content, refer to Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity . |
| 7.4: Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. |
2.2.1 For each time-out that is a function of the content, at least one of the following is true: (Level 1)
3.2.5 Changes of context are initiated only by user request. (Level 3) |
| 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. |
3.2.5 Changes of context are initiated only by user request. (Level 3) |
| 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. |
3.2.1 When any component receives focus, it does not cause a change of context. (Level 1) 3.2.2 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. (Level 1) 3.2.5 Changes of context are initiated only by user request. (Level 3) |
| 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: The document About Baselines and WCAG 2.0 provides advice about choosing appropriate technologies as related to setting baselines. |
| 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 partially maps to a sufficient technique for SC 2.4.1 (level 1): Providing Heading elements at the beginning of each section of content. |
| 13.1: Clearly identify the target of each link. |
2.4.4 Each link is programmatically associated with text from which its purpose can be determined. (Level 2) 2.4.8 The purpose of each link can be programmatically determined from the link. (Level 3) |
| 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, 3.1 and 1.3. This is also baseline-dependent. |
| 13.3: Provide information about the general layout of a site (e.g., a site map or table of contents). |
2.4.2 More than one way is available to locate content within a set of Web units where content is not the result of, or a step in, a process or task. (Level 2) This also maps to the technique Providing a Site Map. Note: This is a partial mapping. |
| 13.4: Use navigation mechanisms in a consistent manner. |
3.2.3 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. (Level 2) 3.2.4 Components that have the same functionality within a set of Web units are identified consistently. (Level 2) |
| 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). |
1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined. (Level 1) |
| 5.4: If a table is used for layout, do not use any structural markup for the purpose of visual formatting. |
1.3.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. (Level 1) Especially: Failure of SC 1.3.1 due to using structural markup in a way that does not represent relationships in the content. |
| 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 not defined in XHTML 1.1, the Working Draft of XFrames, or the Working Draft of XHTML 2.0). The |
| 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. |
User agents now support explicit associations of labels with form controls, so the "until user agents" clause has been satisfied. This is therefore no longer a requirement under WCAG 2.0. It is an Advisory item. Other closely related SC are: 1.3.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. (Level 1) 1.3.4 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. (Level 2) |
| 12.4: Associate labels explicitly with their controls. |
1.3.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. (Level 1) 4.1.2 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. (Level 1) |
| 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. |
2.1.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. (Level 1) Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. 2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface. (Level 3) Note: Device-independent event handlers are not explicitly required. |
| 7.3: Until user agents allow users to freeze moving content, avoid movement in pages. |
The "until user agents" clause has been satisfied, so it is no longer necessary to avoid movement altogether, as long as authors do not do anything to interfere with the user's ability to pause the content. The prohibition has therefore been replaced with this success criterion 2.2.3 2.2.3 Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential. (Level 2) |
| 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.] |
4.1.2 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. (Level 1) 4.2.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. (Level 1) 4.2.2 Content meets the following criteria even if the content uses a technology that is not in the chosen baseline: (Level 1)
|
| 9.2: Ensure that any element that has its own interface can be operated in a device-independent manner. |
2.1.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. (Level 1) Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. 2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface. (Level 3) |
| 9.3: For scripts, specify logical event handlers rather than device-dependent event handlers. |
2.1.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. (Level 1) Note: This does not preclude and should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. 2.1.2 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface. (Level 3) |
| 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. |
3.1.4 A mechanism for finding the expanded form of abbreviations is available. (Level 3) |
| 4.3: Identify the primary natural language of a document. |
3.1.1 The primary natural language or languages of the Web unit can be programmatically determined. (Level 1) |
| 9.4: Create a logical tab order through links, form controls, and objects. |
2.4.6 When a Web unit or authored component is navigated sequentially, components receive focus in an order that follows relationships and sequences in the content. (Level 3) |
| 9.5: Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. |
Accesskeys are no longer required for conformance to WCAG 2.0. It is an advisory item: Providing access keys (optional technique for SC 2.4.1 (level 1)). |
| 10.5: Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. |
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 item (see Situation B under How to Meet Success Criterion 4.2.1, for example). Content negotiation is discussed briefly in "Conformance to Web Content Accessibility Guidelines 2.0." |
| 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). If navigation bars are used, SC 3.2.3 (level 2) applies. 3.2.3 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. (Level 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. |
2.4.1 A mechanism is available to bypass blocks of content that are repeated on multiple Web units. (Level 1) Note: In WCAG 2.0, this requirement applies only 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. . Part of this maps to optional techniqueStarting section headings with unique information for SC 2.4.5 (level 3). |
| 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.7 (level 3) and would appear in advisory items in Understanding WCAG 2.0. |
| 13.10: Provide a means to skip over multi-line ASCII art. |
This item is not required by any Success Criterion in WCAG 2.0. ASCII art is considered non-text content and is therefore covered by SC 1.1.1. |
| 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. Providing visual illustrations of complex ideas, events, and processes and Providing a spoken version of the text are listed as is a technique that can be used to satisfy WCAG 2.0 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.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. |
This is no longer required because user agents now render text alternatives for client-side image map areas. |
| 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 of SC 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables. |
| 5.6: Provide abbreviations for header labels. |
This is no longer required for conformance, but a potentially useful technique. |
| 10.3: Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. |
WCAG 1.0 Checkpoint 10.3 is no longer required for conformance to WCAG 2.0. 1.3.3 When the sequence of the content affects its meaning, that sequence can be programmatically determined. (Level 1) 2.4.6 When a Web unit or authored component is navigated sequentially, components receive focus in an order that follows relationships and sequences in the content. (Level 3) |
| 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. |
This "until user agents" condition is now met and this checkpoint is no longer required. |
2.5.1 If an input error is detected, the error is identified and described to the user in text. (Level 1)
1.3.4 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. (Level 2)
1.3.5 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components. (Level 2)
1.4.2 A mechanism is available to turn off background audio that plays automatically, without requiring the user to turn off all audio. (Level 2)
2.4.3 Web units have titles. (Level 2)
2.5.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. (Level 2)
2.5.3 For forms that cause legal or financial transactions to occur, that modify or delete data in data storage systems, or that submit test responses, at least one of the following is true: (Level 2)
Actions are reversible.
Actions are checked for input errors before going on to the next step in the process.
The user is able to review and confirm or correct information before submitting it.
1.2.5 Sign language interpretation is provided for multimedia. (Level 3)
1.2.7 For prerecorded multimedia, a full multimedia text alternative including any interaction is provided. (Level 3)
1.4.4 Audio content does not contain background sounds, background sounds can be turned off, or background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects. (Level 3)
Note: A 20 decibel difference in sound level is roughly four times (4x) quieter or louder. Background sound that meets this requirement will be approximately four times (4x) quieter than the foreground audio content.
2.2.4 Except for real-time events, timing is not an essential part of the event or activity presented by the content. (Level 3)
2.2.5 Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an emergency. (Level 3)
2.2.6 When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level 3)
2.4.5 Titles, headings, and labels are descriptive. (Level 3)
2.5.4 Context-sensitive help is available for text input. (Level 3)
3.1.3 A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level 3)
3.1.6 A mechanism is available for identifying specific pronunciation of words where meaning cannot be determined without pronunciation. (Level 3)
4.2.4 Content implemented using technologies outside of the chosen baseline satisfies all Level 1 and Level 2 requirements supported by the technologies. (Level 3)