Skip to main content

WCAG 2.2 AA Compliance Checker

Test your website against the latest Web Content Accessibility Guidelines. Our checker evaluates over 50 WCAG 2.2 AA success criteria and tells you exactly what to fix.

ADA · WCAG 2.2 AA · Section 508 · EAA

One lawsuit can cost $25,000. We cost $99/month.

Scan your website for accessibility violations in seconds. Get AI-powered fixes, compliance certificates, and continuous monitoring — before a lawsuit finds the issues first.

Free scan — no account required. Results in under 60 seconds.

10,000+
Sites scanned
500K+
Violations found
99.2%
Accuracy rate

What is WCAG?

The Web Content Accessibility Guidelines (WCAG) are the internationally recognized technical standards for web accessibility, published by the World Wide Web Consortium (W3C). WCAG defines how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

WCAG is organized around four principles, known as POUR:

  • Perceivable — information and UI components must be presentable to users in ways they can perceive (e.g., alt text for images, captions for video).
  • Operable — UI components and navigation must be operable by all users (e.g., keyboard accessibility, enough time to interact).
  • Understandable — information and UI operation must be understandable (e.g., readable text, predictable navigation).
  • Robust — content must be robust enough to be interpreted by a wide variety of user agents and assistive technologies.

WCAG defines three conformance levels:

  • Level A — the minimum level of accessibility. Addresses the most fundamental barriers. Failing Level A means some users literally cannot access your content.
  • Level AA — the standard target for legal compliance worldwide. This is what the ADA, Section 508, the European Accessibility Act, and most other laws reference.
  • Level AAA — the highest level of accessibility. Not typically required by law, but recommended where possible.

What changed in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on October 5, 2023. It builds on WCAG 2.1 by adding nine new success criteria focused on improving the experience for users with cognitive and learning disabilities, users with low vision, and users on mobile and touch devices.

WCAG 2.2 also removed one criterion from 2.1: Success Criterion 4.1.1 (Parsing), which is no longer relevant because modern browsers and assistive technologies handle HTML parsing errors more gracefully than they did when WCAG 2.0 was written.

2.4.11

Focus Not Obscured (Minimum)

Level AA

When a UI component receives keyboard focus, it must not be entirely hidden by other content such as sticky headers, footers, or modals.

2.4.12

Focus Not Obscured (Enhanced)

Level AAA

When a UI component receives keyboard focus, no part of it is hidden by author-created content.

2.4.13

Focus Appearance

Level AAA

Focus indicators must meet minimum area and contrast requirements, making them clearly visible to keyboard users.

2.5.7

Dragging Movements

Level AA

Any functionality that uses dragging must also be operable with a single pointer without dragging, unless dragging is essential.

2.5.8

Target Size (Minimum)

Level AA

Interactive targets must be at least 24x24 CSS pixels, with exceptions for inline text links and targets with sufficient spacing.

3.2.6

Consistent Help

Level A

If a page contains help mechanisms (contact info, chat, FAQ links), they must appear in the same relative order across pages.

3.3.7

Redundant Entry

Level A

Information previously entered by the user in the same process must be auto-populated or available for selection, unless re-entering is essential for security.

3.3.8

Accessible Authentication (Minimum)

Level AA

Authentication processes must not require cognitive function tests (memorizing passwords, solving puzzles) unless an alternative method is available.

3.3.9

Accessible Authentication (Enhanced)

Level AAA

No step in authentication requires a cognitive function test, with no exceptions beyond object or content recognition.

How to check WCAG compliance

Checking WCAG compliance requires a combination of automated testing and manual review. Here is a practical approach:

  1. Run an automated scan — tools like ADAfriendly use the axe-core engine to detect violations across your site. Automated testing reliably catches issues like missing alt text, color contrast failures, missing form labels, empty links, and improper heading hierarchy.
  2. Test with a keyboard — navigate your entire site using only the Tab, Enter, Escape, and arrow keys. Verify that every interactive element is reachable, that focus is visible, and that you never get trapped.
  3. Test with a screen reader — use NVDA (Windows, free), VoiceOver (Mac/iOS, built-in), or TalkBack (Android, built-in) to verify that content is read in a logical order and interactive elements are properly announced.
  4. Check zoom and reflow — zoom your browser to 200% and 400%. Content should reflow to fit a single column without horizontal scrolling at 320px viewport width.
  5. Review color and contrast — ensure text meets 4.5:1 contrast for normal text and 3:1 for large text. Non-text elements like icons and form borders need 3:1 contrast.

Test your site now

Enter your URL to check WCAG 2.2 AA compliance. Results include specific success criteria references for every violation found.

ADA · WCAG 2.2 AA · Section 508 · EAA

One lawsuit can cost $25,000. We cost $99/month.

Scan your website for accessibility violations in seconds. Get AI-powered fixes, compliance certificates, and continuous monitoring — before a lawsuit finds the issues first.

Free scan — no account required. Results in under 60 seconds.

10,000+
Sites scanned
500K+
Violations found
99.2%
Accuracy rate

Go beyond a one-time scan

WCAG compliance is not a one-time project. Content changes, new features, and third-party scripts can introduce violations at any time. ADAfriendly provides continuous monitoring, auto-fixes, and compliance documentation.