W3C logoWeb Accessibility initiative

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

Note: This document contains unapproved draft ideas and should not be referenced or quoted under any circumstances.
The current document is available at www.w3.org/WAI/WCAG20/wcag2faq
$Date: 2012/10/02 15:25:12 $


Below are answers to some frequently asked questions (FAQ) about WCAG 2.0. Let us know what other questions you have.
~Shawn Henry, W3C WAI, updated October 2012

Is WCAG 2.0 stable?

Yes. WCAG 2.0 was published as a final W3C Recommendation Web Standard on 11 December 2008. WCAG 2.0 itself is a stable, referenceable standard that will not change.

The supporting resources Techniques for WCAG 2.0 and Understanding WCAG 2.0 are updated periodically (about once a year) to reflect updates in technologies and best practices.

Where should I start?

If you want a really short introduction to 3 web accessibility issues (alternative text for images, keyboard input, and transcripts), see What: Examples of Web Accessibility.

To learn about web accessibility principles and guidelines, see Accessibility Principles.

To learn about WCAG 2.0 specifically, start with the WCAG Overview. It provides an important foundation for understanding the different WCAG 2.0 documents, and points to several resources for using WCAG 2.0.

How to Meet WCAG 2.0: A customizable quick reference is the primary resource for developers using WCAG 2.0.

What are the different WCAG 2.0 documents?

To learn how the different WCAG 2.0 technical documents are related and linked, see The WCAG 2.0 Documents.

Here's a little more perspective on the different technical documents. When web content and web software developers were using WCAG 1.0, they had many questions on how to implement it, how to evaluate for it, and the reasons behind its requirements. WAI wanted to provide this information with WCAG 2.0, and since those details don't fit well in a technical standard, they are in the supporting documents.

Thus with WCAG 2.0, there are extensive supporting materials, which are advisory documents. The WCAG 2.0 guidelines document itself is the only document that is a web standard, and it is fairly short.

Do I have to follow the Techniques to meet WCAG?

No. The Techniques document provides guidance that is "informative". The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard — not the techniques.

You do not have to use the sufficient techniques to meet WCAG. Web content can use other ways to meet the WCAG success criteria. Web content could even fail a particular technique test, yet still meet WCAG a different way. Also, content that uses some of the published techniques does not necessarily meet all WCAG success criteria.

To learn more about the techniques, please see About the Techniques section of How to Meet WCAG 2.0: A customizable quick reference...

Is ISO/IEC 40500 the same as WCAG 2.0?

Yes. WCAG 2.0 is expected to be approved as an ISO standard: ISO/IEC 40500. ISO/IEC 40500 will be exactly the same as the original Web Content Accessibility Guidelines (WCAG) 2.0 from the W3C Web Accessibility Initiative (WAI).

The content of ISO/IEC 40500 is freely available from www.w3.org/TR/WCAG20; it is available for purchase from the ISO catalogue.

For supporting resources that provide practical advice for meeting ISO/IEC 40500 (which is WCAG 2.0), see the WCAG Overview.

If you want more information on W3C and the ISO process, see W3C PAS FAQ.

Benefits of WCAG as ISO

Approval of WCAG 2.0 as an ISO standard benefits countries and organizations that can more easily adopt ISO standards. Countries that previously adapted WCAG 2.0 may now be able to adopt WCAG 2.0 as is by referencing ISO/IEC 40500.

Is WCAG 2.0 available in other languages?

Yes! Authorized Translations and unofficial translations of the technical documents WCAG 2.0, Techniques for WCAG 2.0, and Understanding WCAG 2.0 are listed in WCAG 2.0 Translations.

Unofficial translations of other WAI documents are listed at Translations of W3C Documents - WAI documents - listed by languages and Translations of W3C Documents - WAI documents - listed by document.

For more information on how you can contribute to WAI translations, see Translating WAI Documents.

Does WCAG 2.0 address mobile accessibility?

Yes. See the Mobile Accessibility page.

Can I meet WCAG 2.0 with Javascript/Ajax, Flash, PDF, Silverlight, and other technologies?

WCAG 2.0 is designed to apply to a broad range of technologies.

Techniques for WCAG 2.0 has techniques for several different technologies. Note that publication of techniques for a specific technology does not imply that the technology can be used in all cases to create accessible content that meets WCAG 2.0. Developers need to be aware of the limitations of specific technologies and ensure that they create content in a way that is accessible to all their potential users.

How is WCAG 2.0 different from WCAG 1.0?

Generally, WCAG 2.0 applies broadly to more advanced technologies; is easier to use and understand; and is more precisely testable with automated testing and human evaluation. The fundamental issues of web accessibility are the same, though there are some differences in the approach and requirements between WCAG 1.0 and WCAG 2.0.

Web Content Accessibility Guidelines 1.0 was published in May 1999. WCAG 2.0 was published on 11 December 2008. W3C WAI recommends using WCAG 2.0, instead of WCAG 1.0.

Most websites that conform to WCAG 1.0 should not require significant changes in order to conform to WCAG 2.0, and some will not need any changes at all. For those familiar with WCAg 1.0, it will take a little time to learn the new approach of how the WCAG 2.0 documents provide guidance. To help you move to WCAG 2.0, WAI is developing:

Where can I find answers to more of my questions?

First, look through the documents on the W3C WAI website, which are listed in the annotated list of WAI Resources. WCAG documents are listed in the navigation area of this page.

WAI hosts an Interest Group (WAI IG) mailing list where the community discusses web accessibility issues. WAI IG provides ideas from different perspectives. If you have a question that might be relevant to the WAI IG list, you can:

WAI staff are actively developing guidelines, technical reports, and supporting material, and generally are not available to answer individual questions. However, you can send questions to wai@w3.org and we will integrate answers into this page and other documents as we are able.