Accessibility · WCAG 2.1 AA
A dated, good-faith record of where a site stands on WCAG 2.1 AA.
ADA-Watch runs a bounded, read-only scan of a public site — live axe-core, its contrast check included, across a same-origin crawl — and produces a deterministic scorecard and a scoped conformance record. Automated scanning only: anything a tool cannot confirm is reported as “needs human review”, never as a pass.
Not sold today — ADA-Watch is not one of the three offers we sell. The scan runs on this site today as a read-only tool. What we sell today is on the pricing page.
What the scan does
Read-only by design
The only tenant is a hard read-only scan: collect and analyse, nothing more. There is no write, propose, or open-PR capability anywhere on this path — asserted at the surface.No fabrication
Criteria this scan does not check, sub-threshold findings, and pages that could not be rendered are all reported as needs human review — never silently upgraded to a pass.Deterministic scorecard
The full WCAG 2.1 A + AA catalogue, scored from live axe-core violations. Contrast is one of them, and it is never scored as a pass: the check cannot read text sitting on a gradient, an image or an overlapping layer, so a clean result speaks for part of the page. Identical evidence yields a byte-identical scorecard — and there is no overall “compliant” boolean to oversell.Public sites only
Every target is SSRF-checked before a byte is fetched: the hostname is resolved once and refused if any answer is a private, loopback, link-local or metadata address; the fetch re-resolves the name, so a record that changes in between is a limit of this guard, not a thing it catches.A record you can keep
Each scan renders an unsigned Accessibility Conformance Statement record (HTML and a scoped PDF): the standard referenced, the date, what was checked, and what still needs a human.Human-in-the-loop
A record becomes a signed statement only when a named accessibility expert reviews and signs it. Automated tooling cannot perform that step, and this record does not claim to.What an automated scan cannot do
Automated tools detect a minority of accessibility barriers. They cannot confirm that content is usable with assistive technology, that meaning is conveyed without colour, that keyboard navigation is logical, or that a page works for a person who is blind, DeafBlind, or has a cognitive disability. A clean automated scan does not mean a page is accessible — it is a starting point for human review, recorded honestly.
