WCAG 2.2 AA — 3 Must-Know Criteria for ADA Compliance (2026) | AccessiTool

WCAG 2.2 AA — 3 Must-Know Criteria for 2026 Compliance

⚡ WCAG 2.2 AA — 3 New Requirements You MUST Know for 2026

  • 2.4.11 — Focus Appearance (AA) — Focus indicator must be visible with 3:1 contrast
  • 2.5.8 — Target Size (AA) — Touch targets minimum 24x24px
  • 3.3.8 — Accessible Authentication (AA) — No CAPTCHA or memory tests

Test your website against WCAG 2.2 AA →

📢 WCAG 2.2 Update — 2026

WCAG 2.2 was officially published on October 5, 2023 as a W3C Recommendation. In 2026, it remains the latest WCAG version and is increasingly referenced in accessibility lawsuits and compliance audits.

Current WCAG version 2026: WCAG 2.2 — with 9 new success criteria since 2.1.

🎯 What is WCAG 2.2?

WCAG 2.2 adds 9 new success criteria to WCAG 2.1, focusing on mobile accessibility, cognitive accessibility, and user experience improvements.

Important: WCAG 2.2 is backward compatible with WCAG 2.1 and 2.0. If you're compliant with WCAG 2.1, you're mostly there — but you may need to address the new criteria.

WCAG 2.2 New Success Criteria — Quick Summary

Success CriterionLevelWhat It Means
2.4.11 — Focus AppearanceAAFocus indicator must be visible with 3:1 contrast
2.4.12 — Focus Not ObscuredAAFocus indicator must not be hidden by other elements
2.4.13 — Focus Not Obscured (Enhanced)AAAFocus indicator must not be hidden at all
2.5.7 — Dragging MovementsAADragging functions must have a simple pointer alternative
2.5.8 — Target SizeAATouch targets minimum 24x24px (with exceptions)
3.2.6 — Consistent HelpAHelp mechanisms must be in consistent locations
3.3.7 — Redundant EntryADon't ask users to re-enter information
3.3.8 — Accessible AuthenticationAAAuthentication must not require memory or transcription
3.3.9 — Accessible Authentication (Enhanced)AAANo cognitive function tests in authentication

Source: W3C WCAG 2.2 Official Specification

✅ Test Your Website Against WCAG 2.2

Use our free ADA checker to see if your website meets the latest standards.

Run Free WCAG Scan →

WCAG 2.2 vs WCAG 2.1 — What Changed?

FeatureWCAG 2.1WCAG 2.2
Total success criteria78 criteria87 criteria (+9)
Level A criteria30 criteria33 criteria (+3)
Level AA criteria20 criteria23 criteria (+3)
Level AAA criteria28 criteria31 criteria (+3)

WCAG 2.1 vs WCAG 2.2 — What's Different?

WCAG 2.2 adds 9 new success criteria on top of WCAG 2.1. No existing criteria have been removed or changed — it's purely additive.

❌ WCAG 2.1 (2018)

  • • Focus indicators not required
  • • 44x44 target size recommended
  • • No authentication requirements
  • • Dragging allowed without alternatives

✅ WCAG 2.2 (2023)

  • • Focus Appearance required (AA)
  • • 24x24 target size required (AA)
  • • Accessible Authentication (AA)
  • • Dragging alternatives required (AA)

The 9 New WCAG 2.2 Success Criteria — Complete List

2.4.11 — Focus Appearance (Level AA) AA

What it means: The keyboard focus indicator must be highly visible. The minimum area of the focus indicator must be at least the area of a 2px thick perimeter of the focused control, or at least 2px thick on the shortest side.

Why it matters: Users with low vision need to clearly see where keyboard focus is. WCAG 2.1 only required a visible focus indicator — 2.2 adds specific size requirements.

/* Good focus indicator meeting 2.4.11 */
:focus {
    outline: 3px solid #3b82f6;
    outline-offset: 2px;
}

/* Or a background color change + border */
:focus {
    background-color: #e0e0e0;
    border: 2px solid #000;
}

2.4.12 — Focus Not Obscured (Minimum) (Level AA) AA

What it means: When an element receives keyboard focus, it must not be completely hidden by other content (like sticky headers or modals).

Why it matters: Sticky headers, chat widgets, and cookie banners often obscure focused elements. Users can't see where they are.

How to test: Tab through your site. Can you always see the focused element? If a sticky header hides it, that's a violation.

/* Fix: Ensure sticky headers don't hide focus */
:target {
    scroll-margin-top: 80px; /* Adjust based on header height */
}

2.4.13 — Focus Not Obscured (Enhanced) (Level AAA) AAA

What it means: An even stricter version of 2.4.12. The focused element must not be obscured at all — not even partially.

Why it matters: For users with cognitive disabilities, even partial obstruction can be disorienting.

2.5.7 — Dragging Movements (Level AA) AA

