Scan a site for accessibility failures
Every page, at desktop and phone widths, against the WCAG 2.2 rules a machine can test. Free, no account. The report fills in here while it runs.
What it checks, and what it cannot
The scanner follows the links on the address you give, same site only, and runs axe-core's WCAG 2.2 Level A and AA rules on each page at 1280 and 375 pixels wide. At 320 pixels it also checks that the page does not scroll sideways and that nothing clips when WCAG's text-spacing overrides are applied. The engine is wcag-sweep, open source; you can run the same sweep on your own machine with no page limit.
What a machine can test is necessary, not sufficient. Keyboard order, meaningful names, captions, the sense of the text and whether the site works with a screen reader still need a person. A clean scan means the automated half is clean. That is where the audit and remediation service starts.
How it runs
- One site at a time; if someone is ahead of you the page says so.
- Public addresses only. Anything that resolves to a private network is refused, before the first request and after any redirect.
- The report is kept for thirty days at a permanent link, then deleted. Nothing else about the scan is kept.
- The scanner names itself in its user agent and links back to the engine, so it is never a mystery in your logs.