What it does
-
Checks against WCAG
Every issue names the WCAG success criterion it relates to, so a finding is something you can act on and cite, not just a warning.
-
The failures that actually show up
Colour contrast, missing alt text, unlabelled form fields, heading order, and landmark structure — the ones that account for most of what automated testing can catch.
-
Points at the element
Each issue is tied to the element on the page that causes it, so you know exactly what to fix instead of hunting through the DOM.
-
Staging and logged-in pages too
It checks the page currently in your tab, so pages behind a login, on staging, or on localhost work the same as public ones.
Questions people ask
If a page passes, is it accessible?
No — and no automated tool can tell you that. Automated checks cover only part of WCAG. Things like whether alt text is meaningful, whether the keyboard order makes sense, or whether a screen reader announces something usefully still need a person to test them.
Which standard does it check against?
WCAG success criteria — each finding names the criterion it relates to so you can look up the full wording.
Does it fix the issues for me?
No. It reports what it finds and where; the fixes go into your own code.
Can I use it on pages behind a login or on localhost?
Yes. It checks the page currently open in your tab, so it doesn't matter whether that page is reachable from the outside.
Is this a compliance audit or a certificate?
No. It's a development aid. A formal accessibility audit involves manual and assistive-technology testing that no extension performs.
Also from WrongOrbit
-
Side Panel
Your favorite sites, tools, and bookmarks — always one click away
-
Minimal Start Page
A calm, customizable start page for Chrome
-
Add Signature to PDF
Draw your signature, embed it into any PDF