Screen reader accessibility audits

I find what stops blind and low-vision people from using your app or website, and show your developers exactly how to fix it.

Why work with me

I use a screen reader every day. I test with NVDA, TalkBack and VoiceOver the way your blind users actually work, not only with automated tools.
I'm a software architect with 12 years of experience, so every problem comes with a fix your developers can apply.
I build accessible products myself. My RedZoc apps include eSpeak NG Text-to-Speech, with over 100,000 installs, and redzoc.com publishes its own accessibility statement. I also contribute Indian-language fixes to the open-source eSpeak NG speech engine.

Who it's for

Product teams that need their app or website to work with screen readers, or need to meet accessibility requirements such as WCAG 2.2: banks and fintechs, edtech, e-commerce, and suppliers to government.

For teams in Europe

The European Accessibility Act has applied since 28 June 2025 to online shops, banking, e-books, transport ticketing and communication services sold in the EU. Its standard, EN 301 549, uses WCAG at level AA. My reports map every finding to WCAG 2.2, so they show where you stand and what to fix first.

What you get

Up to 10 key screens or pages of one product, on one platform: a website, an Android app or an iOS app.
Automated checks, plus manual testing with a screen reader on real tasks like signing up, searching and paying.
Colour contrast, text size and (for websites) keyboard checks.
A written report. Each problem includes where it is, what happens for a screen-reader user, how serious it is, the WCAG 2.2 criterion, and how to fix it, with code examples.
A one-page summary for managers.
One video call to walk through it, and questions answered by email for two weeks.
Delivered within two weeks of receiving access.

How it works

Email me your product, the platform, and the screens that matter most.
I confirm the scope and a start date, and you share access (a test account is fine).
You get the report, the summary and a walkthrough call.
Your developers make the fixes. I can help if you'd like (see below).
Optionally, I retest the same screens to confirm everything works.

Prices

Introductory prices for my first clients, in exchange for permission to publish an anonymised case study.

Audit, up to 10 screens: ₹30,000 (India), €550 (Europe) or US$600 (elsewhere)
Retest of the same screens after fixes: ₹10,000, €180 or US$200
Fix support (reviewing your fixes, calls, pairing on tricky parts): ₹2,500, €45 or US$50 an hour, in blocks of four hours
Hands-on fixes for small, well-defined jobs: quoted separately

I take on a limited number of audits each month, so please get in touch early.

What an audit is not

It's not a legal certification or a guarantee of compliance, and it covers the screens agreed, not the whole product. Larger audits are quoted separately.

A sample finding

"Pay now" button is announced only as "Button"

Where: Checkout screen, Android app

What happens: TalkBack says "Button, double-tap to activate". A blind user can't tell what the button does, so they can't complete payment.

Severity: Critical: it blocks a key task.

WCAG 2.2: 4.1.2 Name, Role, Value (Level A)

Fix: the button is an image button without a label. Add android:contentDescription="Pay now", or in Jetpack Compose, Modifier.semantics { contentDescription = "Pay now" }.

Read a full sample report, from an audit of my own Android app.

Questions

Can you test in Indian languages?: Yes. Interfaces in Hindi, Malayalam and other Indian languages can be tested too.
Will you sign an NDA?: Yes.
How do you handle our data?: Test accounts and anything you share are used only for the audit and deleted afterwards. I can sign your data processing agreement.
Is it remote?: Yes, fully remote. Clients anywhere are welcome.
Can you audit more than 10 screens?: Yes, quoted to your scope.

Get in touch

Email hello@rameesmuhammed.com with your product, platform and the screens that matter most.