This is a table view generated from the 09 August 2005 Working Draft. It represents a condensed view of the normative sections of the guidelines at various conformance levels as well as links into the techniques documents.
There are a total of 13 guidelines and 67 success criteria in the 09 August 2005 Working Draft.
Provide text alternatives for all non-text content.
Provide synchronized alternatives for multimedia.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
1.2 L1 SC1 |
Captions are provided for prerecorded multimedia. |
||||
1.2 L1 SC2 |
Audio descriptions of video are provided for prerecorded multimedia |
||||
1.2 L2 SC1 |
Real-time captions are provided for live multimedia. |
||||
1.2 L3 SC1 |
Sign language interpretation is provided for multimedia |
||||
1.2 L3 SC2 |
Extended audio descriptions of video are provided for prerecorded multimedia. |
||||
1.2 L3 SC3 |
Audio descriptions of video are provided for live multimedia. |
Ensure that information, functionality, and structure can be separated from presentation.
Make it easy to distinguish foreground information from background images or sounds.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
1.4 L1 SC1 |
Any text that is presented over a background image, color, or text can be programmatically determined. |
|
|||
1.4 L2 SC1 |
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 _____. |
|
|||
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. |
||||
1.4 L2 SC3 |
A mechanism is available to turn off background audio that plays automatically. |
||||
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. |
|
|||
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. |
Make all functionality operable via a keyboard interface.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
2.1 L1 SC1 |
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. |
|
|||
2.1 L3 SC1 |
All functionality of the content is designed to be operated through a keyboard interface. |
Allow users to control time limits on their reading or interaction.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
2.2 L1 SC1 |
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:
|
|
|||
2.2 L2 SC1 |
Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit. |
|
|||
2.2 L2 SC2 |
Moving or time-based content can be paused by the user. |
|
|||
2.2 L3 SC1 |
Except for real-time events, timing is not an essential part of the event or activity presented by the content. |
||||
2.2 L3 SC2 |
Non-emergency interruptions, such as the availability of updated content, can be postponed or suppressed by the user. |
||||
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. |
Allow users to avoid content that could cause seizures due to photosensitivity.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
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. |
||||
2.3 L2 SC1 |
Content does not violate Computer adapted ITC Guidance for general flash or Computer adapted ITC Guidance for red flash. |
||||
2.3 L3 SC1 |
Content does not violate Computer adapted spatial pattern thresholds or red flash. |
Provide mechanisms to help users find content, orient themselves within it, and navigate through it.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
2.4 L1 SC1 |
Navigational features can be programmatically identified. |
||||
2.4 L2 SC1 |
More than one way is available to locate content within a set of delivery units. |
|
|||
2.4 L2 SC2 |
Blocks of content that are repeated on multiple perceivable units are implemented so that they can be bypassed. |
|
|||
2.4 L2 SC3 |
Delivery units have descriptive titles |
|
|||
2.4 L2 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. |
||||
2.4 L3 SC1 |
When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content. |
|
|||
2.4 L3 SC2 |
Information about the user's location within a set of delivery units is available. |
Help users avoid mistakes and make it easy to correct them.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
2.5 L2 SC1 |
If an input error is detected, the error is identified and provided to the user in text. |
||||
2.5 L2 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. |
||||
2.5 L2 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:
|
||||
2.5 L3 SC1 |
Additional context-relevant assistance is available for text input. |
Make text content readable and understandable.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
3.1 L1 SC1 |
The primary natural language or languages of the delivery unit can be programmatically determined. |
||||
3.1 L2 SC1 |
The natural language of each foreign passage or phrase in the content can be programmatically determined. |
||||
3.1 L3 SC1 |
A mechanism is available for finding definitions for all words in text content. |
|
|||
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. |
||||
3.1 L3 SC3 |
A mechanism for finding the expanded form of acronyms and abbreviations is available. |
|
|||
3.1 L3 SC4 |
Section titles are descriptive. |
||||
3.1 L3 SC5 |
When text requires reading ability at or above the upper secondary education level, one or more of the following supplements is available:
|
Make the placement and functionality of content predictable.
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
3.2 L1 SC1 |
Any change of context is implemented in a manner that can be programmatically determined. |
|
|||
3.2 L2 SC1 |
Components that are repeated on multiple delivery units within a set of delivery units occur in the same order each time they are repeated. |
|
|||
3.2 L2 SC2 |
When any component receives focus, it does not cause a change of context. |
||||
3.2 L2 SC3 |
Changing the setting of any input field does not automatically cause a change of context . |
|
|||
3.2 L2 SC4 |
Components that have the same functionality in multiple delivery units within a set of delivery units are labeled consistently. |
|
|||
3.2 L3 SC1 |
Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear. |
||||
3.2 L3 SC2 |
Changes of context are initiated only by user request. |
Use technologies according to specification.
Ensure that user interfaces are accessible or provide an accessible alternative(s)
ID | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
---|---|---|---|---|---|
4.2 L1 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. |
||||
4.2 L1 SC2 |
Content using baseline technologies or non-baseline technologies, must meet the following criteria:
|
|
|
||
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. |
||||
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. |
||||
4.2 L1 SC5 |
The states and values of content that can be changed via the user interface can also be changed programmatically. |
||||
4.2 L1 SC6 |
Changes to content, structure, selection, focus, attributes, values, state, and relationships within the content can be programmatically determined. |
||||
4.2 L2 SC1 |
Accessibility conventions of the markup or programming language (API's or specific markup) are used. |
||||
4.2 L3 SC1 |
Content implemented using technologies outside of baseline follows all WCAG requirements supported by the technology. |