Check any public URL against WCAG 2.1 AA.
Compliance runs Lighthouse and axe-core on the rendered page. You get an honest AA call, then recommendations, an executive brief, and developer tasks from those findings only.
Built by Mirabelle Doiron. Hosted demo visitors do not enter API keys.
How it works
A focused accessibility workflow. Evidence first, then action, never the other way around.
- 01
Audit
Lighthouse and axe-core run against the fully rendered page. Scores and affected-element counts reflect the real DOM, not a guess.
- 02
Prioritize
Findings become a ranked action plan: severity, engineering effort, and business impact. Only issues present in the data.
- 03
Ship
Get an executive brief and a ticket-ready developer checklist with acceptance criteria, including WCAG references where they apply.
What you get
Everything you need to brief leadership and hand work to engineering from a single URL.
Rendered accessibility audit
Google PageSpeed Insights runs Lighthouse (axe-core) on the live page. The same class of engine commercial ADA scanners use.
Honest WCAG call
WCAG status is derived from serious and critical barriers, not a lenient overall score. If contrast fails, it says so.
Performance, SEO, best practices
Mobile LCP, CLS, TBT, SEO, and best-practices scores sit next to accessibility so you can see the full picture.
Prioritized recommendations
Each fix includes priority, effort in hours, and business impact. Nothing is templated or invented from outside the audit.
Executive summary
A plain-language brief for executives and marketing: risk, user impact, and what to fix this month.
Developer task checklist
Ticket-ready items grouped by module, with the element involved and what “done” looks like.
Nothing is invented
- Rendered audit by default.
Scores and barrier counts come from the live DOM.
- Static fallback is labeled.
Without a PageSpeed key, only served HTML is checked, and the UI says so.
- Synthesis stays on the evidence.
Recommendations, the executive summary, and developer tasks cover only issues present in the audit.
Download and run locally
The zip is source only. It does not include API keys. If you run Compliance on your machine, you add your own keys. A hosted demo does not ask visitors for keys.
© 2026 Mirabelle Doiron. You may download and use this. Do not sell, republish, or host it as your own product without permission. See LICENSE in the zip.
1. Install
unzip compliance.zip
cd compliance
npm install
cp .env.example .env.local2. Add your own keys to .env.local
Open .env.local and paste the values. Do not commit this file.
ANTHROPIC_API_KEY (required for write-ups)
Needed for Recommendations, Executive Summary, and Developer Tasks. Without it, the audit still runs. Those three buttons will not.
Get a key: console.anthropic.com/settings/keys
PAGESPEED_API_KEY (recommended for the full a11y audit)
Needed for the rendered Lighthouse / axe-core accessibility audit. Free. Without it, only static HTML checks run, and the UI labels that clearly.
Get a free key: Google PageSpeed Insights API
3. Start the app
npm run devThen open http://localhost:3000/audit to run an audit, or http://localhost:3000 for this page.
FAQ
The default path is a rendered Lighthouse / axe-core audit via Google PageSpeed Insights. If no PageSpeed key is set, the app inspects only the served HTML and says so. It never claims to be a full audit in that mode.
Yes, if you download the zip. You provide your own keys in .env.local. Anthropic is required for recommendations, the executive summary, and developer tasks. A free Google PageSpeed Insights key is recommended for the full rendered accessibility audit. Without PageSpeed, only static HTML checks run, and the UI says so. Visitors on a hosted demo do not enter keys.
The full product source: Next.js app, audit engine, synthesis routes, and this landing page. Secrets, node_modules, and build output are excluded. Unzip, install, and run locally.
Yes. Download it and use it for your own sites and internal work. You may not sell, republish, or host it as your own product without written permission from Mirabelle Doiron.
No. Synthesis is constrained to the audit data you just ran. If a check did not fail, it will not appear as a finding.