📋 Updated for 2026

WCAG 2.2 Compliance Checklist: All 9 New Success Criteria

WCAG 2.2 is the current W3C standard with 86 success criteria — 9 new since WCAG 2.1. Courts are citing it in ADA cases, and the European Accessibility Act is adopting it through EN 301 549. This interactive checklist covers every new criterion with implementation guidance.

Compliapoint works on WordPress (including WooCommerce) and Shopify sites.

86Total success criteria in WCAG 2.2
9New criteria added
6New Level A and AA requirements
Oct 2023W3C Recommendation date

WCAG 2.2 at a Glance

WCAG 2.2 was published as a W3C Recommendation on October 5, 2023. It is fully backward-compatible with WCAG 2.1 — all existing criteria remain (except 4.1.1 Parsing, which was removed as obsolete). The 9 new criteria target three underserved user groups: people with cognitive and learning disabilities, people with low vision, and people with motor impairments using mobile or touch devices.

For organizations already meeting WCAG 2.1 AA, achieving WCAG 2.2 AA requires addressing just 6 additional criteria. For everyone else, WCAG 2.2 AA is the target to aim for — and W3C states that a site conforming to it also conforms to 2.1 AA.

⚡ Why WCAG 2.2 Matters Now

The DOJ's 2024 ADA Title II rule specifies WCAG 2.1 AA as the minimum. The European Accessibility Act (effective June 2025) is expected to adopt WCAG 2.2 through EN 301 549. Organizations that implement WCAG 2.2 AA now have the strongest possible compliance posture for both current and upcoming regulations.

In Deque’s 2021 study of more than 2,000 audits, automated testing found 57 percent of issues by volume; a person found the rest. Many of the new criteria — particularly those addressing cognitive accessibility and focus management — require human evaluation.

Interactive WCAG 2.2 New Criteria Checklist

Click any criterion to expand implementation details. Check items off as you address them. Your progress is tracked below.

0 of 9 new criteria addressed
Level A — Minimum Conformance
3.2.6 Consistent Help
Help mechanisms must appear in the same order across pages
If your site provides help features (contact info, chat, FAQ links, help pages), they must appear in the same order relative to the rest of the page on every page where they're offered.
+

Who This Helps

People with cognitive disabilities who rely on consistent, predictable interfaces. Users who need help completing tasks but struggle to locate support when it moves between pages. Also benefits all users through improved UX consistency.

How to Implement

Place help links (contact, chat, FAQ) in a consistent location — typically the footer or a fixed-position chat widget. Ensure the help mechanism appears in the same relative order within your page template on every page. If using a floating chat bubble, keep it in the same corner across all pages.

3.3.7 Redundant Entry
Don't ask users to re-enter information already provided
Information the user already entered, or was given, in the same process must be auto-populated or available for selection, not re-typed. The exceptions: re-entering it is essential, it is needed for security, or the earlier information is no longer valid.
+

Who This Helps

People with cognitive disabilities, memory impairments, and executive function limitations. Users who find form completion time-consuming or error-prone. Benefits everyone by reducing friction in multi-step processes like checkout and applications.

How to Implement

In multi-step forms, auto-populate fields from previous steps (e.g., shipping address → billing address). Provide "same as above" checkboxes. Store session data to persist across steps. For checkout flows, pre-fill known customer data. Review all multi-page processes for redundant fields.

Level AA — Legal Standard Target
2.4.11 Focus Not Obscured (Minimum)
Focused elements must be at least partially visible
When an element receives keyboard focus, it must not be completely hidden behind sticky headers, modal overlays, cookie banners, or other author-created content.
+

Who This Helps

Sighted keyboard users and people with low vision who rely on focus indicators. When focus lands behind a sticky header or chat widget, users cannot see where they are on the page and may think their system has frozen.

How to Implement

Add scroll-padding-top equal to sticky header height. Ensure cookie banners and chat widgets don't overlap focused content. Use scroll-margin on anchor targets. Test by tabbing through every page with all sticky elements visible. Banners opened by the user are excluded from this requirement.

2.5.7 Dragging Movements
Every dragging operation must have a single-pointer alternative
Any action that requires dragging (e.g., sliders, sortable lists, map panning) must also be operable with a single click, tap, or keyboard action.
+

