The blind-first WCAG 2.2 accessibility audit toolkit.
A Chrome extension and web platform built to be operated BY accessibility testers, developers, and designers who use a screen reader, not just FOR them. Free. Open source. No signup needed for the extension.
What AMASAMYA is
AMASAMYA has two parts. The Chrome extension runs 24 WCAG 2.2 audit engines against whatever page you are looking at, walks up to 200 pages of a website in one Site Crawl run, diffs each audit against the last one for the same URL so a follow-up run tells you what is New, Regressed, Unchanged, or Resolved, and (from v5.2.0 onward) can run a crawl on a schedule you set from the platform. Scheduled runs post a summary to Slack, Microsoft Teams, or your own webhook so a regression on your production site pings your team the moment it lands. Findings appear in a side panel that is fully operable with NVDA, JAWS, and VoiceOver. The web platform at amasamya.akhileshmalani.com accepts single-page audits, crawl reports, document files, and structured mobile checklists, and produces reports a manager can read. The new Schedules tab is where you configure recurring crawls.
Both are free. The extension is open source under MIT licence at github.com/AMASAMYA/AMASAMYA.
How it is different from other automated audit tools
Blind-first design
The side panel UI itself is screen-reader operable. Findings appear as keyboard-navigable tables and lists, not visual overlays. The tool passes the standards it tests for.
WCAG 2.2 coverage from day one
24 engines covering Level A and AA, including the 2.2 additions (Focus Not Obscured, Dragging Movements, Consistent Help, Redundant Entry, Accessible Authentication) that older tools have not caught up to.
Vision AI with your own key
Optional Focus Indicator Narrator and Visual Layout Auditor modules connect to your Anthropic, OpenAI, or Google Gemini key for visual checks a blind tester cannot perform alone. Your key stays on your device.
No accessibility overlay
AMASAMYA finds issues and tells you how to fix them. It does not inject JavaScript into your page to "fix" accessibility, a pattern the community has criticised for not actually solving underlying problems.
Who benefits
- Accessibility testers who are blind or low-vision: stop relying on a sighted colleague to translate findings.
- Developers who use a screen reader: a tool whose UI respects your input modality.
- Designers verifying WCAG 2.2 work: check your own work without sighted help.
- Consultants and auditors: structured findings, exportable as JSON, HTML, CSV, Text, SARIF, or annotated PNG.
- Managers and procurement officers: reports aggregated and presentable, including a VPAT 2.5 generator on the platform.
Quick links
On the AMASAMYA platform
- FAQ - what AMASAMYA does, costs, covers, and does not cover.
- Known limitations - honest list of what no automated tool catches.
- About Akhilesh - the person behind the tool.
- Send feedback - bug reports, feature requests, anything.
- Privacy policy - what is collected, what is not, where data lives.
If you try AMASAMYA, please rate the extension on the Chrome Web Store and share what worked or what did not via the feedback page. Community feedback shapes the next release.