• Skip to content
• | Change text size or colors

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

Site Navigation

W3C Home

Web Accessibility Initiative (WAI) Home

1. Introducing Accessibility
2. Guidelines & Techniques
   1. Web Content (WCAG)
      • 1.0 documents
        1. Checklist of Checkpoints
        2. WCAG 1.0
        3. Errata
        4. Translations
        5. Techniques
        6. Core Techniques
        7. HTML Techniques
        8. CSS Techniques
      • 1.0 resources
        1. Navigating
        2. Fact Sheet (FAQ)
        3. Curriculum
        4. Conformance Logos
      • 2.0 WD documents
        1. WCAG 2.0 Working Draft
        2. WCAG 2.0 Checklist
        3. General Techniques
        4. HTML Techniques
        5. CSS Techniques
        6. Scripting Techniques
        7. Requirements WCAG 2.0
        8. Requirements Checklists & Techniques
      • 2.0 resources
        1. »WCAG 2.0 WD Intro
   2. Authoring Tool (ATAG)
   3. User Agent (UAAG)
   4. Evaluation Language (EARL)
   5. Specific Technologies
3. Managing Accessibility
4. Evaluating Accessibility
5. WAI Groups
6. About WAI

Introduction to Web Content Accessibility Guidelines (WCAG) 2.0 Working Draft Documents

Introduction

This page introduces WCAG 2.0 Working Draft documents as of June 2005. For general information about Web Content Accessibility Guidelines (WCAG) and WCAG 1.0, see Web Content Accessibility Guidelines (WCAG) Overview.

Web Content Accessibility Guidelines 1.0 was approved in May 1999 and is the stable and referenceable version.

WCAG 2.0 is being developed to apply to different Web technologies, be easier to use and understand, and be more precisely testable, as documented in Requirements for WCAG 2.0. Because of the nature of the W3C specification development process, WAI cannot be certain when the final version of WCAG 2.0 will be available. WCAG 1.0 will remain the latest approved version until WCAG 2.0 is complete.

WCAG 2.0 Working Draft Documents

WCAG 2.0

The main WCAG 2.0 document applies to all Web content; it is not specific to any one Web technology.

WCAG 2.0 is organized around four design principles for Web accessibility:

1. Content must be perceivable
2. Interface elements in the content must be operable
3. Content and controls must be understandable
4. Content must be robust enough to work with current and future Web technologies

Under each principle are guidelines that define how the principle applies in a specific area.

Under each guideline are success criteria, definitions, benefits, and examples. Success criteria are testable statements to further define the guideline and to determine conformance.

Checklist of Success Criteria

The Web Content Accessibility Guidelines 2.0 Checklist is a list of the WCAG 2.0 success criteria, which are testable statements that define what is required to meet WCAG 2.0.

Techniques

General Techniques for WCAG 2.0 applies to all Web content; it is not specific to any one technology. The General Techniques document provides implementation guidance, explanations, and strategies.

Each technology-specific techniques document provides implementation guidance, preferred approaches, and markup examples for a specific Web technology.

• HTML Techniques for WCAG 2.0
• CSS Techniques for WCAG 2.0
• Client-side Scripting Techniques for WCAG 2.0
• (Additional technology-specific techniques will be available with future Working Drafts, such as Sever-Side Scripting, SMIL, and SVG Techniques.)

The techniques documents are organized by topic; for example, HTML Techniques includes sections on forms, images, lists, links, tables, etc.

Test Suites

Test suites provide sample files that can be used for testing accessibility implementations for a specific Web technology.

• (HTML, CSS, and other Test Suites will be available with future Working Drafts)

Customized test suites are generated based on selected Web technologies, elements, and other criteria.

Navigating WCAG 2.0 Documents

Throughout the documents are links to related information in other documents. Navigation between documents may change in future designs of WCAG 2.0.

How WCAG 2.0 Working Drafts Differ from WCAG 1.0

WCAG 2.0 Working Drafts are much more robust, technology-independent, testable, and with more supporting information that WCAG 1.0.

WCAG 1.0 Priority Checkpoints

WCAG 1.0 is organized around guidelines that have checkpoints, which are priority 1, 2, or 3. The basis for determining conformance to the WCAG 1.0 are the checkpoints.

WCAG 2.0 Level Success Criteria

The current WCAG 2.0 Working Draft is organized around four design principles of Web accessibility. Each principle has guidelines, and each guideline has success criteria at level 1, 2, or 3. The basis for determining conformance to the WCAG 2.0 Working Draft are the success criteria.

Differences in Techniques Documents

The Techniques for WCAG 1.0 document, sometimes called the "Techniques Gateway", provides only links to relevant technology-specific techniques documents, as explained in Navigating WCAG 1.0 Guidelines and Techniques Documents. A separate document, Core Techniques for WCAG 1.0, provides general techniques. WCAG 1.0 has two technology-specific techniques documents, covering HTML and CSS.

General Techniques for WCAG 2.0 provides both general techniques and links to technology-specific techniques documents. There will be several techniques documents for WCAG 2.0, including HTML, CSS, scripting, and others. The technology-specific techniques documents for WCAG 2.0 are much more robust and complete. They also link to evaluation information in the WCAG 2.0 test suite.

Mapping Between WCAG 1.0 and WCAG 2.0

Mapping Between WCAG 1.0 and the WCAG 2.0 Working Draft is a draft document that shows the relationship between WCAG 1.0 checkpoints and WCAG 2.0 Working Draft guidelines.

WAI will provide additional resources to help organizations that are currently using WCAG 1.0 transition to WCAG 2.0.

Comparison Diagrams

Document Information

Version: 2.1 (to be edited with next WCAG 2.0 Working Draft release in 2005)
Feedback welcome to wai-eo-editors@w3.org.

Editor: Shawn Lawton Henry. Developed with the Education and Outreach Working Group (EOWG) and the Web Content Accessibility Guidelines Working Group (WCAG WG).
File (not content) last updated $Date: 2005/07/27 09:02:14 $ by $Author: nobody $

[Contacting WAI]