WCAG 2.2: What's New in 2025 and How It Affects Your Website

The Web Content Accessibility Guidelines (WCAG) 2.2 became the recommended standard in October 2023, but many organizations are still catching up in 2025. If you're responsible for website accessibility, understanding these changes isn't optional—it's essential for legal compliance and user experience.

Why WCAG 2.2 Matters in 2025

The Americans with Disabilities Act (ADA) doesn't specify which WCAG version to follow, but courts increasingly reference WCAG 2.1 AA as the minimum standard. With WCAG 2.2 now established, it's becoming the de facto compliance benchmark.

Legal Context:

• Over 4,500 ADA website lawsuits were filed in 2024
• Average settlement costs range from $10,000 to $75,000
• WCAG 2.2 compliance demonstrates good faith effort to accommodate users with disabilities

The 9 New Success Criteria in WCAG 2.2

1. Focus Not Obscured (Minimum) - Level AA

What it means: When a component receives keyboard focus, it must be at least partially visible—not completely hidden by other content.

Why it matters: Many modern websites use sticky headers, cookie banners, and chat widgets that can cover focused elements, making keyboard navigation impossible.

How to fix:

/* Ensure focused elements are visible */
*:focus {
  scroll-margin-top: 100px; /* Account for sticky header */
  position: relative;
  z-index: 10;
}

2. Focus Appearance - Level AAA

What it means: Focus indicators must have sufficient contrast (at least 3:1) and be at least 2 CSS pixels thick.

Real-world impact: Default browser focus indicators often fail this criterion. You need custom styling.

*:focus-visible {
  outline: 3px solid #0066CC;
  outline-offset: 2px;
}

3. Dragging Movements - Level AA

What it means: Any functionality that requires dragging must have an alternative that works with single-pointer activation (clicks/taps).

Common violations:

• Slider controls (volume, price ranges)
• Sortable lists (drag-to-reorder)
• Image croppers

Solution: Always provide buttons as alternatives to drag operations.

4. Target Size (Minimum) - Level AA

What it means: Interactive elements must be at least 24×24 CSS pixels, with some exceptions.

Why it matters: Users with motor disabilities struggle with small touch targets. This is especially critical for mobile users.

button, a, input, select {
  min-height: 44px; /* Apple's recommendation */
  min-width: 44px;
  padding: 12px 16px;
}

5. Consistent Help - Level A

What it means: If help mechanisms (live chat, phone numbers, contact forms) appear on multiple pages, they must be in the same relative order.

Implementation tip: Create a consistent help section in your footer or header that appears on all pages.

6. Redundant Entry - Level A

What it means: Don't ask users to enter the same information twice in the same session unless necessary for security.

Common violations:

• Multi-step forms asking for name/email repeatedly
• Checkout flows requesting shipping address twice

Solution: Use session storage or form state management to persist user input.

// Save form data to session
const saveFormData = (data) => {
  sessionStorage.setItem('checkoutData', JSON.stringify(data));
};

// Retrieve on next page
const formData = JSON.parse(sessionStorage.getItem('checkoutData') || '{}');

7. Accessible Authentication (Minimum) - Level AA

What it means: Cognitive function tests (like CAPTCHAs) must have alternatives or support for assistive technologies.

Better alternatives:

• Use reCAPTCHA v3 (invisible)
• Implement email/SMS verification
• Use passwordless authentication (magic links)

8. Accessible Authentication (Enhanced) - Level AAA

What it means: Don't require users to remember or transcribe information to authenticate.

Solution: Support password managers, biometric authentication, or magic links.

9. Focus Not Obscured (Enhanced) - Level AAA

What it means: Focused elements must be fully visible (stricter than the Level AA version).

Backward Compatibility: What Stayed the Same

Good news: WCAG 2.2 is backward compatible with WCAG 2.1. If you're already compliant with 2.1 AA, you're about 80% there. The new criteria address gaps in mobile accessibility, cognitive disabilities, and low-vision users.

How to Audit Your Site for WCAG 2.2

Free tools:

1. AccessMend - Automated WCAG 2.2 checker with AI-powered fixes (Try it free)
2. axe DevTools - Browser extension for manual testing
3. WAVE - Visual feedback on accessibility issues

Manual testing checklist:

• Test all interactive elements with keyboard-only navigation
• Measure focus indicator contrast (use browser DevTools color picker)
• Verify touch targets are 44×44px minimum
• Check slider controls have button alternatives
• Review multi-step forms for redundant entry
• Test authentication flows with password manager

WCAG 2.2 Compliance Timeline

January 2025: EU Web Accessibility Directive requires WCAG 2.2 AA for public sector websites

June 2025: Expected spike in ADA lawsuits citing WCAG 2.2 non-compliance

Ongoing: Courts will increasingly reference WCAG 2.2 as the standard of care

Quick Wins for WCAG 2.2 Compliance

Start with these high-impact, low-effort fixes:

1. Improve focus indicators (30 minutes)
2. Increase button sizes (1 hour)
3. Add alternative to sliders (2 hours)
4. Implement form state persistence (3 hours)

Common Myths About WCAG 2.2

Myth: "We're compliant with WCAG 2.0, so we're good." Reality: Courts are moving toward 2.1/2.2 as the baseline. 2.0 compliance is no longer sufficient.

Myth: "Automated tools catch everything." Reality: Automated tools detect ~30-40% of issues. Manual testing is essential.

Myth: "Accessibility is a one-time project." Reality: Every new feature must be tested for accessibility. It's an ongoing process.

Getting Started Today

1. Run a free scan with AccessMend to identify WCAG 2.2 violations
2. Prioritize fixes by severity (A, AA, AAA)
3. Train your team on the 9 new success criteria
4. Update your QA process to include accessibility testing

Don't wait for a lawsuit to take accessibility seriously. WCAG 2.2 compliance protects your users and your business.

Resources

• Official WCAG 2.2 Specification (opens in new tab)
• Understanding WCAG 2.2 (opens in new tab)
• AccessMend WCAG 2.2 Checker

---

Need help with WCAG 2.2 compliance? Get a free accessibility report in 60 seconds.