About one in six people lives with a disability, and many use screen readers, keyboards or zoom. Paste a page’s HTML to find the most common accessibility problems, each linked to its WCAG 2.2 success criterion: images without alt text, form fields without labels, buttons and links with no name, skipped headings, missing page language and title, broken ARIA, zoom blocking, keyboard traps and low colour contrast in inline styles.
loading toolHow to use the accessibility checker
- Paste your code into the box (or tap Try a sample).
- Read the list of problems: ✕ marks an error, ! a warning.
- Tap Show next to a problem to jump to that line, fix it, and watch the list update.
Good to know
- Use real <button> elements for actions: they work with the keyboard automatically.
- Never block pinch-zoom with user-scalable=no.
Questions
Does passing mean my site is fully accessible?
No checker can promise that. It finds the problems that can be detected in code. Also try your page with only a keyboard and with a screen reader (NVDA on Windows, VoiceOver on iPhone and Mac, TalkBack on Android).
Why is a placeholder not a label?
It disappears as soon as someone starts typing, is often too pale to read, and some screen readers skip it. Use a visible <label>.
How is contrast checked?
When an element has both a text colour and a background colour in its style attribute, the contrast ratio is calculated with the WCAG formula: at least 4.5:1 for normal text and 3:1 for large text.
Is my data private?
Yes. Everything happens inside your own browser: nothing you type or choose is uploaded to us or anyone else.
Is it free?
Completely free, with no sign-up, no watermark and no limit on how many times you use it. Light ads keep the site running.
