Scan a site for accessibility failures

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; for a site past 1,000 pages, run the same sweep on your own machine, free, with no limit at all.

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. Nothing here is held back for a paid version: the audit and remediation service is the work a machine cannot do, and the fixes, not more of this scan.

How it runs

• Scans run in the order they arrive; if others are ahead of you, the page says how many. A large site takes a while, a few seconds a page. Its link works the whole time: close the tab and come back.
• 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.