HTML Accessibility Checker
Paste a page or a component, or send a live page with the bookmarklet, and get common accessibility errors with the WCAG criterion behind each one, plus the heading outline.
Last checked
Your HTML
Issues
Paste HTML to see missing alt text, unnamed links and buttons, unlabelled fields, heading skips, duplicate ids and more.
Target size (WCAG 2.2, 2.5.8)
Target size needs real layout, which pasted HTML does not have. Run the bookmarklet below on a page to measure it.
- Every link, button and control is measured. A target under 24×24 CSS px fails when its 24 px circle meets another target or another small target's circle.
- Inline links in text, browser-default checkboxes and targets with a full-size twin to the same URL are shown as exempt.
- The essential exception needs your judgement.
Check a live page (bookmarklet)
View Source misses what JavaScript adds. Drag this button to your bookmarks bar, open the page you want to check (signed-in pages work too), and click the bookmark. It copies the page's current DOM to your clipboard, opens this checker in a new tab and sends the HTML over with postMessage, together with the measured size and position of every target for the 2.5.8 target size check. Nothing goes to a server. If the hand-off is blocked, paste from the clipboard.
How to use it
- Paste HTML: a full page from View Source, or a component's rendered markup from the browser's Elements panel.
- Read the issues. Errors break access for someone; warnings need a human look. Each links to its WCAG criterion; click the line number to jump to the tag.
- Fix them in your code, paste again, then test the page with a keyboard and a screen reader.
What it checks and why
These are the checks that catch the most common failures on real pages: images with no text alternative, links and buttons a screen reader can only announce as 'link' or 'button', form fields with no label, and headings that skip levels. WebAIM's yearly scan of a million home pages finds the same handful of issues at the top every year.
Each finding points to a WCAG 2.2 success criterion with its level: 1.1.1 Non-text Content for alt text, 1.3.1 Info and Relationships for headings, labels, lists, tables and landmarks, 1.3.5 Identify Input Purpose for autocomplete, 1.2.2 Captions, 1.4.2 Audio Control, 1.4.3 Contrast, 1.4.4 Resize Text for zoom blocking, 2.1.1 Keyboard for click handlers, 2.2.2 Pause, Stop, Hide, 2.4.1 Bypass Blocks for a missing main, 2.4.2 Page Titled, 2.4.4 Link Purpose, 2.5.8 Target Size (Minimum), 3.1.1 Language of Page, 3.1.2 Language of Parts, and 4.1.2 Name, Role, Value for ARIA, buttons and iframes. Errors are clear failures; 'needs review' findings depend on context a tool cannot see.
ARIA checks follow WAI-ARIA 1.2: the role must exist and not be abstract, aria-* names must be real, some roles need a state (a checkbox needs aria-checked), and content hidden with aria-hidden must not take keyboard focus.
The checker reads the markup as text, so it sees what you paste and nothing else. For a JavaScript app, use the bookmarklet: it serialises the page's DOM as it is now, copies it to your clipboard as a backup, opens this tool in a new tab and hands the HTML over with postMessage. The HTML stays in your browser. Some sites cut the link between tabs (Cross-Origin-Opener-Policy) or block bookmarklets with their Content Security Policy; then paste from the clipboard, or copy the html element from the DevTools Elements panel.
The target size check follows WCAG 2.2 success criterion 2.5.8, Target Size (Minimum), level AA: 'The size of the target for pointer inputs is at least 24 by 24 CSS pixels', unless an exception applies. Size needs real layout, so it runs only on pages sent with the bookmarklet, which measures each link, button and control with getBoundingClientRect. A target under 24 by 24 still passes when a 24 px circle centred on its bounding box does not intersect another target or the circle of another undersized target. Links inside a sentence (inline), browser-default checkboxes and radios (user agent control) and small targets with a full-size twin to the same URL (equivalent) are listed as exempt.
Specs and sources
- W3C WAI: Understanding SC 2.5.8 Target Size (Minimum)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- W3C: How to Meet WCAG 2.2 (Quick Reference)
- WebAIM Million: annual accessibility analysis of the top 1,000,000 home pages
- W3C WAI: Images tutorial (alt decision tree)
- W3C: Accessible Rich Internet Applications (WAI-ARIA) 1.2
- W3C WAI: ARIA11, using ARIA landmarks to identify regions of a page
- MDN: Window.postMessage()
Limits
- This is a pre-check, not a replacement for axe, WAVE or manual testing with a keyboard and a screen reader.
- It does not run CSS, so contrast is checked only where both colours are in inline styles; stylesheets, focus visibility and keyboard traps are not checked. Use the contrast checker and a keyboard for those.
- ARIA checks cover common roles and states, not every rule in the spec. Click handlers added with addEventListener or a framework leave no onclick in the HTML and are not seen.
- Media checks only see the markup: a video with captions burned in, or no speech at all, still gets a 'needs review' note.
- Target size is measured only through the bookmarklet, at the window size and zoom you run it at. The essential exception, and whether a small link really sits in a sentence, need your judgement. Equivalent targets are matched by the same link URL only.
- Automated checks find only part of the problems. A page with no findings can still be hard to use.
Questions
- Can this check a URL?
- Not by typing the address: the tool has no server to fetch pages, which also means nothing you check leaves your browser. Use the bookmarklet on the page instead, or paste its HTML from View Source.
- How do I check WCAG 2.2 target size (24px)?
- Run the bookmarklet on the page. The checker measures every link, button and control and lists each one under 24 by 24 CSS pixels whose 24 px circle, centred on it, intersects another target or another small target's circle, with its size and that neighbour. Pasted HTML has no layout, so it cannot be measured.
- Does a small icon button always fail 2.5.8?
- No. It passes if it has enough space: a 24 px circle centred on it must not touch another target or the circle of another small target. Links inside a sentence, browser-default controls and targets with a full-size alternative are also exempt.
- How do I check a website for accessibility?
- Start with an automated check like this one or a browser extension, then test with a keyboard only, zoom to 200%, and try a screen reader such as NVDA or VoiceOver on the key pages.
- Do decorative images need alt text?
- They need an empty alt attribute, alt="", so screen readers skip them. Leaving alt out entirely makes many screen readers read the file name.
- Is a placeholder enough as a form label?
- No. The placeholder disappears as soon as someone types and is not reliably announced. Use a visible label element tied to the field.
- How do I check a page that is built with JavaScript?
- Drag the bookmarklet on this page to your bookmarks bar, open the page and click it. It sends the DOM as it is after scripts ran, including pages behind a login, to the checker in a new tab.
- Can headings skip levels?
- WCAG does not strictly forbid it, but a jump from h1 to h3 suggests a missing section to screen reader users who navigate by headings, so it is flagged as a warning.