Accessibility quick check
Paste HTML to catch common accessibility problems: alt text, labels, headings, language.
FreeRuns in your browserNo signupUpdated 2026-11-05
Checked in your browser with DOMParser. Scripts in the HTML are not run.
Errors
0
Warnings
0
Elements checked
0
Issues
Paste some HTML to check it.
This is a quick heuristic check, not a full WCAG audit. It cannot judge colour contrast, keyboard use, focus order, captions or whether alt text is accurate. Test with a keyboard and a screen reader too.
About this tool
How it works and how to read the result.
Need this done for you?
Website design & development
Company websites designed and built to win trust and enquiries.
See the serviceWhat it does
This accessibility checker reads HTML you paste and flags common problems that stop people using a page with a screen reader, a keyboard or zoom. It checks for images without alt text or with file names as alt text, form fields without labels, missing or jumping heading levels, links and buttons with no text, vague link text such as "click here", a missing lang attribute or title, zoom blocked in the viewport tag, frames without titles, positive tabindex and duplicate ids. It runs in your browser with DOMParser and does not run any scripts in the HTML. It is not a full WCAG audit.
How to use it
- Open the page in your browser, view the source and copy it, or copy a section of your template.
- Paste the HTML into the box.
- Read the errors first, then the warnings. Each one shows the element it found.
- Fix the issues in your code or CMS and paste the HTML again to check.
How to read the result
The sample HTML has 6 errors and 4 warnings across 10 checked elements. The errors are a missing lang attribute on the html element, a viewport tag that blocks zoom, a logo image with no alt attribute, a logo link that therefore has no accessible name, a name field with only a placeholder and an empty button. The warnings are alt text that is just a file name, a jump from h1 to h3, a "Click here" link and a map iframe with no title.
Errors usually block someone completely: a screen reader user hears "link" or "button" with nothing after it and cannot tell what it does. Warnings make a page harder to use but rarely stop it working.
Some problems come in pairs. The logo image has no alt text, so the link around it has no name either. Adding alt="Example Plumbing home" fixes both.
A clean result means the page passed these checks, not that it is accessible. Contrast, keyboard focus and screen reader behaviour need testing by hand.
We build sites with semantic HTML, labelled forms and keyboard support as part of website design and development. For text colours, the contrast checker tests WCAG contrast ratios.
Questions
Frequently asked.
Is this a full WCAG audit?
No. It is a quick check of problems that can be found in the HTML alone. A WCAG audit also tests colour contrast, keyboard use, focus order, zoom and reflow, captions, error messages and how the page works with a screen reader. Use the quick check to fix the obvious problems first, then test properly.
Should every image have alt text?
Every image needs an alt attribute, but not every image needs a description. Images that carry meaning, such as a product photo or a chart, need alt text that says what they show. Decorative images should have an empty alt attribute, alt="", so screen readers skip them.
Why are placeholders not enough as form labels?
Placeholder text disappears as soon as someone starts typing, so people forget what the field was for. Many screen readers do not announce it reliably, and its pale grey colour is often hard to read. Use a visible label element linked to the field, and keep placeholders for examples of the format.
More in SEO
Related tools.
Your next move
Like what you see? Tell us about it.
A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.
India · Working with clients worldwide