The 12 HTML checks my accessibility scanner runs — and what each one can't see
The 12 HTML checks my accessibility scanner runs — and what each one can't see I build AuditReady, an accessibility scanner that runs 12 deterministic checks over a page's HTML and turns the findings into a report an agency can hand a client. Same product as my first post here , so the disclosure stands: it's mine. Here is what each check decides, and where it runs out of road. Every check looks…
This accessibility scanner runs 12 checks on a webpage's HTML code, producing a report for agencies to share with their clients. Each check looks for a specific pattern and determines if it violates WCAG 2.2 criteria. The checks include missing alt text, missing form labels, heading structure issues, missing page titles, incorrect page language, vague link text, pinch-zoom problems, icon buttons without names, iframes without titles, duplicate id values, missing table headers, and positive tabindex values.
However, these checks are limited as they only read markup and cannot see what a browser, ear, or human judgment would notice. Automated tools can only catch a minority of WCAG issues, and AuditReady, the accessibility scanner in question, is not a compliance guarantee or legal advice; a manual review by a person is still required.
The full report also includes contrast measurements, non-text contrast for icons and borders, focus visibility, keyboard traps, custom widget operability, error descriptions, zoom and reflow testing, skip links, captions, transcripts, audio description, cookie banners, chat widgets, booking engines, and more.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
