Which version of the Web Content Accessibility Guidelines (WCAG) should you use for your audit or VPAT/ACR?
While most organizations choose WCAG 2.1 AA, there can be compelling reasons to consider versions 2.0 or 2.2 based on your situation. Let’s go over each version to help you make this important decision.
Note: We highly recommend defaulting to conformance level AA no matter which version you go with. A only provides for foundational accessibility and AAA has extremely strict requirements.
Table of Contents
WCAG 2.0: The Classic Standard
WCAG 2.0 represents the classic accessibility standard. Published in 2008, this version includes 38 success criteria which revolve around desktop usage.
The WCAG 2.0 AA standard is comprised of 38 success criteria or requirements. While it may seem dated, WCAG 2.0 remains relevant for certain situations, particularly when dealing with desktop-only applications or when seeking formal documentation of conformance.
If your website or other digital asset is nonconformant with some success criteria in 2.1 or 2.2, then moving backwards to 2.0 can make more sense if documentation is a priority.
WCAG 2.1: The Prevailing Choice
WCAG 2.1, published in 2018, builds upon 2.0 AA by adding 12 new success criteria, bringing the total to 50. These additions include mobile accessibility considerations, which make sense given the widespread usage of mobile devices in the decade since 2.0 was released. 2.1 has become the de facto standard for several reasons:
- It’s been incorporated into multiple laws
- It’s commonly required in the private sector
- It provides comprehensive accessibility coverage
- It effectively addresses both desktop and mobile experiences
WCAG 2.2: The Current Standard
Released in 2023, WCAG 2.2 represents the most current version of the guidelines. It introduces six additional success criteria (with one obsolete criterion removed from 2.1), bringing the total to 55.
While this version offers the most comprehensive coverage, it’s worth noting that 2.1 AA conformance is already a weighty project for most organizations. Adding even more success criteria – and a few are more complex – can push digital teams to a point of feeling overwhelmed.
Plus, again, 2.2 isn’t dominant in the marketplace or legal landscape – 2.1 is.
Making Your Choice: Factors to Consider
The “default” recommendation is typically WCAG 2.1 AA, as it strikes an excellent balance between comprehensive accessibility and meeting market (and compliance) demand. However, several factors might influence your decision:
- If your application is desktop-only, WCAG 2.0 can be sufficient.
- If you need formal certification or documentation, starting with 2.0 might be strategically advantageous.
- If you want to future-proof your accessibility efforts, WCAG 2.2 is definitely worth considering.
A practical approach many organizations take is to start with WCAG 2.1 AA conformance and then gradually work toward WCAG 2.2 as part of their long-term accessibility strategy. This phased approach allows teams to manage the workload more effectively while still maintaining a strong commitment to accessibility.
While WCAG 2.1 AA remains, by far, the preferred choice, the right version for your organization will depend on your unique situation.
If you need help with an audit or even consultation in deciding what direction your organization should go, we’re happy to help.
We reply quickly to emails and offer very fast turnarounds for services, including audits and VPAT services.
