W3C logoWeb Accessibility Initiative (WAI) logo

WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities

Site Navigation: W3C Home > WAI Home > WCAG 2.0 Overview

The Different WCAG 2.0 Documents*
[Editor's Draft, 4 August 2008]

Status: This document is a draft. Please send comments to wai-eo-editors@w3.org (a publicly archived list).

The Web Content Accessibility Guidelines (WCAG 2.0) is introduced in the Overview of WCAG 2.0 Documents.
[ *Editor's note: The contents and titles of these pages will change as we migrate from WCAG 1.0 to WCAG 2.0.]

This page describes the different WCAG 2.0 documents, to help you know where to go for which type of information.

Different Documents for Different Purposes

@@

Web Content Accessibility Guidelines (WCAG) 2.0 is planned to become a Web Standard "W3C Recommendation" in late 2008. WCAG 2.0 itself is designed as a stable, referenceable technical standard. Most people will use the supporting documents when developing Web content and Web tools, instead of the actual technical standards document.

How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0 requirements (Success Criteria) and techniques is a key resource for designers and developers using WCAG 2.0. It includes all the WCAG 2.0 guidelines and success criteria. The success criteria are the testable statements that define how Web content meets (conforms to) WCAG 2.0. Under each success criteria are a list of sufficient techniques; that is, if you implement those techniques you meet the success criteria. It also lists common failures, that is, things that do not meet the guidelines.

You can customize How to Meet WCAG 2.0 based on whether you are using CSS, JavaScript, or other Web technologies. You can also select to show Level A, AA, or AAA success criteria.

Understanding WCAG 2.0 has additional details on learning and implementing WCAG 2.0 for people who want to understand the guidelines and success criteria more thoroughly.

Techniques for WCAG 2.0 gives specific guidance on how to develop accessible Web content, such as HTML code examples.

Getting from one document to the other

The WCAG 2.0 documents are interlinked. For example:

@@

[ Editor's Note: change doc positions? ]

Single topic pages and whole documents

How to Meet WCAG 2.0 is currently all in one Web page. When you follow a link such as "How to Meet 1.1.1", you go to that section within the whole document.

When you follow links such as "Understanding 1.1.1" or a technique link, you go to a separate Web page that has only that one topic.

The entire Understanding WCAG 2.0 or Techniques for WCAG 2.0 document is available from the "single HTML version" links in the footer of each topic page, and the "Single file version" links near the top of the Contents pages. [Editor's note: ask WCAG WG to use same word here?]