← Back to Accessalyze

WCAG 2.2: What's New and What Changed

What's New in WCAG 2.2

What Was Removed

4.1.1 Parsing REMOVED — This criterion required HTML to be parseable without errors (no duplicate IDs, properly nested elements). It was removed because modern browsers handle HTML errors gracefully, and it was not meaningfully correlated with actual AT failures. Unique IDs are still a best practice, just not a WCAG criterion.

The 6 New AA Criteria You Need to Implement

1. Focus Not Obscured (2.4.11)

Sticky navigation bars and cookie consent banners frequently obscure keyboard-focused elements. Fix: ensure your sticky headers have adequate scroll-padding-top.

html {
  /* Match the height of your sticky header */
  scroll-padding-top: 80px;
}

2. Focus Appearance (2.4.13)

This goes significantly beyond WCAG 2.1's focus visible (2.4.7). The focus indicator must have:

• An area of at least (perimeter of component in CSS pixels × 2)
• Color contrast of at least 3:1 between focused and unfocused states

:focus-visible {
  outline: 3px solid #2563eb; /* 5.08:1 against white ✓ */
  outline-offset: 2px;
  /* For a 100px wide button: 3px outline ≥ 2px requirement ✓ */
}

3. Dragging Movements (2.5.7)

Any drag-and-drop interface needs a single-pointer alternative:

<!-- Sortable list: drag is primary, but also provide buttons -->
<li>
  Task name
  <button aria-label="Move task up">↑</button>
  <button aria-label="Move task down">↓</button>
</li>

4. Target Size — Minimum (2.5.8)

Targets must be at least 24×24 CSS pixels. Inline links are exempt (can't resize without reflowing text). For other interactive elements:

button, [role="button"], input, a.standalone-link {
  min-height: 24px;
  min-width: 24px;
  /* Better: aim for 44×44px (WCAG 2.5.5 AAA) */
}

5. Redundant Entry (3.3.7)

In multi-step forms, don't make users re-enter information from earlier steps. Either auto-populate it or provide a selection option.

6. Accessible Authentication (3.3.8)

Login that requires typing a CAPTCHA code violates this if no alternative is provided. Acceptable alternatives: copy-paste the code (don't block clipboard), use a password manager (don't disable autocomplete), provide an email link option.

<!-- Allow password manager autofill -->
<input type="password" autocomplete="current-password">

<!-- Don't block clipboard paste -->
<!-- Never add: onpaste="return false" -->

Is WCAG 2.2 AA Legally Required?

As of April 2026, the DOJ's ADA Title II final rule references WCAG 2.1 AA, not 2.2. However, WCAG 2.2 is the current W3C recommendation and represents current best practice. Legal requirements will likely reference 2.2 in future rule updates.

← Back to Accessalyze · ← What Is WCAG 2.1 AA?