Account

What new tool do you want?

Web & SEO

Website Accessibility Checker (WCAG 2.2 Quick Scan)

Scan a web page for common WCAG 2.2 accessibility failures — missing alt text, unlabelled form fields and buttons, empty links, heading order, page language and title, disabled zoom and more — with fixes for each.

How to use

  1. 1Enter the page address.
  2. 2Review the issues, starting with 'serious' ones.
  3. 3Fix them, then re-scan. Test with a keyboard and a screen reader too — automated tools catch only part of WCAG.

Frequently asked questions

Does passing mean my site is WCAG compliant?

No. Automated checks find roughly 30–40% of accessibility issues. Colour contrast, keyboard use, focus order, captions and screen-reader behaviour need manual testing.

Which laws require accessibility?

In the EU the European Accessibility Act applies to many products and services since June 2025; in the US, ADA Title III lawsuits commonly cite WCAG 2.1 AA, and public bodies must meet WCAG 2.1 AA under the 2024 DOJ rule; in the UK, public sector sites must meet WCAG 2.2 AA.

Will an accessibility overlay fix this?

Generally no — overlays rarely fix underlying code problems and can create new ones. Fix the HTML instead. Our Accessibility Overlay Checker shows whether a site uses one.

Sources

Why automated scanning only catches a documented fraction of real issues

The tool's own FAQ states automated checks find roughly 30-40% of accessibility issues, and that figure isn't a vague caveat — it reflects a real structural limit of what a script can evaluate without a human or assistive technology actually using the page. Missing alt text, unlabelled form fields and skipped heading levels are detectable because they're structural facts present in the HTML; whether color contrast is genuinely readable in context, whether keyboard focus moves in a logical order, or whether a screen reader actually announces content sensibly all require judgment or interactive testing a static scan can't perform.

Worked example: Website Accessibility Checker

Scanning a page might flag three images with no alt attribute, a form input with no associated label, and a heading structure that jumps from H1 straight to H3 — each a concrete, independently fixable item with a specific location in the HTML. After fixing those and re-scanning to confirm they're resolved, the FAQ's own guidance is to then test the same page with just a keyboard (can you reach and activate every interactive element using only Tab and Enter?) and a screen reader (does the announced content and order actually make sense?) — since passing the automated scan clean doesn't mean those manual checks will also pass.

Why overlays are called out specifically as not a fix

The FAQ directly addresses a common shortcut: installing a third-party accessibility overlay widget that promises automated fixes. It states plainly that overlays generally don't fix underlying code problems and can introduce new interference with assistive technology — a position reflecting broad consensus among accessibility professionals and disabled users, not a one-off opinion. Checking whether a site relies on an overlay instead of fixing its actual HTML is exactly what this tool's companion Accessibility Overlay Checker is built to reveal.

Why the legal landscape varies enough to need checking for your specific situation

The applicable rules genuinely differ by region and sector — the EU's European Accessibility Act applies to many products and services since June 2025, US ADA Title III lawsuits commonly cite WCAG 2.1 AA as the practical standard even though ADA itself doesn't name a specific technical standard, US public bodies must meet WCAG 2.1 AA under a 2024 DOJ rule, and UK public sector sites must meet WCAG 2.2 AA specifically. Which rule set actually applies depends on your organization's sector, location and audience — worth confirming against your specific situation rather than assuming one region's rule covers all cases.

Related tools

More: Web & SEO