Free Website Accessibility Checker
Enter any public page and this checker reads its HTML for the accessibility failures a machine can see: missing alt text, links and buttons with no name, unlabeled form fields, missing page language, disabled zoom and untitled frames. Each result names the WCAG success criterion and the fix. It is free and stores nothing.
What it checks
These are the failures that show up most across the web. WebAIM’s 2026 analysis of the top one million home pages found missing alt text on 53.1%, missing form labels on 51%, empty links on 46.3% and missing document language on 13.5% (WebAIM Million).
| WCAG | Criterion | What is checked |
|---|---|---|
| 3.1.1 | Language of Page | The html element declares the page language. |
| 2.4.2 | Page Titled | The page has a title element. |
| 1.1.1 | Non-text Content | Visible images carry an alt attribute. |
| 2.4.4 | Link Purpose | Every link has text, an aria-label or an image with alt text. |
| 4.1.2 | Name, Role, Value | Buttons have an accessible name; iframes have a title; IDs used by labels and ARIA are unique. |
| 1.3.1 | Info and Relationships | Form fields have labels; headings form an outline without empty headings. |
| 1.4.4 | Resize Text | The viewport tag does not disable pinch zoom. |
| 2.4.1 | Bypass Blocks | There is a skip link or a main landmark. |
| 2.4.3 | Focus Order | No element uses a positive tabindex. |
| 1.4.2 | Audio Control | No media autoplays with sound. |
What it cannot tell you
An HTML check is a starting point. Contrast, keyboard use, focus, captions and whether text alternatives actually make sense need a rendered test and a person. That is why we audit with automated tools and manual testing together, and why an overlay that edits the page after it loads cannot settle the question; see what the FTC found. In our study of 95 California government homepages, the most common automated failures were unnamed links, low contrast and small tap targets.
Found failures? We fix them in the code.
A full audit tests your templates against WCAG 2.2 AA with automated and manual checks, then remediates in the source.
Common questions
What does this accessibility checker test?
It fetches the page you enter and checks its HTML against 13 automated tests mapped to WCAG success criteria: page language, page title, image alt attributes, link and button names, form labels, zoom, iframe titles, heading structure, skip links, tabindex, autoplaying media and duplicate IDs used by labels and ARIA.
Does a clean result mean my site meets WCAG?
No. These checks cover what can be seen in markup. Color contrast, keyboard operation, visible focus, captions, error handling and whether alt and link text are meaningful all need a person or a rendered test. Use the WCAG 2.2 checklist for the rest.
Why does it not check color contrast?
Contrast depends on the final rendered colors, including CSS, images and backgrounds. This tool reads the HTML without rendering it, so it reports contrast as not checked rather than guessing.
Is anything stored?
No. The page is fetched once when you ask, the results are shown to you, and nothing is saved.
Is this legal advice about ADA compliance?
No. It is a technical check of one page. Legal obligations depend on who you are and what you publish; our guides on the ADA Title II rule and on business websites explain what the Justice Department has said.
Related
- WCAG 2.2 AA checklist: all 55 criteria
- ADA website compliance and remediation
- The ADA Title II web rule explained
- Does the ADA apply to business websites?
- What is WCAG?
- All free tools
General information, not legal advice.