Who This Helps

People with motor impairments who cannot perform drag-and-drop gestures, including users of switch devices, mouth sticks, eye-tracking systems, and those with tremors or limited dexterity. Also benefits mobile users in one-handed or accessibility modes.

How to Implement

Provide click-to-select and click-to-place as an alternative to drag. For sliders, add increment/decrement buttons. For sortable lists, add "Move Up" / "Move Down" controls. For maps, provide zoom buttons and directional pads alongside pinch-and-drag. Ensure all alternatives are keyboard-accessible.

2.5.8 Target Size (Minimum)
Touch/click targets must be at least 24×24 CSS pixels
Interactive elements must have a minimum size of 24×24 CSS pixels, or have sufficient spacing so their target area doesn't overlap with adjacent targets. Inline links in text are exempt.
+

Who This Helps

People with motor impairments, tremors, or limited fine-motor control. Mobile users operating devices one-handed or in motion. Older adults with reduced precision. Users of styluses, mouth sticks, or head pointers.

How to Implement

Set minimum min-height and min-width of 24px on buttons, links in navigation, form controls, and icon buttons. For smaller elements, ensure 24px of non-overlapping space by adding padding or margin. Audit icon buttons — they're the most common violators. Inline text links are exempt.

3.3.8 Accessible Authentication (Minimum)
No cognitive function test required for login
Authentication must not require memorization, transcription, or solving puzzles, unless there is another way to sign in, a mechanism that helps (such as a password manager filling the field), or the test is only to recognize objects or content the user supplied.
+

Who This Helps

People with cognitive, memory, and learning disabilities. Users who struggle with CAPTCHAs, complex passwords, or multi-step verification requiring recall. Also benefits users with anxiety or processing disorders.

How to Implement

