Accessibility Checker

Open in app

Scan any public URL against 14 WCAG 2.2 checks. Our homepage is loaded as an example.Scan any public URL against 14 WCAG 2.2 checks.

We fetch the page's HTML on our server and scan it. Nothing is installed, and we never see anything you haven't made publicly reachable.

Kept in this browser. Log in to save it to your account. Download or copy anything you want to keep.

What it checks

14 checks, each mapped to a WCAG criterion.

Every finding names the exact WCAG 2.2 success criterion it relates to, explains who it affects and why, and shows the offending code with a plain-English fix.

Images missing alt textWCAG 1.1.1
Unhelpful or filename-style alt textWCAG 1.1.1
Missing, multiple, or skipped heading levelsWCAG 1.3.1
Missing or invalid <html lang>WCAG 3.1.1
Missing or generic page titleWCAG 2.4.2
Form fields with no associated labelWCAG 1.3.1 / 4.1.2
Links with no text, or generic text like "click here"WCAG 2.4.4
Buttons with no accessible nameWCAG 4.1.2
Viewport meta that blocks pinch-to-zoomWCAG 1.4.4
Positive tabindex valuesWCAG 2.4.3
Missing "skip to content" linkWCAG 2.4.1
Data tables with no header cells or captionWCAG 1.3.1
iframes with no titleWCAG 4.1.2
Deprecated presentational markupWCAG 4.1.1
Questions

Frequently asked questions

What can't this checker find?
It only sees the initial HTML your server returns, so anything built later by JavaScript is invisible to it. It can't judge colour contrast in context (use our Contrast Checker for that), keyboard traps, focus order or how a screen reader reads the page, and it can't tell whether alt text is accurate, only that it exists. Automated tools catch roughly a third of accessibility issues at best, so a clean result isn't proof of accessibility.
Who's this for?

These fixes are usually made by QA engineers, front-end developers and content managers, alt text is a content owner's job, not a designer's. If you're a UX designer it's still worth understanding what gets flagged and why, since it shapes what you hand off. This isn't a core UX design tool, and we'd rather say that than oversell it.

Is this a full accessibility audit?

No. It's a static scan of the page's raw HTML against a checklist of common WCAG 2.2 failures. It's a genuinely useful first pass, and it's free, but it isn't a substitute for a manual audit by someone who understands assistive technology and can actually use the page with a screen reader or keyboard alone.

What does it actually check?

Things a computer can verify from the HTML alone: whether images have alt text, whether headings are structured properly, whether form fields have labels, whether links and buttons have discernible names, and a handful of other common failures. The full checklist is on this page.

Why can it not check colour contrast?
Contrast depends on how colours are actually rendered on screen: CSS variables, gradients, background images and overlays all affect it, and a lot of that only resolves in a real browser. Use our dedicated Contrast Checker for that, which does render real colour values.
Do you store the URLs people scan?

We fetch the page to run the scan and show you the result. We don't publish or share the URLs people submit.