Source evidence
Eight bounded checks look for names, structure, alternatives, landmarks and a few risky interaction hints.
HTML evidence + human checks
Free website accessibility check.
Find accessibility signals the HTML can reveal, then work through the keyboard, zoom, contrast and content checks that need a person.
Review a pageInspect one public response
Which page should we review?
Start with a homepage, important service page, form or checkout step. Different templates should be checked separately.
This reads the HTML returned for the public page. Controls created only after JavaScript runs may need a browser-based review as well.
The part a person must do
Walk through the page, not just the markup.
Mark an item only after you have tried it. This progress stays on the page and is a working note, not a compliance result.
0 of 8 reviewed
Why there is no accessibility score
Conformance belongs to the complete experience.
WCAG applies to full pages and their responsive variations. A source scan can find useful evidence, but it cannot decide whether content is understandable or every interaction works for people.
Read W3C's evaluation overviewHuman walkthrough
A person checks keyboard operation, focus, zoom, contrast, meaning, errors and media quality.
Representative evaluation
Important services benefit from structured conformance evaluation and involvement from disabled users.
Accessibility questions
Know what this first look can—and cannot—tell you.
Does this prove WCAG compliance?
No. It reviews selected signals in one public HTML response. WCAG conformance requires evaluation of the full page and cannot be determined by automation alone.
Why do alt attributes still need human review?
A tool can detect an alternative, but a person must decide whether it communicates the image's purpose and whether empty alt text is appropriate.
What checks need a person?
Keyboard use, visible focus, zoom, contrast, clear labels, useful errors, reading order, caption quality and the accuracy of alternatives all need human judgement.
Why might a JavaScript application look incomplete?
This first look reads the returned HTML source. Content created only after JavaScript runs may not appear and should be tested in the rendered browser experience.
Should I check more than the homepage?
Yes. Review representative templates and important journeys such as search, contact, account, booking and checkout—including error and success states.