AMASAMYA - Frequently Asked Questions

AMASAMYA is an accessibility audit toolkit for the web. It has two parts: a Chrome browser extension that audits whatever page you are looking at, and a web platform at amasamya.akhileshmalani.com that ingests results from the extension, aggregates them, and produces manager-readable reports. Both are built blind-first: the user interface is itself fully operable with a keyboard and a screen reader.

Akhilesh Malani built it. Akhilesh is blind, uses NVDA and JAWS daily, and has spent his career auditing accessibility for Google, Oracle Financial Services, Dun and Bradstreet, Bank of Montreal, and others. The tools on the market work, but very few of them were built to be used by the people they are testing the web for. AMASAMYA exists to close that gap. Read more on the About Akhilesh page.

It means three concrete things. First, every UI element in the extension and the platform is reachable by keyboard, announces a sensible name and role to NVDA and JAWS, and works without the mouse. Second, audit findings are presented as tables and lists rather than visual overlays, because overlays do not survive a screen-reader read. Third, the development process itself includes screen-reader testing of every release, not as an afterthought.

Yes, today both the Chrome extension and the platform are free to use. The extension is published on the Chrome Web Store at no cost. The platform has a free Firebase sign-in and no paywall.

The Chrome extension will stay free and open-source. The platform may add a paid tier in future with team accounts, scheduled crawls, bug-tracker integrations, and stored audit history. Anything that exists in the free platform today will remain available to existing users; new paid features will be additions on top, not replacements.

Yes. There is no restriction on using AMASAMYA to audit client sites or to produce reports for clients, including paid client engagements. The Chrome extension source is MIT-licensed at github.com/accessitestai/AMASAMYA so you can also fork it for your own internal use.

The Chrome extension v4.2.0 ships with 24 automated audit engines covering WCAG 2.2 success criteria across Levels A and AA. From v4.2.0 onwards the same engines can also be run across a whole website in one go through the Site Crawl feature (up to 200 pages per run, three pages audited in parallel). A complete engine list is in the README at github.com/accessitestai/AMASAMYA. Reliable automated coverage of the full WCAG 2.2 success-criteria set is not possible from any tool; see the Known limitations page for an honest list of what AMASAMYA does not catch.

The platform has a Document Audit feature for PDF and Office document accessibility. There is also a structured mobile accessibility checklist for guided manual review of mobile apps (iOS and Android). The extension is web-only.

No, and on purpose. AMASAMYA finds issues and tells you how to fix them. It does not modify the audited page. Tools that promise automatic remediation through a JavaScript overlay are widely criticised by the accessibility community for not actually solving underlying problems and for sometimes making the page worse for assistive technology. AMASAMYA is the opposite of an overlay.

Extension audit results live in your browser's session storage and are gone when the browser session ends. Platform sessions are tied to your sign-in and stored in Firebase Firestore under your user record. The developer never receives copies of your audit findings.

No. AMASAMYA does not sell, rent, or share any user data with third parties for advertising or profiling. The only external transfer that the extension or platform makes is the optional sending of page screenshots to a Vision AI provider you have configured (Anthropic, OpenAI, or Google Gemini), using your own API key. Full details on the Privacy Policy page.

No. The Chrome extension works without any sign-in. The platform requires a free Firebase account so it can save your audit history across sessions.

All three are mature, credible tools. axe DevTools (and the axe-core rule library that also powers Lighthouse) is the de-facto industry standard rule set. WAVE is a trusted academic tool from WebAIM with a strong visual overlay. AMASAMYA's distinctive points are: blind-first UI, WCAG 2.2 coverage at Level AA from day one, Vision AI integration with the user's own API keys, and an MIT-licensed open-source extension. None of those tools and AMASAMYA fully cover all WCAG 2.2; manual testing is always required.

Use both if you can. Different rule libraries catch different issues. AMASAMYA is designed to be honest about its limits, so running it alongside another tool is encouraged rather than discouraged.

Use the Send feedback page on this site, or open an issue at github.com/accessitestai/AMASAMYA. AMASAMYA is built and maintained by one person, so response times depend on what else is in flight; every report is read.