What is being updated in September 2023?
We will update this section throughout September 2023 as we publish updates.
WCAG 2.1: On 21 September, we published an update to WCAG 2.1. The update:
- Adds informative notes to success criteria 4.1.1 Parsing. More information is under Why is success criteria 4.1.1 Parsing obsolete.
- Incorporates existing errata that are mostly minor wording corrections. The changes are listed in the WCAG 2.1 changelog.
You can link to the latest version or specific versions of WCAG 2.1:
- For the latest version of WCAG 2.1: https://www.w3.org/TR/WCAG21/
- The version published today, 21 September 2023: https://www.w3.org/TR/2023/REC-WCAG21-20230921/
- The version published 5 June 2018: https://www.w3.org/TR/2018/REC-WCAG21-20180605/
More info on linking is in Referencing and Linking to WAI Guidelines.
WCAG 2.2: We plan to provide an update on WCAG 2.2 publication by 29 September 2023.
Updates for success criteria 4.1.1 Parsing are listed under the next question.
How and why is success criteria 4.1.1 Parsing obsolete?
Success criteria 4.1.1 Parsing is obsolete. WCAG 2.2 indicates it as 4.1.1 Parsing (Obsolete and removed), along with a note.
WCAG 2.1 and WCAG 2.0 now include this note from a conformance perspective:
This Success Criterion should be considered as always satisfied for any content using HTML or XML.
That note is in:
- updated WCAG 2.1 that includes new notes under 4.1.1 Parsing and incorporates errata listed in the WCAG 2.1 changelog
- WCAG 2.0 errata
- Understanding documents
Parsing was included in WCAG 2.0 to ensure that browsers and assistive technologies could accurately parse markup and content. Since then, specifications (such as HTML) and browsers have improved how they handle parsing errors. Also, previously assistive technology did their own markup parsing. Now they rely on the browser.
With today’s technology, accessibility issues that would have failed 4.1.1, will fail other criteria, such as Info and Relationships (SC 1.3.1) or Name, Role, Value (SC 4.1.2). Therefore 4.1.1 is no longer needed for accessibility.
(Using tools that assess parsing errors and fixing parsing issues may still be useful — it’s just not required for accessibility.)
When was WCAG 2.0 published?
What about WCAG 2.1?
All requirements (“success criteria”) from 2.0 are included in 2.1. The 2.0 success criteria are exactly the same (verbatim, word-for-word) in 2.1.
The primary focus for WCAG 2.1 is additional accessibility requirements for:
There are 17 additional success criteria in 2.1 that are not in 2.0. They are introduced in [What’s New in WCAG 2.1].
Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. (This is often called “backwards compatible”.) A website that meets WCAG 2.1 should meet the requirements of policies that reference WCAG 2.0.
To put it another way: If you want to meet both WCAG 2.0 and WCAG 2.1, you can use the 2.1 resources and you don’t need to bother looking at 2.0.
WCAG 2.0 and WCAG 2.1 are both existing standards. WCAG 2.1 does not deprecate or supersede WCAG 2.0. W3C encourages you to use the most recent version of WCAG when developing or updating content or accessibility policies.
What about WCAG 2.2?
The Accessibility Guidelines Working Group (AG WG) is developing WCAG 2.2, and plans to publish the final standard in 2023. The structure and content of WCAG 2.2 is the same as 2.1 and 2.0. Version 2.2 will include new accessibility requirements, called “success criteria”.
For the latest information on dates and changes for WCAG 2.2, please see What’s New in WCAG 2.2 Working Draft.
AG WG will probably not do another version of WCAG 2, that is, not do WCAG 2.3. AG WG is working on WCAG 3.0.
What about WCAG 3.0? What about “Silver”?
WCAG 3.0 is the result of the project previously temporarily referred to as “Silver”.
Please see important up-to-date information in the WCAG 3 Introduction page.
WCAG 3.0 Name
WCAG 2 and WCAG 3 have different names.
The new standard is currently referred to as “W3C Accessibility Guidelines (WCAG) 3.0”. This name was chosen because of wide-spread familiarity with the “WCAG” acronym, and to encompass the broader scope beyond “content”.
How Can I Get Updates?
We will announce when more information is available on WCAG 2.2 and WCAG 3.0. To get announcements of updated drafts for review in e-mail, tweets, and RSS, see Get WAI News.
Does WCAG 2 address mobile accessibility?
Yes. See the [Mobile Accessibility at W3C] page.
Does VPAT 2.1 include WCAG 2.1?
No. Voluntary Product Accessibility Template (VPAT) 2.1 includes information from WCAG 2.0. VPAT 2.1 does not include information from WCAG 2.1. (VPAT is not developed by W3C.)
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 Examples of Web Accessibility.
To learn about web accessibility principles and guidelines, see [Accessibility Principles].
To learn about WCAG 2 specifically, start with the WCAG Overview. It provides an important foundation for understanding the different WCAG 2 documents, and points to several resources for using WCAG 2.
How to Meet WCAG 2: A customizable quick reference is the primary resource for developers using WCAG 2.
What are the different WCAG 2 documents?
To learn how the different WCAG 2 technical documents are related and linked, see [The WCAG 2 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, and since those details don’t fit well in a technical standard, they are in the supporting documents.
Thus with WCAG 2, there are extensive supporting materials, which are advisory documents. The WCAG 2 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 document.
The techniques are informative; that means they are not required. The basis for determining conformance to WCAG 2 is the success criteria from the WCAG 2 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.1.
What would be the negative consequences of allowing only W3C’s published techniques to be used for conformance to WCAG 2?
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 success criteria. The basis for determining conformance to WCAG 2 is the success criteria from the WCAG 2 standard — not the techniques. W3C’s Techniques for WCAG 2 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:
It would prevent the use of new technologies (for example, HTML5 and WAI-ARIA) while the technologies and relevant sufficient techniques are being developed, which is usually more than a year.
It often takes several years for technologies to be developed and finalized. Once a technology is stable, it usually takes several months for the WCAG Working Group to develop techniques, test them with user agents and assistive technologies, make them available for public review, revise them as needed, and formally publish them.
W3C’s Techniques for WCAG 2 is not comprehensive and may not cover newer technologies and situations. There may be techniques that are sufficient to meet a given success criteria, but that are not yet included in W3C’s published document.
W3C’s published sufficient techniques may not always be the best techniques in a specific circumstance.
It is not always possible to use the W3C’s published sufficient techniques — for example, because of the way the content is designed — and there are other ways to meet the success criteria.
It would prevent the use of new techniques and best practices until W3C published them.
Therefore, W3C’s published techniques should not be required as the only way to meet WCAG 2 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.1.
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).
For supporting resources that provide practical advice for meeting ISO/IEC 40500 (which is WCAG 2.0), see the WCAG Overview.
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.
Does W3C plan to send WCAG 2.1 or WCAG 2.2 to ISO for endorsement?
W3C does not plan to send WCAG 2.1 to ISO for endorsement and would not support that action, because WCAG 2.2 is expected to be finalized within 2022 and will be an improvement in several respects.
W3C expects to send WCAG 2.2 to ISO for endorsement, and has started that process by notifying the ISO/IEC Joint Technical Committee 1 (JTC 1) of our intention to do so.
Is WCAG 2 available in other languages?
Yes. Authorized Translations and unofficial translations of the technical documents WCAG 2, Techniques for WCAG 2, and Understanding WCAG 2 are listed in [WCAG 2 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].
WCAG 2 is designed to apply to a broad range of web technologies.
Techniques for WCAG 2 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. 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 to Non-Web Information and Communications Technologies (WCAG2ICT).
Where can I find answers to more of my questions?
First, look through the documents on the W3C WAI website.
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:
- Search the WAI IG list archives to see if your question has already been addressed sufficiently.
- Join the self-subscription list and post an appropriate question. Please read the Using the WAI IG mailing list section of the WAI IG page.
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 email@example.com and we will integrate answers into this page and other documents as we are able.Back to Top