Find the accessibility problems on a page in one click.
A11yScope checks whatever page you are looking at against the automatable parts of WCAG 2.2 Level AA, shows each finding with the success criterion it comes from, and highlights the element on the page.
No account, no sign-in, nothing uploaded — and you do not have to take that on trust: the source is public. There is not a single network call in it.
31 checks, grouped by what breaks
-
Text alternatives
Images with no alt text, form controls with only a placeholder, icon buttons and links with no accessible name, untitled frames.
-
Colour contrast
Text below 4.5:1, with the measured ratio and both colours. Translucent backgrounds are composited through every ancestor layer rather than guessed at.
-
Structure
Missing page language or title, skipped heading levels, absent landmarks, data tables without header cells, malformed lists.
-
Keyboard, pointer and ARIA
Zoom disabled, tab order scrambled by positive tabindex, focusable elements hidden from screen readers, targets below the 24×24 minimum added in WCAG 2.2, misspelled ARIA roles.
What it will not tell you
Automated testing finds roughly a third of accessibility barriers. A clean scan is a good sign. It is not a compliance certificate, and no tool can confirm conformance with the European Accessibility Act on your behalf.
Whether your alt text is accurate, whether the page makes sense read aloud, whether a keyboard user can actually finish a task — those need a person.
So findings that cannot be decided automatically are marked needs review rather than passed or failed. Each one is a real question, not a false alarm to dismiss. Contrast over a background image, a control hidden off-screen until focused, a video whose captions live in the player — the tool says it does not know, because saying nothing would hide the question and guessing would be worse.
Details
- Where does my data go?
- Nowhere. Scans run inside your browser and results exist only in the side panel until you close it. See the privacy policy — or check it yourself: the source is public, and there is a test in it that fails the build if anyone ever adds a network call.
- What permissions does it need?
-
activeTab, which grants access only to the tab you press Scan on, only at that moment. It has no standing access to your browsing. - Which standard does it test against?
- WCAG 2.2 Level AA, including the newer 2.5.8 target size criterion — with its spacing and in-sentence exceptions implemented, so correctly built pages are not flagged.
- 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.