Accessibility Checker
We're already showing a live scan of our own homepage so you can see exactly what a result looks like. Replace the URL with your own page and scan it whenever you're ready.
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.
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.
What this tool can't do.
This is a static scan of the initial HTML your server returns -- nothing more. It's genuinely useful as a first pass, and it'll catch real, fixable problems. It isn't a full audit, and treating a clean result as proof of accessibility would be a mistake.
- It only sees the initial HTML response, not anything rendered afterwards by JavaScript -- a lot of modern sites build most of their page client-side, which this scan can't see.
- It can't judge colour contrast in visual context (use our Contrast Checker for that), or spot content that's visually hidden but not marked up as such.
- It can't test keyboard traps, focus order in practice, or how a real screen reader actually reads the page out loud.
- It can't judge whether alt text is accurate, only whether it exists and isn't obviously a placeholder.
- Automated tools like this one catch roughly a third of accessibility issues at best -- the rest need a person to use the page.
Frequently asked
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.
For the two-thirds a scan can't see.
Automated scans catch roughly a third of accessibility issues at best. The rest -- how the page actually feels with a screen reader, real keyboard navigation, colour contrast in visual context -- need a trained person to check.
Beginner UX (AI) Design starts 14 October 2026.
Tools help you do the work. They don't teach you the judgement behind it. Beginner UX (AI) Design is taught live online by working UX professionals, built for career-changers with no design background.
Working in a team rather than learning on your own? We run in-house UX training built around your own product, and we can talk it through on the same call.