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, delivered through Virtusa Consultancy, Tech Mahindra, HCL Technology, and Prakat Solutions. Before that, I held a technical-support role at Mphasis, which is where my professional career began before I moved into accessibility.
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 I built AMASAMYA
Most accessibility tools on the market work fine if you can see the screen. Very few of them work if you cannot. Their menus assume you can point at things. Their reports assume you can scan a screenshot. Their help pages assume you know what the arrow icon means.
So when I, a blind accessibility auditor, need to check a website for accessibility problems, the tool I use to do that job often has accessibility problems of its own. That is silly, and it costs me real time. I built AMASAMYA to be the tool I wished existed. Everything in it works with a screen reader from start to finish. The results are shown as plain lists, not highlights drawn on the page. Every new version is tested with a screen reader before I release it.
Nobody pays me to work on AMASAMYA. It is free because the only cost was my evenings, and I built it because I needed it. Nobody owns it or gets to tell me what to change.
Professional roles
| Employer | Role |
|---|---|
| Virtusa Consultancy (Mar 2024 to present) | Accessibility Architect. Strategy and architecture across regulated sectors including banking and financial services. |
| Tech Mahindra (Nov 2019 to Mar 2024) | Accessibility Lead and SME (4.5 years). Led accessibility programmes at global technology scale. ACE Award 2023. |
| HCL Technology (Jul 2014 to Oct 2019) | Accessibility Lead and SME (5.5 years). Delivered accessibility programmes at global technology scale. |
| Prakat Solutions (Feb 2011 to Jun 2014) | Accessibility Tester. First accessibility role; foundational work across 250+ websites, applications, and documents. |
| Mphasis, an HP Company (Apr 2009 to Sep 2010) | Technical Support Engineer (L2). Managed complex customer queries related to HP hardware, software, and operating systems via email support. Pre-accessibility career, before the switch into accessibility testing. |
How I work
When I check a site, I combine three things: automated tools (AMASAMYA itself, plus other trusted ones), hands-on testing with the screen readers real users actually use, and walking through the whole page with only the keyboard. I write up what I find in plain English so the developer who has to fix it does not need to run a screen reader themselves to understand what I mean.
I write about accessibility on LinkedIn, where most of the conversation in this field happens. If you want to follow along or reach me, the 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/AMASAMYA/AMASAMYA.