2026-05-17 · 5 min read

WCAG 2.1 vs WCAG 2.2: What the Difference Means for Your Government Website

# WCAG 2.1 vs WCAG 2.2: What the Difference Means for Your Government Website

The question comes up often in conversations with government IT directors: does the DOJ Title II Final Rule require WCAG 2.1 or WCAG 2.2? And if agencies are already working toward compliance, do they need to update their target standard?

The short answer is: the rule requires WCAG 2.1 Level AA. WCAG 2.2 is not mandated. But the longer answer matters for agencies that want to build a compliance program that holds up through the next update cycle — and for IT directors who will need to explain the difference to their legal counsel and procurement officers.

What the rule actually requires

The DOJ Title II Final Rule — the regulation that establishes binding web accessibility requirements for state and local government websites — specifies WCAG 2.1 Level AA as the required standard. This is the version published by the World Wide Web Consortium in June 2018. The compliance deadline for jurisdictions with populations of 50,000 or more is April 26, 2027.

WCAG 2.2 is not required by the current rule. Agencies that conform to WCAG 2.1 Level AA are in compliance with the rule, even if their sites do not meet the additional criteria introduced in 2.2.

What changed in WCAG 2.2

The W3C published WCAG 2.2 in October 2023. It is backward compatible with 2.1 — all 50 success criteria from WCAG 2.1 Level A and AA are present in 2.2, except one: Success Criterion 4.1.1 (Parsing) was removed because modern browsers have matured to the point where the underlying problem it addressed no longer meaningfully affects assistive technology behavior.

WCAG 2.2 adds 9 new success criteria. Six of them are at Level A or AA, meaning they would be mandatory if the DOJ rule referenced 2.2. Three are at Level AAA, which is typically treated as aspirational.

The six new A/AA criteria in WCAG 2.2 are worth knowing, because auditors increasingly flag them even when the contract is for WCAG 2.1 compliance, and because some of them address failure patterns that are common on government sites:

2.4.11 Focus Appearance (AA) — Requires that keyboard focus indicators meet minimum size and contrast requirements. Many government sites have focus indicators that technically exist but are so faint they provide no meaningful guidance to keyboard-only users. This criterion formalizes what good practice already required.

2.4.12 Focus Not Obscured (AA) — Requires that the component receiving keyboard focus is not entirely hidden by sticky headers, cookie banners, or other overlapping content. This is a common failure on government sites with persistent navigation bars that scroll over content.

2.4.13 Focus Appearance (Minimum Size, AAA) — Extends 2.4.11 with stricter dimensional requirements. Level AAA, so not mandatory under any current rule.

2.5.7 Dragging Movements (AA) — Requires that any functionality using dragging can also be operated with a single pointer without dragging. This affects interactive maps, sliders, and drag-and-drop interfaces.

2.5.8 Target Size (Minimum) (AA) — Requires that touch targets are at least 24×24 CSS pixels unless spacing compensates. Addresses small buttons and links on mobile government sites.

3.2.6 Consistent Help (A) — Requires that help mechanisms (phone numbers, chat, self-help pages) appear in a consistent location across pages if they appear at all.

3.3.7 Redundant Entry (A) — Requires that information previously provided in a process is auto-populated or available for selection. Affects multi-step forms on government sites.

3.3.8 Accessible Authentication (Minimum) (AA) — Requires that authentication processes don't rely on cognitive function tests (like solving puzzles or transcribing text) unless an alternative is provided.

3.3.9 Accessible Authentication (Enhanced) (AAA) — Stricter version of 3.3.8.

Why this matters for your compliance planning

Conforming to WCAG 2.1 is the legal target. If your audit scope is WCAG 2.1 Level AA and you achieve it, you satisfy the rule. Your VPAT and accessibility statement should reference WCAG 2.1, not 2.2.

The DOJ may update the rule to reference 2.2. The regulatory process for updating the Title II rule takes years. When the next update does occur, it will almost certainly reference WCAG 2.2 (or whatever version is current at that time). Agencies that build toward WCAG 2.1 conformance with awareness of the 2.2 additions will be better positioned when the requirement changes.

Focus Appearance (2.4.11) is already expected by auditors. The focus indicator requirements in WCAG 2.2 formalize what has long been considered good practice. Professional auditors frequently note focus indicator failures as separate findings in WCAG 2.1 reports, often under 2.4.7 (Focus Visible), even when the strict 2.4.11 threshold doesn't apply. Remediating your focus indicators now satisfies both.

Parsing (4.1.1) is gone from 2.2. If you have legacy automated scan findings flagging duplicate ID issues and similar parsing errors, know that this criterion no longer exists in 2.2. For compliance with the current rule (2.1), it remains in scope — but it's a declining issue as browser handling of malformed markup has improved.

What smart agencies are doing now

Agencies that are approaching this strategically are:

1. Targeting WCAG 2.1 Level AA as their compliance milestone for April 2027, because that is what the rule requires. 2. Noting the new 2.2 AA criteria during remediation planning, so that development tickets address 2.4.11 focus appearance and 2.5.8 target size in the same sprint rather than in a second round when the rule eventually updates. 3. Writing their accessibility statements to reference WCAG 2.1, with a note that the agency is working toward future alignment with WCAG 2.2 where applicable. This is accurate and demonstrates forward-looking compliance intent without overstating current conformance. 4. Choosing auditors who understand both versions. An audit firm that reports only against WCAG 2.1 without noting relevant 2.2 criteria is giving you a compliance snapshot that will age poorly.

Getting started

Before commissioning an audit, a 10-minute self-assessment using WAVE and a keyboard gives you a realistic baseline for where your site stands on the most common WCAG 2.1 failures. The quick self-assessment guide covers the tools and checklist for exactly that.

If your agency is ready to understand the full scope of your compliance gap — both WCAG 2.1 failures for the April 2027 deadline and WCAG 2.2 criteria that will matter in the next regulatory cycle — the Parallax WCAG Audit reports findings against both standards. The audit deliverable notes each finding's status under 2.1 and 2.2, so your remediation roadmap is durable across the standards update.

---

*Morton Technology Consulting LLC, Tallahassee, FL. Questions about WCAG 2.1, WCAG 2.2, or Title II compliance: [email protected].*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →