What this checks
About twenty-five checks, read from the page's HTML and its response headers, grouped the way ShipperAG groups a release:
- Human experience. Language declared, alternative text, accessible names on links and buttons, form labels, iframe titles, one H1, heading order, a main landmark, zooming allowed, duplicated ids.
- Findability. Title length, meta description, canonical URL, social preview tags, structured data that parses, and whether the page asks not to be indexed.
- Trust. HTTPS, HSTS, Content Security Policy, X-Content-Type-Options, Referrer-Policy, and clickjacking protection.
- Operability. The status code, whether a missing page returns a real 404, whether a sitemap exists, and how heavy the HTML is.
What it does not check, and why that is on the report
This runs without opening a browser, so colour contrast, touch target sizes, keyboard order, focus visibility and anything that appears after a click are outside it. Those are not omitted quietly — they are listed, by name, in the fourth panel of every report.
That is the whole argument. A checker that reports "all clear" because it could not see anything is worse than one that says what it did not look at. In our scan of 410 high-traffic home pages, 74% failed a check a machine can decide — and 81% also returned checks the tool would not decide at all. Every one of those sat in a state most dashboards do not have.
If your page comes back with almost nothing in the HTML, the report will say so. That usually means it renders with JavaScript, and it is worth knowing: some crawlers and AI assistants see exactly what this check saw.
Why four states
- Verified. A check ran and passed, and you can see which one.
- Issue found. A check ran and failed, with the count.
- Needs input. A machine got as far as it can and a person has to judge: the alt text exists, but is it accurate?
- Not covered. Nothing checked it. This is the state most reports quietly leave out.
The same four states are how ShipperAG reports a whole release, against your requirements rather than one page. See the 32 WCAG criteria no tool checks for you, or the full website QA checklist for the manual half.