This is a table view generated from the 11 February 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 77 success criteria in the 11 February 2005 Working Draft.
Provide text alternatives for all non-text content.
Provide synchronized alternatives for multimedia.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | Captions are provided for prerecorded multimedia. (media-equiv-captions) | ||||
| 1 | Audio descriptions of video are provided for prerecorded multimedia (media-equiv-audio-desc) | ||||
| 1 | If multimedia content is rebroadcast from another medium, the accessibility features required by policy for that medium are intact. (media-equiv-rebroadcast) | ||||
| 2 | Real-time captions are provided for live multimedia. (media-equiv-real-time-captions) | ||||
| 3 | Sign language interpretation is provided for multimedia (media-equiv-sign) | ||||
| 3 | Extended audio descriptions of video are provided for prerecorded multimedia. (media-equiv-extended-ad) | ||||
| 3 | Audio descriptions of video are provided for live multimedia. (media-equiv-live-ad) |
Ensure that information, functionality, and structure are separable from presentation.
Make it easy to distinguish foreground information from background images or sounds.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | Any text that is presented over a background image, color, or text can be programmatically determined. (visual-audio-contrast-determined) |
|
|||
| 2 | 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 _____. (visual-audio-contrast-contrast) |
|
|||
| 2 | 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. (visual-audio-contrast-bg-patterns) | ||||
| 2 | Users can disable background audio that plays automatically on a page so that it does not interfere with text reading software they may be using. (visual-audio-contrast-dis-audio) | ||||
| 3 | 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. (visual-audio-contrast-nobg) |
|
|||
| 3 | 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. (visual-audio-contrast-noaudio) |
Make all functionality operable via a keyboard or a keyboard interface.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 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 or keyboard interface. (keyboard-operation-keyboard-operable) |
|
|||
| 2 | Wherever a choice between input device event handlers is available and supported, the more abstract event is used. (keyboard-operation-abstract-events) | ||||
| 3 | All functionality of the content is designed to be operated through a keyboard or keyboard interface. (keyboard-operation-all-funcs) |
Allow users to control time limits on their reading or interaction.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 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: (time-limits-required-behaviors) |
|
|||
| 2 | A method is provided to stop content that blinks for more than 3 seconds. (time-limits-blink) |
|
|||
| 2 | A method is provided to pause and/or permanently stop dynamic (moving or time-based) content. (time-limits-pause) |
|
|||
| 3 | With the exception of real-time events, content has been designed in a way that timing is not designed to be an essential part of the activity and any time limits in the content would pass level 1, success criteria 1 for this guideline. (time-limits-no-exceptions) | ||||
| 3 | Any non-emergency interruptions, such as the availability of updated content, can be postponed and/or suppressed by the user. (time-limits-postponed) |
Allow users to avoid content that could cause photosensitive epileptic seizures.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 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. (flicker-rate-and-warning) | ||||
| 2 | Content does not violate international health and safety standards for general flash or red flash. (flicker-does-not-violate) | ||||
| 3 | Content does not violate international health and safety standards for spatial pattern thresholds or red flash. (flicker-SPT) |
Provide mechanisms to help users find content, orient themselves within it, and navigate through it.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | Structures and relationships within the content can be programmatically determined. (navigation-mechanisms-structure) | ||||
| 2 | Documents that have five or more section headings and are presented as a single delivery unit include a table of contents with links to important sections of the document. (navigation-mechanisms-toc) |
|
|||
| 2 | There is more than one way to locate the content of each delivery unit, including but not limited to link groups, a site map, site search or other navigation mechanism. (navigation-mechanisms-mult-loc) | ||||
| 2 | Blocks of repeated material, such as navigation menus and document headers, are marked up so that they can be bypassed by people who use assistive technology or who navigate via keyboard or keyboard interface. (navigation-mechanisms-skip) |
|
|||
| 3 | When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically. (navigation-mechanisms-one-seq) |
|
|||
| 3 | When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content. (navigation-mechanisms-focus) | ||||
| 3 | Images have structure that users can access. (navigation-mechanisms-images) | ||||
| 3 | Delivery units have descriptive titles (navigation-mechanisms-title) | ||||
| 3 | Text is divided into paragraphs. (navigation-mechanisms-paragraphs) | ||||
| 3 | Documents are divided into hierarchical sections and subsections that have descriptive titles. (navigation-mechanisms-title-subsections) |
Help users avoid mistakes and make it easy to correct them.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 2 | If a user error is detected, the error is identified and provided to the user in text. (minimize-error-identified) | ||||
| 2 | If a user error is detected and suggestions for correction are known and can be provided without jeopardizing security or purpose, the error is identified and the suggestions are provided. (minimize-error-suggestions) | ||||
| 2 | Where consequences are significant and time-response is not important, one of the following is true: (minimize-error-reversible) | ||||
| 3 | Where text entry is required for which there is a known set of less than 75 valid choices and they can be provided without jeopardizing security or purpose, users are allowed to select from a list of options as well as to type the data directly. (minimize-error-selection) | ||||
| 3 | If possible for the natural language of the text, an option is provided to check text entries for misspelled words with suggestions for correct spellings. (minimize-error-spelling) |
Ensure that the meaning of content can be determined.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | The natural language of the document as a whole can be identified by automated tools. (meaning-doc-lang-id) | ||||
| 1 | The meaning of abbreviations and acronyms can be programmatically located. (meaning-located) |
|
|||
| 2 | The meanings and pronunciations of all words in the content can be programmatically located. (meaning-prog-located) |
|
|||
| 2 | The meaning of all idioms in the content can be programmatically determined. (meaning-idioms) | ||||
| 2 | For each foreign language passage or phrase in the body of the content, the language is identified through markup or other means. Foreign passages or phrases are passages or phrases that are in a language other than the primary language of the document. (meaning-other-lang-id) | ||||
| 3 | Where a word has multiple meanings and the intended meaning is not the first in the associated dictionary(s), then additional markup or another mechanism is provided for determining the correct meaning. (meaning-multi-meanings) | ||||
| 3 | Section headings and link text are understandable when read by themselves or as a group (for example, in a screen reader's list of links or a table of contents). (meaning-read-alone) |
|
|||
| 3 | There is a statement associated with the content asserting that the Strategies for Reducing the Complexity of Content (the following list) were considered. (meaning-strategies) |
Organize content consistently from "page to page" and make interactive components behave in predictable ways.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | Any extreme change of context is implemented in a manner that can be programmatically identified. (consistent-behavior-change-of-context) |
|
|||
| 2 | Components that are repeated on multiple "pages" within a resource or a section of a resource occur in the same sequence each time they are repeated, for at least one presentation format. (consistent-behavior-consistent-locations) | ||||
| 2 | All user interface components should be able to receive focus without causing activation. (consistent-behavior-receive-focus) | ||||
| 2 | Changing the setting of any input field should not automatically cause an extreme change in context such as leaving the "page." (consistent-behavior-unpredictable-change) |
|
|||
| 2 | Interactive elements that appear on multiple "pages," including graphical elements, are associated with the same functionality wherever they appear. (consistent-behavior-consistent-functionality) |
|
|||
| 2 | Explicit notice is given in advance of any extreme change of context. (consistent-behavior-unpredictable-warning) | ||||
| 2 | The destination of each link is identified through words or phrases that either occur in the link or can be programmatically determined. (consistent-behavior-target-identified) | ||||
| 3 | Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear. (consistent-behavior-text-equivalents) | ||||
| 3 | Components that appear visually on multiple pages, such as navigation bars, search forms, and sections within the main content, are displayed in the same location relative to other content on every page or screen where they appear. (consistent-behavior-visual-location) | ||||
| 3 | When components such as navigation menus and search forms appear on multiple pages, users can choose to have those elements presented in a different visual position or reading-order. (consistent-behavior-user-choose-order) | ||||
| 3 | There are no extreme changes of context. (consistent-behavior-no-extreme-changes-context) |
Use technologies according to specification.
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | Except where the site has documented that a specification was violated for backward compatibility or compatibility with assistive technology, the technology has: (use-spec-document-backward-compat-violations) |
|
|||
| 3 | Technologies are used according to specification without exception. (use-spec-avoid-spec-no-exception) |
|
Ensure that user interfaces are accessible or provide an accessible alternative(s)
| Level | Success Criteria | General Techniques | HTML Techniques | CSS Techniques | Scripting Techniques |
|---|---|---|---|---|---|
| 1 | At least one user agent supporting the content conforms to at least the default set of conformance requirements of the User Agent Accessibility Guidelines (UAAG) 1.0 at Level A plus the sets of requirements (a) through (i) (below) that apply. If required plug-ins are not accessible, an alternative solution is provided that conforms to WCAG 2.0. If inaccessible plug-ins are available, then a method for obtaining an accessible plug-in is provided from the content. (technology-supports-access-plugins) |
|
|
||
| 1 | Any programmatic user interface components of the content conform to at least the default set of conformance requirements of the UAAG 1.0 at Level A plus the sets of requirements (a) through (i) (below) that apply. If the custom user interfaces cannot be made accessible, an alternative solution is provided that meets WCAG 2.0 (including this provision) to the level claimed. (technology-supports-access-custom-ui) | ||||
| 2 | Accessibility conventions of the markup or programming language (API's or specific markup) are used. (technology-supports-access-use-access-conventions) | ||||
| 3 | The Web resource includes a list of the technologies user agents must support in order for its content to work as intended. The list is documented in metadata if such metadata is supported by the format, otherwise it is documented in a policy statement associated with the content. (technology-supports-access-list-reqd-features) | ||||
| 3 | Users who do not have one or more of these technologies can still access and use the resource, though the experience may be degraded. (technology-supports-access-test-non-reqd) | ||||
| 3 | Technologies and features on the required list are open standards or have a public specification. (technology-supports-access-ensure-avail) |