WCAG 2.1 vs WCAG 2.2: What Government Websites Actually Need to Meet

Why There Are Two Version Numbers in the Conversation

If you have started researching digital accessibility compliance for your government agency, you have probably encountered both WCAG 2.1 and WCAG 2.2. They sound similar. They largely overlap. But they are not the same, and the distinction matters for how you plan your compliance program.

Here is the straightforward explanation.

What the DOJ Actually Requires

The DOJ Title II final rule, published April 24, 2024, explicitly requires compliance with **WCAG 2.1 Level AA**. That is the legal standard. If your website and digital content meet WCAG 2.1 AA, you are compliant with the DOJ rule.

WCAG 2.2 is the successor standard, published by the World Wide Web Consortium in October 2023. It is more comprehensive. It adds new success criteria. But it is not what the DOJ rule requires — at least not yet.

What Is New in WCAG 2.2

WCAG 2.2 adds nine new success criteria beyond what 2.1 requires. The most practically significant ones for government websites are:

• **Focus Appearance (2.4.11 and 2.4.12)**: Keyboard focus indicators must meet minimum size and contrast requirements. Many government sites have invisible or nearly invisible focus rings that would fail this criterion.
• **Dragging Movements (2.5.7)**: Any functionality that requires dragging must have a single-pointer alternative. This affects map interfaces, sliders, and interactive diagrams common on government sites.
• **Target Size (2.5.8)**: Interactive targets (buttons, links) must be at least 24x24 CSS pixels. Small click targets are a common issue on older government sites.
• **Consistent Help (3.2.6)**: If a help mechanism appears on multiple pages, it must appear in the same location. This affects chatbots, accessibility help buttons, and contact links.
• **Redundant Entry (3.3.7)**: Users should not have to re-enter information they have already provided in the same session. This affects multi-step government forms.

WCAG 2.2 also removed one criterion from 2.1: 4.1.3 (Status Messages) remains, but 2.4.7 (Focus Visible) was superseded by the more rigorous Focus Appearance requirements.

The Strategic Recommendation

For government entities planning compliance programs today, our recommendation is straightforward: **target WCAG 2.2 AA, audit against WCAG 2.1 AA**.

Here is the reasoning:

The DOJ rule requires 2.1. But the DOJ has also signaled that it will update its technical standards over time as WCAG evolves. Building to 2.2 now means you will not need to retrofit when the rule updates. The additional criteria in 2.2 are also genuinely better for users — particularly users who navigate by keyboard or use assistive technology on mobile devices.

From a legal defensibility standpoint, demonstrating that you exceed the minimum standard is never a liability. It strengthens your good-faith compliance record.

What This Means for Your Audit

When you commission or run an accessibility audit, be clear about which standard you are auditing against. A WCAG 2.1 AA audit will not flag issues introduced in 2.2. If your audit tool or vendor only reports against 2.1, you may have a false sense of security about focus indicators and target sizes.

Automated tools like axe-core (which powers most professional accessibility scanners) support WCAG 2.2 criteria. When you run a scan, check whether the results are being filtered to 2.1 only or include 2.2 violations.

The Bottom Line

For legal compliance with the DOJ Title II rule: WCAG 2.1 Level AA is the requirement.

For building a genuinely accessible government website that will remain compliant as standards evolve: target WCAG 2.2 Level AA.

The gap between the two is not large — nine additional criteria, most of which address keyboard navigation and touch target sizing. Agencies that are already doing the hard work of auditing and remediating their sites should cover both versions simultaneously rather than treating 2.2 as a future problem.