Common questions.
If yours isn't here, email us and we'll answer it directly.
How does an audit work?
Paste in a public URL. We render the page in a real browser, scan it against WCAG 2.2, and order the results the way a screen reader would meet the page. Most scans finish in under a minute.
Is this a substitute for a full manual audit?
No. Automated tools catch a meaningful slice of WCAG issues, but not all of them; things like whether alt text is actually meaningful, or whether a workflow makes sense to someone using a screen reader, still need a human. Treat this as a fast first pass, not a legal compliance sign-off. If you need a full audit or advice on what to fix, get in touch.
What WCAG level do you check?
We check against WCAG 2.2 at the A and AA levels, which is what most accessibility laws and policies reference. AAA criteria aren't included in the automated scan.
Can you audit pages behind a login?
Not in the current version. The scanner needs a public URL it can reach directly. Support for authenticated pages is on the roadmap.
Do you store the pages you scan?
We keep the scan results so you can revisit your report, but we don't store a copy of your site itself beyond what's needed to generate that report.
How accurate is it?
We build on axe-core, the same open-source engine used by Chrome DevTools and most accessibility tooling, so false positives are rare. It's still an automated check though, so we'd rather under-claim than over-promise. Need a human review? Request an audit.
Does it work on single-page apps?
Yes. The page is rendered in a real browser and we wait for it to finish loading before scanning, so content built with JavaScript is included.
Can I audit a whole site, not just one page?
Not yet. The current version scans one URL at a time. Multi-page and full-site audits are on the roadmap.