Accessibility
Quick WCAG 2.2 checks for developers, designers and writers: names, labels, headings, keyboard order, colour blindness, captions and reading level. Learn more
Accessible Name Calculator
The name a screen reader announces for each control.
Alt Text Checker
Missing, redundant and file-name alt text, and empty image links.
ARIA Role & Attribute Reference
Every common role, and a checker for ARIA mistakes.
Colour-Blind-Safe Palette Checker
See your palette with colour blindness and in greyscale.
Form Label Checker
Unlabelled fields, placeholder labels and broken for/id links.
Heading Structure Checker
Your heading outline, with skipped levels and empty headings.
Link Text Quality Checker
Vague, duplicate, URL-only and unnamed links, flagged.
prefers-reduced-motion Generator
CSS and JS that respect a visitor’s reduce-motion setting.
Readable Line Length Checker
Characters per line for your width and font, measured.
Reading Level Checker (WCAG)
Flesch, Fog and a UK reading age, with long sentences shown.
Skip Link Generator
A working “skip to main content” link, with a live preview.
SRT/Caption Formatter & Validator
Check timings and reading speed, fix, shift or convert to WebVTT.
Tab Order Checker
The real keyboard order, plus clickables Tab can’t reach.
Touch Target Size Checker
Check sizes and spacing against WCAG 2.5.8 and 2.5.5.
Free accessibility checkers for WCAG 2.2
Accessibility problems are easiest to fix while you're building, and these tools let you check a snippet of HTML in seconds without installing anything. Paste your markup into the Alt Text Checker to catch missing and unhelpful image descriptions, the Form Label Checker to find fields that rely on a placeholder, the Heading Structure Checker to see your page outline, and the Link Text Quality Checker to spot every “click here”. The Accessible Name Calculator shows exactly what a screen reader will announce for each control, the Tab Order Checker shows the order keyboard users move through it, and the ARIA Role & Attribute Reference checks your ARIA for misspellings, missing states and roles in the wrong place.
For design decisions, the Colour-Blind-Safe Palette Checker shows your chart or status colours as people with colour blindness see them, the Touch Target Size Checker tests buttons against the WCAG 2.2 size rules, and the Readable Line Length Checker keeps paragraphs comfortable to read. Writers can score copy with the Reading Level Checker, video makers can tidy captions with the SRT Caption Validator, and developers can drop in a skip link and a reduced-motion stylesheet. Everything runs in your browser, and pasted HTML is read safely without running any of its scripts.
Questions and answers
- Can these tools tell me if my site meets WCAG?
- They check specific things that can be tested automatically, such as missing alt text, unlabelled fields, skipped heading levels and target sizes, which catches many common failures. Automated checks can't judge whether alt text is accurate, whether a custom widget really works with a keyboard, or whether content makes sense, so a full audit also needs manual testing with a keyboard and a screen reader.
- What's the difference between the Accessible Name Calculator and the Form Label Checker?
- The Accessible Name Calculator shows the name a screen reader announces for every button, link, field and image, and which attribute it came from. The Form Label Checker focuses on forms: as well as missing names, it flags placeholder-only labels, labels pointing at the wrong id, radio groups with no fieldset and missing autocomplete on personal details.
- Why does the Tab Order Checker flag positive tabindex values?
- Browsers visit every element with a tabindex of 1 or more before anything else on the page, in number order, so a single tabindex="1" can make keyboard focus jump to the middle of the page first. Using 0, or no tabindex, and putting the HTML in a sensible order keeps the tab order matching what people see.
- Should I use the WCAG 2.5.8 or 2.5.5 target size?
- WCAG 2.5.8 is Level AA, so it's the one most organisations must meet: 24 by 24 pixels, or smaller with enough space around it. WCAG 2.5.5 is the stricter Level AAA target of 44 by 44, which matches Apple's guidance and is worth aiming for on touch screens. The Touch Target Size Checker tests both, plus Android's 48dp.
- What reading level should I aim for?
- WCAG 3.1.5 suggests offering a simpler version when text needs more than a lower-secondary reading level, usually taken as a grade of 9 or a reading age of about 14. Public information should aim lower: GOV.UK writes for a reading age of 9. The Reading Level Checker shows which sentences push the score up so you know where to start.