W3C logoWeb Accessibility Initiative

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


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

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.

What about WCAG 2.1?

WCAG 2.1 is currently in development and is scheduled to be published as a standard by June 2018. The primary focus for WCAG 2.1 is accessibility requirements for mobile accessibility, people with low vision, and people with cognitive and learning disabilities.

WCAG 2.1 is designed to be "backwards compatible" so websites that conform to WCAG 2.1 will also conform to WCAG 2.0 — which means that a website that meets WCAG 2.1 will meet the requirements of policies that reference WCAG 2.0.

Additional information:

After WCAG 2.1

The Accessibility Guidelines Working Group is also exploring future accessibility guidelines through the Silver Task Force. Additional information is available in a Silver presentation. This project will take several years.

In the interim, the Working Group might decide to develop WCAG 2.2 to provide additional updates to address current accessibility requirements.

Does WCAG 2.0 address mobile accessibility?

Yes. See the Mobile Accessibility page.

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 content authors (developers, designers, etc.) have to follow W3C's techniques to meet WCAG?

No, you do not have to use the techniques in W3C's Techniques for WCAG 2.0 document.

The techniques are informative; that means they are not required. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard — not the techniques.

While many authors find W3C-documented techniques useful, there may be other ways to meet WCAG success criteria. You can use other techniques. Web content could even fail a particular technique test, yet still meet WCAG in a different way. Also, content that uses some of the Techniques does not necessarily meet all WCAG success criteria.

For important additional information, see the Understanding Techniques for WCAG Success Criteria section of Understanding WCAG 2.0.

What would be the negative consequences of allowing only W3C's published techniques to be used for conformance to WCAG 2.0?

Background: Some organizations have considered requiring all web content to use W3C's published techniques.

W3C recommends that the only thing that is required is meeting the WCAG 2.0 success criteria. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard — not the techniques. W3C's Techniques for WCAG 2.0 document is informative (that is, not required, non-normative).

W3C cautions against requiring web content to use only W3C's published sufficient techniques and not allowing other techniques for several reasons, including:

Therefore, W3C's published techniques should not be required as the only way to meet WCAG 2.0 success criteria unless the limitations and consequences above are understood and acceptable.

For additional information, see: Understanding Techniques for WCAG Success Criteria section of Understanding WCAG 2.0

Is ISO/IEC 40500 the same as WCAG 2.0?

Yes. WCAG 2.0 is approved as an ISO standard: ISO/IEC 40500:2012. ISO/IEC 40500 is 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.

The approval was announced 15 October 2012 in a press release and blog post. 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.


W3C has offered our WCAG 2.0 Authorized Translations to be used for the ISO/IEC translations. We will update this page when more information about translations is available.

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.

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 web technologies.

Techniques for WCAG 2.0 has techniques for several different web 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.

WAI is also developing guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT).

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 developed:

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.