What it means: Any functionality that requires dragging (like sliders or drag-and-drop) must also have a single-pointer alternative (like tapping up/down buttons).

Why it matters: Users with motor impairments may not be able to perform precise dragging movements.

<!-- Good: Provide both drag AND buttons -->
<div class="slider">
    <button onclick="decrease()">-</button>
    <div class="drag-area" draggable="true"></div>
    <button onclick="increase()">+</button>
</div>

2.5.8 — Target Size (Minimum) (Level AA) AA

What it means: Touch targets (buttons, links) must be at least 24x24 CSS pixels.

Why it matters: Small buttons are hard to tap on mobile devices. This is now a Level AA requirement.

Exception: Inline links, sentence links, and targets in a sentence can be smaller if there's enough spacing.

/* Ensure buttons are at least 24x24px */
.button {
    min-width: 24px;
    min-height: 24px;
    padding: 8px;
}

/* For mobile, 44x44 is still recommended */
@media (max-width: 768px) {
    .button {
        min-width: 44px;
        min-height: 44px;
    }
}

3.2.6 — Consistent Help (Level A) A

What it means: If your website provides help mechanisms (contact info, chat, help desk), they must be in the same relative order across all pages.

3.3.7 — Redundant Entry (Level A) A

What it means: Information that users previously entered must be auto-populated or easily selectable, unless re-entering is essential.

3.3.8 — Accessible Authentication (Minimum) (Level AA) AA

What it means: Authentication processes (login, password reset) must not rely on cognitive function tests like remembering passwords or solving puzzles — unless there's an alternative.

<!-- Good: Provide multiple login options -->
<button>Log in with email link (no password)</button>
<button>Log in with password</button>
<button>Log in with Google</button>

3.3.9 — Accessible Authentication (Enhanced) (Level AAA) AAA

What it means: An even stricter version of 3.3.8. No cognitive function tests at all.

🔍 Is Your Website WCAG 2.2 Ready?

Run a free accessibility scan to check against the latest standards.

Test Your Website →

Developer Checklist — WCAG 2.2 Compliance

✅ Focus Appearance (2.4.11)

  • ☐ Focus indicator has at least 3:1 contrast against adjacent colors
  • ☐ Focus indicator is at least as large as a 1px thick border
  • ☐ Focus indicator is visible on all interactive elements

✅ Target Size (2.5.8)

  • ☐ All touch targets are at least 24x24 CSS pixels
  • ☐ Exceptions: inline links, essential targets, target spacing
  • ☐ Test with mobile devices and touch screens

✅ Accessible Authentication (3.3.8)

  • ☐ Authentication doesn't require solving puzzles or transcription
  • ☐ CAPTCHA has an accessible alternative
  • ☐ Password managers are supported

✅ Focus Not Obscured (2.4.12)

  • ☐ Sticky headers don't hide focused elements
  • ☐ Modals don't obscure focus
  • ☐ Scroll margin is set for anchor targets

Tools to Test WCAG 2.2 Compliance

⚠️ What you should do in 2026: Focus on WCAG 2.1 Level AA first — that's what courts and laws currently require. Once you're compliant with 2.1, start addressing the new WCAG 2.2 AA criteria (especially 2.5.8 Target Size and 2.4.11 Focus Appearance).

Internal Links — More WCAG Resources

Frequently Asked Questions

❓ What is the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 adds 9 new success criteria focusing on mobile accessibility, cognitive accessibility, focus visibility, and authentication. WCAG 2.2 is backward compatible with 2.1 — nothing was removed.
❓ Is WCAG 2.2 legally required in 2026?
Not yet. Most laws (ADA, Section 508, EAA) still reference WCAG 2.1 Level AA. However, WCAG 2.2 represents best practice, and courts may eventually adopt it.
❓ What is the most important new WCAG 2.2 criterion?
2.5.8 Target Size (Minimum) — making touch targets at least 24x24px on mobile. This affects almost every mobile website and is now a Level AA requirement.
❓ What is the current WCAG version in 2026?
The current WCAG version in 2026 is WCAG 2.2, published October 2023. WCAG 3.0 is still in development and not yet finalized.
❓ Can I test WCAG 2.2 with a free ADA checker?
Many free checkers still focus on WCAG 2.1, but AccessiTool's free ADA checker includes WCAG 2.2 criteria like focus appearance and target size.

Final Thoughts

WCAG 2.2 is the latest evolution of web accessibility guidelines. While not yet legally required, it represents the current best practice for making websites accessible to everyone.

The most impactful new criteria for most websites are 2.5.8 Target Size (24x24px minimum) and 2.4.11 Focus Appearance (visible focus indicator). Start with these, then work through the remaining AA criteria.

🚀 Test Your Website Against WCAG 2.2

Free WCAG compliance scan — includes WCAG 2.1 and 2.2 criteria.

Scan Your Website Now →

No signup. Instant results. WCAG 2.2 ready.

Share