Free check · WCAG 2.2 · Updated
How do I check my website against WCAG 2.2?
Start with an automated scan, then check by hand what software cannot judge. A11yProof’s free scan loads your page in real Chrome and runs the axe-core rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA; each finding names the success criterion, how serious it is and how to fix it. Automated testing finds roughly 30–40% of WCAG problems, so the manual checks below cover the rest.
Check your page now
WCAG 2.2 AA rules in real Chrome, each issue with how to fix it.
What changed in WCAG 2.2
WCAG 2.2 became a W3C Recommendation on 5 October 2023. It keeps the WCAG 2.1 criteria, drops 4.1.1 Parsing and adds nine success criteria; six of them are at level A or AA:
- 2.4.11 Focus Not Obscured (Minimum), AA — a focused element is not hidden behind sticky headers, banners or chat widgets
- 2.5.7 Dragging Movements, AA — anything done by dragging also works with a single click or tap
- 2.5.8 Target Size (Minimum), AA — click and tap targets are at least 24 × 24 CSS pixels, or spaced so they are not crowded
- 3.2.6 Consistent Help, A — help options (contact, chat, FAQ) sit in the same place on every page
- 3.3.7 Redundant Entry, A — people are not asked to type the same information twice in one process
- 3.3.8 Accessible Authentication (Minimum), AA — logging in does not depend on a memory or puzzle test; pasting passwords and password managers work
What the automated scan checks
Rules a browser can verify reliably, on the page as it renders:
- Text alternatives for images, and names for links, buttons and form fields
- Colour contrast of text against its background
- Page title, page language and valid language codes
- Heading order, lists, frames and landmark regions
- ARIA roles and required ARIA attributes
- Target size (WCAG 2.2, 2.5.8) where the rule can measure it
The manual checks that close the gap
Fifteen minutes with a keyboard and a careful eye:
- Unplug the mouse: reach every link, button and form field with Tab, see where the focus is at all times and never get stuck.
- Watch the focus pass under sticky headers and cookie banners — it must stay visible (2.4.11).
- Try every slider, map and sortable list without dragging (2.5.7).
- Log in with a password manager and with pasting; no puzzle without an alternative (3.3.8).
- Read the alt texts: do they say what the image means? Check captions on videos.
- Zoom to 200% and narrow the window to 320 px: nothing should be cut off or need sideways scrolling.
Frequently asked questions
If my site meets WCAG 2.2, does it meet WCAG 2.1?
Yes. WCAG 2.2 includes the WCAG 2.1 success criteria (apart from 4.1.1 Parsing, which was removed), so content that meets 2.2 also meets 2.1 and 2.0.
Which level do I need?
Level AA. It is the level the European standard EN 301 549 references and the one accessibility laws such as the European Accessibility Act are measured against in practice.
Can I check a whole website, not just one page?
The free scan checks one page at a time, as often as you like. Monitor crawls up to 100 pages per site and re-checks daily; Compliance crawls up to 1,000 pages.
Can ChatGPT or Claude run the check for me?
Yes, on every plan including the free Scan. A11yProof supports MCP, so a connected assistant can read your scans and issues with their how-to-fix guidance and, at the level you allow, re-scan a page. Anything that uses your plan waits for your yes in the chat.
Do I need to sign up?
No. The single-page scan is free and needs no account.
Find the accessibility issues on your page
One page, free, no account. Monitoring, audit reports and an EAA statement when you need them.
Related
- Does the European Accessibility Act apply to me?
- Guide: target size
- Guide: colour contrast
- Use A11yProof from ChatGPT or Claude
- Everything A11yProof checks
Sources
Automated testing finds roughly 30–40% of WCAG problems; A11yProof reports what it found on the pages it tested. This page is general information, not legal advice.