What the audit checks

Every audit runs these checks on the rendered page in a real browser. Each finding is tied to a WCAG 2.2 criterion.

Ten checks, one audit

Open a check to see what it finds, what a failure looks like in code, and what still needs a person to test.

Checks in the audit and the WCAG criteria they cover
Check What it finds WCAG
Alt text Finds images, icons and image buttons with missing or empty text alternatives, and alt text that says nothing useful. 1.1.1, 1.4.5
Color contrast Measures text and control colors on the rendered page against the WCAG 2.2 AA ratios, and flags links that differ from text by color alone. 1.4.3, 1.4.11, 1.4.1
Keyboard and focus Finds controls people can't reach by keyboard, focus styles that were removed, and focused elements hidden behind sticky headers. 2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.11
Form labels Finds inputs without labels, placeholders used as the only label, and fields that don't say what they collect. 3.3.2, 1.3.1, 1.3.5, 4.1.2
Headings and landmarks Checks that pages have a clear heading outline, a main landmark and a way to skip repeated navigation. 1.3.1, 2.4.1, 2.4.6
Link text Finds links with no accessible name, vague text like "click here", and links that open new windows without warning. 2.4.4
ARIA Finds invalid roles and attributes, controls with no accessible name and ARIA that hides content people need. 4.1.2
Page language and title Checks that each page declares its language, marks passages in other languages and has a title. 3.1.1, 3.1.2, 2.4.2
Data tables Checks that data tables mark header cells, connect cells to their headers and have a caption or name. 1.3.1
Target size Measures buttons, links and icons on the rendered page against the WCAG 2.2 minimum of 24 by 24 pixels. 2.5.8

What automation can't decide

Automated checks find many failures, but some WCAG criteria need a person. The checklist shows which is which for every WCAG 2.2 A and AA criterion.

Run every check on a client page

Free, no account needed, results in about a minute.