Last updated: 11 June 2026.
Who I am
My name is Akhilesh Malani. I am an accessibility architect and digital inclusion strategist. I am blind, and I use the NVDA and JAWS screen readers on Windows every day for my work, my reading, and to build AMASAMYA itself.
I have spent the last sixteen-plus years auditing accessibility for enterprise web applications, banking platforms, and large content sites. The clients I have worked for include Google, Oracle Financial Services, Dun and Bradstreet, and Bank of Montreal, alongside many smaller engagements where I worked directly with engineering and product teams to ship more inclusive software.
My full portfolio is at akhileshmalani.com
The personal site has my long-form work, conference talks, the complete role history, contact options, and the case studies behind the impact statements on this page. If you want context on the person building this tool, that is the place to start.
Visit akhileshmalani.comWhy AMASAMYA exists
Most accessibility audit tools on the market work well enough, but very few were built to be used by the people they are testing the web for. The user interfaces of these tools assume a sighted operator. The findings reports assume a sighted reader. The documentation assumes you can scan a screenshot to understand what is being described.
When I have to use a tool that is itself inaccessible to audit a page for accessibility, the irony costs real time. AMASAMYA is the tool I wanted to use. The side panel is operable with a screen reader. Findings are presented in tables and lists rather than visual overlays. The development process includes screen-reader testing of every release, not as a final pass but as the way the work is done.
The project is self-funded. I have no investors influencing the privacy policy or feature roadmap. The reason I can give the tool away is that the cost of building it was my time, and I built it because I needed it.
Recent professional roles
| Client | Focus |
|---|---|
| Accessibility programme support for consumer products. | |
| Oracle Financial Services | End-to-end audits of banking applications across web and mobile, with prioritised remediation roadmaps executed across multiple release cycles. |
| Dun and Bradstreet | Enterprise-scale accessibility programme, including audit, training, and conformance documentation. |
| Bank of Montreal | Audits of online banking journeys with focus on screen-reader and keyboard parity. |
How I work
I audit with a mix of automated tooling (AMASAMYA itself, axe DevTools, WAVE), manual testing with NVDA, JAWS, VoiceOver, and TalkBack, and structured keyboard-only walkthroughs. I write the remediation guidance in plain language so the engineer reading the ticket does not need a screen reader of their own to understand what is broken.
I publish about accessibility on LinkedIn, where most of the conversation in our field happens. If you want to follow what I work on or read more about how AMASAMYA evolves, the LinkedIn profile and contact details are on akhileshmalani.com.
How to reach me
The fastest paths are:
- For product feedback or bug reports: the Send feedback page on this site.
- For engagement, consulting, or speaking enquiries: contact details on akhileshmalani.com.
- For source code, issues, and pull requests: github.com/accessitestai/AMASAMYA.