WCAG 2.2 and Future Mandate Updates

WCAG is not law. It never has been. It becomes enforceable only when a regulator or court adopts it as a measuring stick.

In the U.S., that usually happens indirectly. The U.S. Department of Justice enforces the ADA. The ADA does not name WCAG. The DOJ points to WCAG in guidance and settlement agreements. Courts follow.

That’s the pattern that turned WCAG 2.0 AA into the de facto standard around 2015. WCAG 2.1 AA followed the same path after its 2018 release. WCAG 2.2 is now in that same holding pattern.

Mandates don’t flip on publication day. They creep.

what changed from wcag 2.1 to 2.2

WCAG 2.2 added nine new success criteria. It did not remove any. Everything from 2.1 still applies.

The additions mostly target users with cognitive disabilities, low vision, and motor impairments. These are not edge cases. They’re common failure points in modern UI frameworks.

Here’s what matters in practice.

focus appearance gets stricter

WCAG 2.2 adds 2.4.11 (Focus Appearance) and 2.4.12 (Focus Appearance Enhanced).

Before 2.2, focus indicators just had to exist. A faint dotted outline technically passed. Now the indicator must meet size and contrast minimums relative to the focused component.

This hits custom components hard. Buttons styled to remove outlines. Card-based layouts with click handlers. JavaScript-heavy navigation.

Automated tools can partially detect failures here. Many can’t. Plaintiffs’ experts test it manually.

dragging alternatives are now required

Success Criterion 2.5.7 (Dragging Movements) requires that any function requiring dragging also has a non-dragging alternative.

Think sortable lists. Sliders. Map pins. File uploads.

This one is easy to miss and easy to fail. It shows up often in design systems built before 2023.

target size finally has teeth

WCAG 2.2 adds 2.5.8 (Target Size Minimum).

Interactive elements must be at least 24 by 24 CSS pixels unless an exception applies.

Mobile menus. Close icons. Pagination dots. Calendar controls. All common failures.

This criterion alone can force design changes, not just code fixes. That’s why some teams quietly ignore it.

Ignoring it doesn’t make it disappear.

consistent help is now measurable

2.2.6 (Consistent Help) requires that help mechanisms appear in the same relative order across pages.

That includes chat widgets, help links, and support icons.

Sites that inject support tools conditionally based on page type often fail this. So do sites that A/B test help placement without accessibility review.

accessible authentication targets cognitive load

WCAG 2.2 expands accessible authentication with 3.3.8 and 3.3.7.

CAPTCHAs that require memorization, puzzles, or time pressure are now harder to justify without alternatives.

This change lines up with recent DOJ settlements involving login barriers. Not coincidental.

what didn’t change but still causes lawsuits

WCAG 2.2 didn’t fix old habits. Most ADA lawsuits still hinge on basics.

Missing labels. Broken keyboard access. Inaccessible PDFs. Improper headings.

WCAG 2.2 adds requirements. It doesn’t excuse failure on older ones.

Some defendants point to 2.2 as “new” and argue lack of notice. Courts haven’t been receptive. If a barrier blocks access, version numbers don’t matter much.

how wcag versions show up in lawsuits today

Most complaints still cite WCAG 2.0 or 2.1 Level AA. That’s because plaintiffs mirror DOJ language.

But expert reports are changing. In 2024 filings in New York federal court, experts have started noting 2.2 failures alongside 2.1 failures. Not as the sole basis. As additional evidence.

That trend matters. It’s how standards migrate into enforcement.

a concrete example from an ecommerce site

In late 2023, a national apparel retailer rolled out a redesigned product grid. The design passed their existing WCAG 2.1 audit.

The problem was focus indicators. The grid used custom focus styles that met 2.1 but failed 2.2 contrast and thickness requirements.

A keyboard-only user complained publicly. No lawsuit yet. The internal accessibility team flagged the issue and updated the design tokens.

That fix cost design time, not legal fees. Waiting would have cost more.

That’s how 2.2 enters real workflows. Quietly.

future mandate updates don’t arrive as announcements

Businesses wait for official rules. That’s not how this works.

The DOJ announced in 2022 that it would issue formal web accessibility regulations under the ADA. As of now, those rules are still pending.

In the meantime, enforcement continues. Settlements continue. Courts continue.

When rules finally publish, they usually codify what’s already happening. Rarely the other way around.

title ii updates are closer than title iii

State and local governments fall under ADA Title II. Private businesses fall under Title III.

The DOJ has been clearer about updating Title II web accessibility rules. Those are expected to explicitly reference WCAG, likely 2.1 or later.

When that happens, pressure spills over. Vendors update contracts. Plaintiffs update templates. Expectations shift.

Private businesses feel it even if the rule technically doesn’t bind them.

international mandates move faster

Outside the U.S., WCAG adoption is more direct.

The European Accessibility Act references WCAG 2.1. Enforcement ramps up in 2025. Canada references WCAG explicitly. The UK does the same.

Multinational companies already align to the highest common denominator. That denominator is moving toward 2.2.

U.S.-only companies lag until sued. That’s been the pattern for a decade.

automation lag is a real limitation

Most automated testing tools lag WCAG updates by months or years.

Many tools still don’t fully test 2.1 criteria. 2.2 coverage is uneven.

That creates a problem. Teams rely on scores that don’t reflect current standards.

False confidence is worse than known gaps.

manual audits are getting stricter

Accessibility consultants are updating their checklists.

Audits that ignored target size now flag it. Focus appearance gets more attention. Dragging interactions are tested.

Audit scope creep increases cost. That’s the trade-off.

But audits that ignore 2.2 look dated already.

overlays don’t solve 2.2 failures

Overlay tools don’t change target size. They don’t fix dragging interactions. They don’t enforce focus indicator thickness.

Some vendors claim AI-driven fixes. In practice, these criteria require design decisions.

That limitation shows up fast under 2.2.

product teams feel the friction first

WCAG 2.2 pushes accessibility earlier in design.

Spacing. Component sizing. Interaction patterns.

Developers can’t patch these after launch without rework. Designers can’t ignore them without creating debt.

That friction is real. It slows releases. It increases review cycles.

The alternative is litigation risk.

what “future updates” usually look like

Based on past cycles, here’s the pattern without prediction language.

WCAG publishes an update.
Advocacy groups reference it.
Experts include it in reports.
Settlements quietly require it.
Courts accept it as reasonable.
Regulators codify it later.

This took about five years for WCAG 2.0. About three for 2.1. 2.2 is already moving faster.

documentation matters more than version numbers

When defendants lose, it’s rarely because they picked the wrong WCAG version.

It’s because they had no testing history, no remediation plan, and no proof of maintenance.

Teams that document decisions about 2.2, even if phased, fare better than teams that ignore it entirely.

Paper trails still matter.

cost pressure increases with each update

Each WCAG update adds scope. Scope adds cost.

Design remediation costs more than code remediation. Training costs more than fixes. Testing costs recur.

That’s the criticism. Accessibility standards expand without funding mandates.

Courts don’t offset that cost. They enforce access.

why waiting for “final rules” fails

Businesses wait for certainty. Accessibility enforcement thrives on ambiguity.

Plaintiffs don’t need regulations. They need barriers. WCAG provides a language to describe those barriers.

That language keeps updating whether laws do or not.

the real state of wcag 2.2 today

WCAG 2.2 is published. Experts use it. Tools lag it. Laws don’t name it yet. Enforcement inches toward it anyway.

Future mandate updates will likely formalize what’s already informally expected.

That’s not optimism. That’s how the last two updates worked.

End.