This section is informative.
You are reading the Web Content Accessibility Guidelines (WCAG) version 2.0. This is the central document that defines the requirements for making Web-based information and applications accessible to a wide range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning difficulties, cognitive limitations, limited movement, speech difficulties, and others. Following these guidelines will also make your Web content more usable to the vast majority of users, including older users. It will also enable people to access Web content using many different devices - including a wide variety of assistive technologies and mobile technologies.
WCAG 2.0 covers a wide range of issues and recommendations for making Web content more accessible. The guidelines do not include standard usability recommendations except where they have specific impact on accessibility.
The WCAG 2.0 document itself consists of :
This introduction
Information about conformance to WCAG 2.0
Guidelines with success criteria for each guideline
Links to information on intent, sufficient techniques, examples and benefits for each success criterion
A link to information about the Working Group's approach to defining baseline assumptions about the technologies that are available to end users
Appendices containing definitions, a checklist, references, and other support information.
In addition to WCAG 2.0 (this document) there are a number of related support documents that provide additional information and examples. These other documents are informative only and do not define conformance to WCAG 2.0. Only this document (WCAG 2.0) is normative. That is, only this document can be used for determining conformance to these guidelines. Readers should consult WCAG 2.0 in order to determine the exact wording of the success criteria and for information about documenting conformance.
The other informative documents in this set are provided to help readers understand WCAG 2.0 and how to produce conforming content. These informative documents are written to be used by a diverse audience, including but not limited to:
people who create Web content
developers who write code
QA or accessibility evaluators
policy makers
managers
users
Currently, these informative documents include:
Essential Components of Web Accessibility - Explains how the Web Content Accessibility Guidelines work with the other WAI guidelines (the User Agent Accessibility Guidelines and the Authoring Tool Accessibility Guidelines) and with assistive technologies to provide access to the Web by people with disabilities.
Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents - Provides an overview of WCAG 2.0 and its various informative support documents.
Questions and Answers about Baseline and WCAG 2.0 - Provides additional information on baselines.
Understanding WCAG 2.0 - Provides information about each success criterion including:
its intent,
key terms from the WCAG 2.0 Glossary needed to understand the success criterion,
names of and links to techniques that the working group deems sufficient to meet the success criterion, and
examples and benefits of the success criterion.
Note: Each of the "How to meet SC x.x.x" links in WCAG 2.0 links to the relevant section of the Understanding WCAG 2.0 document.
Technique and Tests documents - Provide specific details on different techniques including examples, code, and tests.
Editorial Note: Some techniques documents are unfinished at this time. However, at least one sufficient technique is documented for each success criterion.
Application Notes - Provide detailed application information in different areas. For example an Application Note on Forms will provide a collection of techniques, and strategies for creating accessible forms. It will also summarize the different success criteria that relate to forms.
Editorial Note: No examples of applicaion notes have been completed as of this release.
The Working Group plans to publish a number of other technology-specific Techniques documents and encourages development of techniques documents that show how to meet WCAG 2.0 using non-W3C technologies. Please visit the Working Group home page for a complete list of these and other informative documents related to WCAG 2.0.
Every attempt has been made to make WCAG 2.0 and the related documents listed above as readable and usable as possible while still retaining the accuracy and clarity needed in a technical specification. Sometimes technical terms are needed for clarity or testability. In these cases, the terms are defined in Appendix A Glossary . The Working Group recognizes that readers who are new to accessibility may need or want additional information. For these readers, the work of the of the Web Accessibility Initiative and its Education and Outreach Working Group is highly recommended. The articles called Getting Started: Making a Web Site Accessible and How People with Disabilities Use the Web are especially useful.
A large part of Web content is created using authoring tools. These tools often determine how Web content is implemented, either by making authoring decisions directly or by limiting the choices available to the author. As a result, authoring tools will play an important role in creating Web content that conforms to the Web Content Accessibility Guidelines. At the same time, we recommend that all authors become familiar with the Guidelines because this will help in creating accessible content and coverage of the Guidelines may vary between tools.
Developers of authoring tools can make their tools aware of the Web Content Accessibility Guidelines by following the Authoring Tool Accessibility Guidelines. The working group encourages users and purchasers of authoring tools to consider conformance to the Authoring Tool Accessibility Guidelines as a criterion when selecting tools. The current version at the time of this document's release can be found at Authoring Tool Accessibility Guidelines.
The WCAG 2.0 Guidelines are organized around the following 4 principles:
Content must be perceivable
Interface components in the content must be operable
Content and controls must be understandable
Content should be robust enough to work with current and future user agents (including assistive technologies)
These four principles lay the foundation necessary for anyone to access and use Web content. WCAG 2.0 offers information about how to increase the ability of people with disabilities to perceive, operate, and understand Web content. Under each principle there is a list of guidelines that address the principle. Under each guideline there are success criteria used to evaluate conformance to this standard for that guideline. The success criteria are written as statements that will be either true or false when specific Web content is tested against the success criteria. The success criteria are grouped into three levels of conformance, each representing a higher level of accessibility for that guideline.
The principles, guidelines, and success criteria represent concepts that apply to all Web-based content. They address accessibility issues and needs, regardless of the technology used. They are not specific to HTML, XML, or any other technology. This approach makes it possible to apply WCAG 2.0 to a variety of situations and technologies, including those that do not yet exist.
The principles and guidelines give direction and guidance to Web authors. The success criteria are written as true/false statements so that they can be used in determining conformance. Only the success criteria are testable.