Developer Tools · Accessibility audit
A11yReady
Accessible by design, compliant by law.
Audit your website against WCAG 2.2 AA and see what each issue means under the European Accessibility Act, the ADA, and UK, Australian and Indian rules.
$ a11y-ready https://shop.example --markets EU,US --statement statement.md
71% of automated checks passed across 2 pages (12 failing, 6 warnings)
[FAIL] AR03 WCAG 1.1.1 Images have text alternatives
[FAIL] AR05 WCAG 1.3.1 Form fields have labels
[FAIL] AR13 WCAG 1.4.4 Users can zoom
[FAIL] AR26 WCAG 1.4.3 Text colour contrast
Report: a11y-report.html · Statement draft: statement.md
The problem
Since June 2025 the European Accessibility Act covers online shops, banking and booking services sold to EU consumers, including sellers outside the EU. US stores get ADA demand letters. Most teams don't know where their site fails.
What it does
26 automated checks, each tied to a WCAG success criterion with a concrete fix
Audits key journeys first: contact, checkout, sign-up and login pages
Explains the law in the EU, UK, US, Australia and India for your markets
Drafts an accessibility statement listing known issues, honestly marked 'partially compliant'
Manual checklist for what automation can't judge, including the WCAG 2.2 additions
GitHub Action: job summary on every build and a minimum-score gate for preview deployments
Works from saved or built HTML pages when sites block bots
How it works
- Enter your website and the markets you sell to
- Fix the failures, starting with level A
- Publish the statement and test the manual checklist
Works with
Runs in your CI
- uses: ./.github/actions/accessibility-ready
with:
url: https://preview.shop.example
html: dist/**/*.html
baseline: a11y-baseline.json # fail only on new issues
fail-on-new: 'true'
Your data
- Scans public pages only.
- No user data is collected.
- Reports are yours to share with auditors.
Who it's for
Questions
Who must comply with the EAA?
Since June 2025, online shops, banking and booking services sold to EU consumers.
Does it replace manual testing?
It finds what automation can; screen-reader testing by people remains important.
Related
Often used with A11yReady
RunbookFinder
Engineering knowledge searchAnswers your engineers can trust. Ask how a system works and get the runbook section, the postmortem and the code, with who owns it and whether it's out of date.
₹20,000–50,000View product → Developer ToolsTestHealer
Self-healing test fixesRedesign without breaking tests. After a redesign, find every UI test selector that broke, the element it meant, and a verified fix as a diff. The same for API version bumps.
₹25,000–75,000 per suiteView product → Developer ToolsBharatReady
India-readiness checksBuilt for India, properly. Find what breaks for Indian users: time-zone and financial-year bugs in your code, and Indian-language text that breaks your interface.
₹30,000–1,00,000View product →See A11yReady on your own data
A 30-minute call. We run the product on your export, repository or document and walk you through the results.