Support
Questions, problems and — most usefully — false positives.
Found a finding that is wrong? Please tell us. A scanner that flags correct markup is worse than no scanner, and a report of that kind is the most valuable thing you can send. Every one we receive gets a regression test so it cannot come back.
Email perceivablehq@gmail.com with the page URL and the finding text. A screenshot helps.
Getting started
- Open the page you want to check.
- Click the A11yScope icon in the toolbar. The side panel opens.
- Choose Scan this page.
- Select any finding to highlight that element on the page.
Common questions
Why does it say "needs review" instead of pass or fail?
Because the answer genuinely cannot be determined automatically. Contrast over a background image, a control hidden off-screen until focused, a video whose captions live in the player — each is a real question for a person, not a false alarm to dismiss. Guessing would be worse than saying so.
Does a clean scan mean my site is compliant?
No, and no tool can tell you that. Automated checks cover roughly a third of accessibility barriers. Whether your alt text is accurate, whether the page makes sense read aloud, whether a keyboard user can finish a task — those need manual testing. A clean scan is a good sign, not a certificate.
It says "this page cannot be scanned".
Browser pages (chrome://), the Chrome Web Store and
other extensions' pages are blocked to extensions for security
reasons. Open an ordinary web page and scan again.
Does it scan content inside iframes?
Not yet — only the top frame. Embedded content has to be opened directly and scanned on its own.
Does it work on pages behind a login?
Yes. It reads the page as rendered in your browser, so anything you can see, it can check. Nothing is uploaded — see the privacy policy.
Why did it flag something my other tool passed?
Tools implement different subsets of WCAG and make different calls on the exceptions. A11yScope implements the WCAG 2.2 target size criterion (2.5.8) including its spacing and in-sentence exceptions, which many tools skip entirely. If you think a finding is wrong, send it over — that is exactly the report we want.
Feature requests
Send them to the same address. Particularly useful: which checks you expected to see and did not, and what you currently do by hand that a tool could do for you.
Response time
A11yScope is maintained by one person alongside other work. Expect a reply within a few days. False-positive reports are handled first.