Support password managers (don't block paste in login fields). Offer email/SMS magic links, OAuth/SSO sign-in, biometric authentication, or passkeys. If CAPTCHAs are required, provide object recognition alternatives — not text transcription. Allow copy-paste of verification codes.

Level AAA — Enhanced (Recommended)
2.4.12 Focus Not Obscured (Enhanced)
Focused elements must be fully visible — no partial obstruction
A stricter version of 2.4.11: when an element receives keyboard focus, no part of it or its focus indicator may be hidden by author-created content.
+

Who This Helps

The same users as 2.4.11, but this enhanced version eliminates even partial obstruction. Particularly important for users with low vision who need to see the entire focused element and its indicator.

How to Implement

All the same techniques as 2.4.11, plus ensure that sticky elements and overlays leave enough clearance for the full focus indicator (typically 2-3px outline). Test with visible focus indicators at every scroll position. Consider reducing sticky header height or making it collapsible.

2.4.13 Focus Appearance
Focus indicators must meet minimum size and contrast
The keyboard focus indicator must be at least as large as a 2 CSS pixel perimeter of the component and have a contrast ratio of at least 3:1 between focused and unfocused states.
+

Who This Helps

People with low vision who cannot see thin or low-contrast focus indicators. Keyboard-only users who need clear visual confirmation of their position. Older adults with age-related vision changes.

How to Implement

Use outline: 2px solid with a color that has ≥3:1 contrast against adjacent colors. Avoid outline: none without replacement. For dark backgrounds, use light outlines; for light backgrounds, use dark outlines. Test with the browser's default focus indicator disabled. A 2px solid outline in a contrasting color passes in most cases.

3.3.9 Accessible Authentication (Enhanced)
No cognitive test for login — stricter than 3.3.8
A stricter version of 3.3.8: only two exceptions are allowed (alternative method and assistive mechanism). Object recognition and personal content exceptions are removed.
+

Who This Helps

The same users as 3.3.8, with additional protection for people who struggle with image-based recognition tests (e.g., "click all traffic lights"). Particularly benefits users with visual processing disorders.

How to Implement

All the same techniques as 3.3.8, but also eliminate image recognition CAPTCHAs. Use invisible reCAPTCHA, honeypot fields, or rate limiting instead of visual challenges. Support passkeys and WebAuthn for the most accessible authentication possible.

🗑️ Removed: 4.1.1 Parsing

WCAG 2.2 removes Success Criterion 4.1.1 Parsing (previously Level A). Modern browsers and assistive technologies now handle HTML parsing robustly, making this criterion obsolete. Focus on semantic correctness and proper ARIA usage instead of strict parsing validation.

Implementation Priority Guide

Not all criteria carry equal risk. Here's the recommended order based on user impact and implementation effort.

🔴 Fix First

2.5.8 Target Size (Minimum) — Easy to audit and easy to fix, and new in WCAG 2.2, so an older audit will not have checked it.

3.3.7 Redundant Entry — Checkout and sign-up flows are where it shows up. A multi-step form that asks again for something already entered fails it, unless one of the exceptions applies.

🟡 Fix Next — High User Impact

2.4.11 Focus Not Obscured — Sticky headers hiding focused elements is extremely common and blocks keyboard-only users.

3.3.8 Accessible Authentication — Blocking paste in login fields, or a CAPTCHA that makes people retype distorted text with no other way through, locks out users with cognitive disabilities.

🔵 Address Next — Important for Full Compliance

2.5.7 Dragging Movements — Only affects sites with drag-and-drop interfaces, sliders, or interactive maps.

3.2.6 Consistent Help — Low implementation effort. Audit help mechanism placement across pages for consistency.

💡 Already WCAG 2.1 AA Compliant?

You only need to address the 6 new Level A and AA criteria listed above. The 3 Level AAA criteria (Focus Not Obscured Enhanced, Focus Appearance, Accessible Authentication Enhanced) are recommended but not required for legal compliance.

Frequently Asked Questions

What's new in WCAG 2.2?
WCAG 2.2 adds 9 new success criteria targeting users with cognitive disabilities, low vision, and motor impairments. It removes one criterion (4.1.1 Parsing). The total is now 86 criteria across levels A, AA, and AAA. For Level AA compliance (the legal target), you need to meet 6 new criteria beyond WCAG 2.1 AA.
Is WCAG 2.2 required by law?
The DOJ's 2024 ADA Title II rule references WCAG 2.1 AA. However, WCAG 2.2 is backward-compatible with it. The European Accessibility Act (EAA, effective June 2025) is expected to adopt WCAG 2.2 through EN 301 549. Implementing 2.2 now provides the strongest compliance posture for current and emerging regulations.
Is WCAG 2.2 backward compatible with 2.1?
Yes, fully. WCAG 2.2 adds criteria but doesn't remove any from 2.1 (except 4.1.1 Parsing, now obsolete). If your site conforms to WCAG 2.2 at a given level, it also conforms to 2.1 and 2.0 at the same level or higher.
How long does WCAG 2.2 compliance take?
From a WCAG 2.1 AA baseline there are 6 new Level A and AA criteria to address. Compliapoint's standard delivery is 7–10 business days from the day work starts, or 1–3 business days on rush, for urgent situations like active demand letters.
Can automated tools check WCAG 2.2?
Only partially. In Deque’s 2021 study of more than 2,000 audits, automated testing found 57 percent of issues by volume. Many new criteria (Focus Not Obscured, Accessible Authentication, Consistent Help, Redundant Entry) require human testing. Automated scans are a starting point, not a compliance solution. Compliapoint combines automated scanning with comprehensive manual expert evaluation.
Can an overlay widget make my site WCAG 2.2 compliant?
No. Overlay widgets cannot fix many WCAG 2.2 criteria, particularly Focus Not Obscured, Target Size, Redundant Entry, Consistent Help, and Accessible Authentication — these all require source-code-level changes. In 2025, 24.9% of the ADA website lawsuits EcomBack counted were filed against sites that already had a widget installed, and the FTC ordered accessiBe to pay $1 million in 2025 over its compliance claims.

Get Your WCAG 2.2 Compliance Audit

We evaluate your site against WCAG 2.2 — then fix what's broken in your actual source code. One-time cost, and the fixes stay in your code. WordPress and Shopify are the two platforms we work in exclusively, so we already know where their failures come from.

Start Your Assessment

Related: Title II Deadline · Overlay vs. Remediation