Web Content Accessibility Guidelines (WCAG) 2 is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally.
The WCAG documents explain how to make web content more accessible to people with disabilities. Web “content” generally refers to the information in a web page or web application, including:
- natural information such as text, images, and sounds
- code or markup that defines structure, presentation, etc.
WCAG 2.0, 2.1, 2.2
The Web Content Accessibility Guidelines (WCAG) standards are stable and referenceable.
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 2.0 and 2.1 success criteria are exactly the same in 2.2, with two expections:
- 2.4.7 Focus Visible is changed from Level AA in WCAG 2.1 to Level A in WCAG 2.2.
- 4.1.1 Parsing is obsolete and removed from WCAG 2.2. More information is in the WCAG 2 FAQ.
There are additional success criteria in 2.1 that are not in 2.0. They are introduced in What’s New in WCAG 2.1.
The proposed new success criteria in 2.2 are introduced in What’s New in WCAG 2.2 Draft.
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.
Who WCAG is for
WCAG is for those who want a technical standard. It is not an introduction to accessibility. For links to introductory material, see “Where should I start?” in the FAQ.
WCAG is primarily intended for:
- Web content developers (page authors, site designers, etc.)
- Web authoring tool developers
- Web accessibility evaluation tool developers
- Others who want or need a standard for web accessibility, including for mobile accessibility
To meet the needs of others — including policy makers, managers, and researchers — there are many different WAI Resources.
What is in WCAG 2
The WCAG standards have 12-13 guidelines. The guidelines are organized under 4 principles: perceivable, operable, understandable, and robust.
For each guideline, there are testable success criteria. The success criteria are at three levels: A, AA, and AAA.
The success criteria are what determine “conformance” to WCAG. That is, in order to meet WCAG, the content needs to meet the success criteria. Details are in the Conformance section of WCAG.
For a short summary of the WCAG 2 guidelines, see WCAG 2.1 at a Glance.
Supporting material and supplemental guidance
The following resources help you understand and implement WCAG, and improve accessibility beyond WCAG:
- Quick Reference / How to Meet WCAG 2 / Checklist
- Understanding WCAG 2
- Techniques for WCAG 2
- Test Rules for WCAG 2
- Supplemental Guidance
Please read about these WCAG 2 resources from WCAG 2 Documents.
Authorized Translations and unofficial translations of WCAG 2 are listed in WCAG 2 Translations.
WCAG 2.0 is ISO/IEC 40500
WCAG 2.0 is approved as an ISO standard: ISO/IEC 40500:2012. ISO/IEC 40500 is exactly the same as the original WCAG 2.0, which is introduced above along with supporting resources.
Who develops WCAG
The WCAG technical documents are developed by the Accessibility Guidelines Working Group (AG WG) (formerly the Web Content Accessibility Guidelines Working Group), which is part of the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI).
Opportunities for contributing to WCAG and other WAI work are introduced in Participating in WAI.
WCAG 3 and More Information
WCAG is part of a series of accessibility guidelines, including the Authoring Tool Accessibility Guidelines (ATAG) and the User Agent Accessibility Guidelines (UAAG). Essential Components of Web Accessibility explains the relationship between the different guidelines.
See the WCAG 2 FAQ for more information on:
For information on the early draft of W3C Accessibility Guidelines 3.0 (formerly known as “Sliver”), see the WCAG 3 Introduction.Back to Top