Free WCAG 2.2 checker from 3thingsMedia

Can everyone use your website?

Check any page for accessibility problems against WCAG 2.2 AA, the standard behind the AODA and ADA. See exactly which elements fail and how to fix them.

10 of 10 free checks left this hour

Free, no signup
25 checks mapped to WCAG 2.2
Shows the exact elements to fix

What the checker looks at

Twenty-five checks, each linked to the WCAG 2.2 success criterion it tests, grouped by how badly a problem affects people.

Screen readers

Alt text on images, labels on form fields, names on links and buttons, page language and title, headings, and ARIA that points to real elements.

Keyboard & navigation

A way to skip past the menu, a tab order that isn't forced, no hidden content you can still tab to, and focus outlines that aren't removed.

Vision & motion

Zooming allowed on mobile, no sound that plays by itself, captions on videos, no timed refreshes, and no scrolling or blinking text.

Recently checked

Latest 1

sweary.com 17 minutes ago · 5 issues score89

What an automated check can't tell you

Automated testing finds roughly a third of accessibility problems. The rest need a person: is the alt text accurate, does everything work with a keyboard, is the colour contrast high enough?

Every report includes a manual checklist with simple ways to test each one. A clean result here doesn't mean a site is legally compliant; it means nothing obvious is in the way.

Lists show domains only, and only when the person checking chose to list the result.

FAQ

Accessibility questions

Can't find what you need? Ask us directly.

Which accessibility standard does it test against?

WCAG 2.2 Level AA, the current version of the Web Content Accessibility Guidelines. It's the standard behind accessibility laws in most places: Ontario's AODA requires WCAG 2.0 AA, and the US ADA rules and the EU's EN 301 549 point to WCAG 2.1 AA. WCAG 2.2 builds on both, so meeting 2.2 AA covers them too.

Does passing mean my site is compliant?

No. Automated tools can only find around a third of accessibility problems. Things like colour contrast on images, whether alt text is accurate and whether everything works with a keyboard need a person to check. Use this to find and fix the obvious problems quickly, then work through the manual checklist in your report.

Who needs an accessible website?

Everyone benefits: people using screen readers, keyboard users, people with low vision who zoom in, and anyone on a small screen in bright sunlight. In Ontario, businesses with 50 or more employees must meet WCAG 2.0 AA, and in the US, ADA lawsuits over inaccessible websites are common.

Do accessibility overlay widgets fix these problems?

Not on their own. Overlay widgets add a toolbar on top of the page, but the problems in the underlying HTML stay, and most accessibility experts advise against relying on them. The fixes in your report change the page itself.

Why don't you check colour contrast?

Contrast depends on the final colours after all of a site's stylesheets are applied, which needs a full browser to work out. Your report links to a free contrast checker and lists contrast first in the manual checks.

What do you store when I run a check?

The address checked (without any query string), the results and the time. We don't store your IP address; rate limits use a one-way hash of it. The recent list shows the domain only, and only if you tick the box.

More free tools

All 18 free tools →

Performance