PUBLIC-SERVICE WEBSITES. BUILT FOR PEOPLE.A service by HiperFusion
HiperFusionCIVIC ACCESS

WCAG 2.1 vs. 2.2 AA for public-service websites

Understand the newer WCAG 2.2 AA criteria and how they relate to the WCAG 2.1 AA standard named in US government web accessibility guidance.

By HiperFusion · Reviewed September 13, 2026

Is WCAG 2.2 new?

WCAG 2.2 first became a W3C Recommendation on October 5, 2023. It builds on WCAG 2.1, adding requirements that address practical barriers in focus visibility, pointer interaction, help, forms, and authentication. It is a newer technical standard, not a new accessibility overlay or an automated certification.

What changes at Level A and AA?

The six added A/AA criteria concern keyboard focus not being entirely hidden by author-created content; alternatives to dragging; minimum pointer target size or qualifying spacing; consistent placement of repeated help; avoiding unnecessary repeated entry; and authentication that does not depend on a cognitive-function test without a qualifying alternative or assistance. WCAG 2.2 also removes the obsolete Parsing criterion. Several additional new criteria are AAA and are outside an AA target.

What does this mean for a redesign?

Check sticky banners and footers against focused controls. Make small icon buttons easier to select. Provide buttons or another simple pointer alternative for drag interactions. Keep help in consistent locations. Reuse information already entered where required, and support password managers and paste in authentication. Whether a criterion applies depends on the actual features in scope.

Which version applies to government requirements?

The US Department of Justice's state and local government web and mobile accessibility rule names WCAG 2.1 Level AA. A WCAG 2.2 design target does not by itself change an organization's legal obligations. Consult current official guidance for deadlines, coverage, and exceptions, and obtain legal advice about your circumstances. HiperFusion provides technical services, not legal advice.

How we scope testing

An engagement should name the target standard, pages and workflows, document scope, third-party dependencies, testing methods, and retest evidence. For this marketing website, our design target is WCAG 2.2 AA. Our accessibility statement describes evaluation limits; we do not claim that automated checks establish full conformance.

Official references

HiperFusion provides technical accessibility services and does not provide legal advice. Explore our accessibility audit service or read more planning resources.

A CLEAR FIRST STEP

Let’s make your website
work for more people.

Tell us what you have, where you’re getting stuck, and what your team needs next.

Request an accessibility review Schedule a 20-Minute Review (opens Zoho Bookings in a new tab)

A practical conversation. A clearly scoped next step.