In your pipeline

A failure in CI reproduces by opening the panel on the same page, because it is the same code path.

A terminal showing the JSON report the standalone bundle produces — a summary with counts by severity, then each finding with its rule id, severity, title and the WCAG criteria it breaks.

One file, no browser APIs

The scanning engine ships as a standalone bundle with no dependency on the extension APIs. Any runner that can evaluate a script in a page — Playwright, Puppeteer, Selenium — can inject it and read the report back as JSON.

The same rules, the same results

This is not a reduced rule set or a second implementation. A finding in CI has the same rule id, the same selector and the same suggested fix as the one you would see in the panel — which is what makes “reproduce it locally” a real instruction rather than a hopeful one.

Start with the page you are on

Install the extension, press F12 and open the Accessibility tab. No account, nothing to configure, and nothing leaves your machine.