This draft includes a number or editorial changes, recent proposals and an additional level of conformance.
W3C published the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) as a Recommendation in May 1999. This Working Draft for version 2.0 builds on WCAG 1.0. It has the same aim: to explain how to make Web content accessible to people with disabilities and to define target levels of accessibility. Incorporating feedback on WCAG 1.0, this Working Draft of version 2.0 focuses on checkpoints. It attempts to apply checkpoints to a wider range of technologies and to use wording that may be understood by a more varied audience.
This document is an editors' copy that has no official standing.
This document is prepared by the Web Content Accessibility Guidelines Working Group (WCAG WG) to show how more generalized (less HTML-specific) WCAG checkpoints might read. This draft is not yet based on consensus of the WCAG Working Group nor has it gone through W3C process. This Working Draft in no way supersedes WCAG 1.0.
This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of current W3C Recommendations and other technical documents is available.
The Working Group welcomes comments on this document at email@example.com. The archives for this list are publicly available. Archives of the WCAG WG mailing list discussions are also publicly available.
Patent disclosures relevant to this specification may be found on the WCAG Working Group's patent disclosure page in conformance with W3C policy.
This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG WG are discussed in the Working Group charter. The WCAG WG is part of the WAI Technical Activity.
Editorial Note (06/10/03): There is discussion about moving some of the current success criteria from Required to Best Practice or to an Extended checkpoint. The issue stems from trying to apply the success criteria to every Web cam, newscast, and home broadcast. Another approach is to allow a conformance claim to state, for example, "All pages and applications on this site meet the Core checkpoints of WCAG 2.0 except the Web cam at http://example.org/webcam/."
All Core Success Criteria for this checkpoint have been met (link to 1.2 in Core)
Editorial Note: This whole Checkpoint (1.2) needs reworking. Perhaps move some down from above, or limit the items above to just certain classes of content - and then put the rest of the coverage (for other types of content) here.
All Core Success Criteria for this checkpoint have been met (link to 1.3 in Core)
any information presented using color is also available without color and without having to interpret markup.[I#317]
All Core Success Criteria for this checkpoint have been met (link to 1.4 in Core)
abbreviations and acronyms are clearly identified each time they occur if they collide with a word in the standard language that would also logically appear in the same case (e.g. all caps). (See also checkpoint 3.1) [I#341]
symbols such as diacritic marks that are found in standard usage of the natural language of the content, and that are necessary for unambiguous identification of words, are present or another standard mechanism for disambiguation is provided.
the structural elements present have a different visual appearance or auditory characteristic from each other and from body text.
the structural emphases are chosen to be distinct on different major visual display types (e.g. black and white, small display, mono audio playback).
content is constructed such that users can control the presentation of the structural elements.
text content that is presented over a background image or pattern is implemented using mechanisms that allow the user to display the text without the background image or pattern.
text that is presented over a background color or grayscale has a mechanism that allows the text to be presented in a fashion that has a contrast greater than ______ between text and background color as measured by ______.[I#344]
when text content is presented over a background image or pattern, the text is easily readable when the page is viewed in 256 grayscale.
text content is not presented over a background image or pattern OR the text is easily readable when the page is viewed in black and white (no grayscale).
this item should read identically to the required item #2, except that it should say "in default presentation mode"[I#345]
audio content does not contain background sounds OR the background sounds are at least 20 db lower than the foreground audio content.
A 20 db difference in sound level is roughly 4 times quieter (or louder).
Editorial Note: The working group is seeking an algorithm that measures contrast in a way that is accurate and testable enough that we could include it in the guidelines. One algorithm, which comes from the Techniques For Accessibility Evaluation And Repair Tools document, is currently under consideration for inclusion in the techniques, but the group has not yet found something that is specific enough to be included at the guidelines level.
All Core Success Criteria for this checkpoint have been met (link to 2.2 in Core)
wherever possible, activities are designed so that time limits are not an essential part of the activity. (e.g. alternate forms of competition, testing, etc. are used that are not time based.)
any blinking content can be turned off.[I#325]
any moving content can be frozen using the keyboard[I#325]
Editorial Note (06/10/03): This Checkpoint is currently included in the Core set of Checkpoints because the WCAG WG expects that it will be possible to test content for flicker and the result will be a flicker rate in Hz that can be stored in a machine-readable format. The WG also expects that a user could, in the future, be able to configure a client to only render content that flickers at "a rate greater than X" by which the client could compare the content metadata and the user's preference. If the assumption regarding a testing tool does not hold at time of final review of these guidelines, this checkpoint will be moved to the Extended set of Checkpoints."
animation or other content does not visibly or purposely flicker between 3 and 49 Hz.
content that might create a problem has been tested [using XYZ tool]; only pages with unavoidable flicker remain and appropriate warnings along with a close alternative presentation have been provided for these pages.
(tougher test - that would make pages pass with even slower equipment. Hardware might be old or just slow for other reasons.) [I#321]
In documents greater than 50,000 words or sites larger than 50 perceived pages, the following are provided.
hierarchical structure mark up
Table of contents (or site map)
Alternate display orders (or alternate site navigation mechanisms)
Users are able to skip over large blocks of repetitive material, navigational bars or other blocks of links that are greater than 7 when reading with a synthesizer or navigating using keyboard.[I#323]
the content has been reviewed, taking into account the following strategies for facilitating orientation and movement, applying them as appropriate.
breaking up text into logical paragraphs
providing hierarchical sections and titles, particularly for longer documents
revealing important non-hierarchical relationships, such as cross-references, or the correspondence between header and data cells in a table, so that they are represented unambiguously in the markup or data model
dividing very large works into sections and or chapters with logical labels
if an error is detected, feedback is provided to the user identifying the error (in an accessible form that meets core checkpoints). [I#349]
where possible, the user is allowed to select from a list of options as well as to generate input text directly
errors are identified specifically and suggestions for correction are provided where possible
checks for misspelled words are applied and correct spellings are suggested when text entry is required.
where consequences are significant and time-response is not important, one of the following is true
actions are reversible where possible
where not reversible, actions are checked for errors in advance
where not reversible, and not checkable, a confirmation is asked before acceptance
acronyms and abbreviations do not appear first in standard unabridged dictionaries for the language or define the first time the first time they appear or are available in a glossary on the site.[I#330]
a list is provided on the page or home page of URIs to cascading dictionaries that can or should be used to define abbreviations or acronyms.[I#350]
Editorial Note: If a standard format for doing it can be achieved, we might require that linkages to glossaries for all abbreviations and acronyms that are created by the author or site be provided. We could also recommend that linkages to any abbreviations, acronyms, etc. used by the authors also be provided. We could also have a weaker recommendation for acronyms and abbreviations appearing on the site that linkages to glossaries explaining all abbreviations acronyms, etc. that appear in any documents on the site be provided.
the content has been reviewed, taking into account the following strategies for evaluating the complexity of the content, applying them as appropriate.
familiarity of terms and language structure
reasonableness of length and complexity of sentences
coherence of paragraphs (and sensibility in length)
clarity of headings and linked text when read out of context
accuracy and uniqueness of page titles
care in the use of all-capital letters where normal sentence case might increase comprehension
inclusion of non-text content to supplement text for key pages or sections of the site where they felt it was appropriate.
key orientation and navigational elements (such as navigation bars) are generally found in one or two consistent locations or their locations are otherwise predictable.
where inconsistent or unpredictable responses are essential to the function of the content (e.g. mystery games, adventure games, tests, etc.) the user is warned in advance of encountering them.
wherever there are extreme changes in context, one of the following is true:
an easy to find setting, that persists for the site visit, is provided for the user to deactivate processes or features that cause extreme changes in context or
extreme changes in context are identified before they occur so the user can determine if they wish to proceed or so they can be prepared for the change
user can select a different location for navigation elements in the layout of the page.[I#352]
All Core Success Criteria for this checkpoint have been met (link to 4.1 in Core)
deprecated features of markup are avoided.[I#329]
Same as item #1 above, without the exception for backward compatibility.
the Web resource includes a list of the technologies (other than standard HTML) users must have in order for its content to work as intended. Users who do not have one or more of these technologies can still access and use the resource, though the experience may be degraded.[I#351]
When determining your list of technological requirements, consider that assistive hardware and software is often slow to adapt to technological advances, and the availability of assistive technology varies across natural languages. Verify that assistive technology compatible with the technologies you choose is available in the natural language(s) of your content.
a list of technologies and features, support for which is required in order for the content to be operable, has been determined and is documented in metadata and / or a policy statement associated with the content.
Technologies and features on the required list are available in at least two independently-developed implementations.
Editorial Note: This checkpoint is currently in the set of extended checkpoints. The implications of this are that there is no core checkpoint that says content must transform gracefully or that it must be backwards compatible. However, if the set of core checkpoints is designed well, core conformance would result in content that transforms gracefully. This checkpoint might be too subjective or difficult to test and may be deleted.
Editorial Note: The WCAG WG is considering whether to delete this checkpoint because it is about the development process rather than about the characteristics of accessible content. What are the implications of deleting this checkpoint? Should there be any checkpoints related to the development process?
any applications with custom user interfaces conform to at least Level A of the User Agent Accessibility Guidelines 1.0. If the application cannot be made accessible, an alternative, accessible solution is provided.
the technology or combination of technologies chosen:
support device independence
include accessibility features
have publicly documented interfaces for interoperability
make use of operating system accessibility features (either directly or via the user agent) supported by assistive technologies in the natural language(s) of the content
are implemented in user agents and/or proxies in the natural language(s) of the content [I#331]
accessibility conventions of the markup or programming language (API's or specific markup) are used [I#331]