Our default standard for website accessibility audits is WCAG 2.1 AA (it’s whats in our 2025 client proposal templates), but this isn’t the latest version of the Web Content Accessibility Guidelines (WCAG) – 2.2 is.
If 2.2 is the latest version, why do we default to 2.1 AA?
- de facto standard used for most digital accessibility laws
- provides a comprehensive level of accessibility
- some clients lose steam when working through 2.1 AA issues
- if you plan for interval audits, it’s logical to start with 2.1 AA and continue with 2.2 AA on the next audit
- Easier to reach full conformance and receive certification
But we always encourage clients to go for a WCAG 2.2 AA audit if they feel so inclined. Here are some good reasons to choose WCAG 2.2 AA as your standard:
- Latest version of WCAG
- Enhances accessibility even further
- Confidence in meeting highest standard (at AA level)
- Keep pace with any laws that use “most recent version” of WCAG language
- Just six additional success criteria (at AA level)
- Accessibility is your priority project currently
- Marketability: you can showcase your advanced accessibility in an ACR (VPAT) or accessibility statement
Another consideration for European Accessibility Act (EAA) compliance is we’re waiting on EN 301 549 to be harmonized so that EN 301 549 conformance creates a presumption of conformity with the EAA.
A new version, v4.1.1 of EN 301 549, is expected to be completed in the second half of 2025 and it’s possible that it could be updated to include the WCAG 2.2 AA standard.
As of now, EN 301 549 and the technical requirements in the EAA still center around WCAG 2.1 AA, but we do like the idea of WCAG 2.2 AA conformance when responding to inquiries from market surveillance authorities.
As you can see, there are a lot of great reasons to zoom past WCAG 2.1 AA to WCAG 2.2 AA.
However, 2.1 still provides for an excellent level of accessibility and even despite the fact that we’ve seen a new rule updating Title II of the Americans with Disabilities Act (ADA) after 2.2 was released, the Department of Justice still elected to go with 2.1 as their technical standard for compliance with the new rule.
We saw the Department of Health and Human Services (HHS) double down on incorporation of 2.1 because they elected to mirror the new Title II rule in their update to Section 504.
And while their may be an update in Europe once v.4.1.1 of EN 301 549 is released (to harmonize with the European Accessibility Act), EN 301 549 still incorporates WCAG 2.1 AA.
So it really is a matter of preference. If your organization is ready for WCAG 2.2 AA, we say go for it. If you have multiple audits planned (e.g., one now and one in six months), we recommend starting with WCAG 2.1 AA and then using WCAG 2.2 AA for the second.
If you need help with an audit, we’d love to help. Contact us or send us a message below and we’ll be right with you.
