An accessibility checker that works on pages behind a login

axe-core, the same open-source rule engine behind axe DevTools and the accessibility category in Lighthouse. It ships inside the extension rather than being fetched at runtime, because Manifest V3 doesn't allow remote code. You get the same rule results you'd get from any other axe-based tool.

Yes, and this is the reason to run it here rather than in a URL-based checker. The audit runs against the page already open in your browser, so a staging site, an admin screen or anything else that needs a session works the same as a public page. Nothing is sent anywhere to be scanned.

Pick from All rules, WCAG 2.0 A, WCAG 2.0 AA, WCAG 2.1 AA or WCAG 2.2 AA, and turn axe's best-practice rules on or off separately. Changing either setting re-runs the audit, and the standard you chose is named on the exported report.

Contrast has its own tab. Every failing pair shows the measured ratio against the ratio WCAG requires at that font size, the element's selector and both colours. Where a fix exists, Hoverify suggests the nearest passing colour: it holds the hue and saturation you chose and walks the lightness only as far as it needs to, so the suggestion still looks like your palette.

There are five simulations: protanopia, deuteranopia, tritanopia, achromatopsia and a low-vision blur. They apply to the page itself rather than to a screenshot, so you can keep scrolling and interacting while one is on.

No, and no automated tool will. Rule engines catch the machine-checkable failures: missing alt text, unlabelled controls, contrast, broken landmark and heading structure. That is a large share of what's wrong on most pages, but not all of it. Things like whether alt text is accurate, or whether a custom widget makes sense to a screen-reader user, still need a person. Treat the report as the fast first pass, not the certificate.

Export as a PDF report or as JSON. The PDF opens as a styled report you save from the print dialog, which is the one to send a client. The JSON is the raw audit data, which is the one to feed a CI pipeline or an issue tracker.

Yes. Every tool runs in the Firefox build; it carries an experimental label because Chromium gets fixes and new features first. Chrome is the fully supported browser, along with Chromium forks like Edge and Brave.

The accessibility checker is part of Hoverify, a paid extension with a 14-day refund policy. That's the substitute for a trial, and the checker isn't sold as a standalone scanner. One license runs in 3 browsers at a time and nothing auto-renews. See the pricing.