Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Users say my app is not accessible and I do not know where to start

Short answer

An accessibility complaint usually points to a few concrete gaps: controls without labels, tiny tap targets, low contrast, or flows a screen reader cannot finish. Both stores publish testing guidance. Reply politely, ask which screen failed, and have the main flows tested with the phone's own screen reader.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A user wrote to support that they cannot complete a purchase or sign-in with a screen reader.
  • Someone left a review saying the text is too small or the buttons are hard to hit.
  • A customer or partner asked for an accessibility statement and I have nothing to send.
  • My developer says the app is fine because it works on their phone.
  • I do not know whether the complaint is about one screen or the whole app.

Why does this happen?

  1. Controls have no spoken label

    Android's testing guide lists content labelling as a category: elements without a label that describes their purpose. A screen reader then says only 'button', so the person cannot tell what it does.

  2. Tap targets and contrast were never checked

    The same guide lists touch targets smaller than recommended and text and background colours with too little contrast. Both pass unnoticed when the app is only tried by people with good eyesight and steady hands.

  3. Nobody tried the app with a screen reader

    Android's guide says manual testing with TalkBack lets you experience the app as the user does, and asks whether every element can be reached and the main workflows completed. An app that was never tested this way often has dead ends.

  4. The app was built from a design that ignored it

    Custom-made buttons, icons without text and gesture-only actions look fine but expose nothing to assistive tools. They are cheap to build in and costly to retrofit.

What can I do about it today?

  1. Reply and ask for specificsThank the person, say you are looking into it, and ask which screen, which phone and which assistive feature they use. Do not argue or promise a date.
  2. Try the main journey yourselfOn your own phone switch on the screen reader and try to sign in and do the one thing customers pay for. Android's guide says to check that you can reach every element and complete the main workflows.
  3. Save the evidenceKeep the complaint, the screens named and your own notes. They become the to-do list.
  4. Check the store dashboardsOn Google Play the pre-launch report has an Accessibility tab showing touch target size, contrast and content labelling findings. Ask whoever holds your Play Console to share it.
  5. Do not publish an accessibility claim yetWrite nothing public about being accessible until the main flows have been tested. For legal obligations in your country, ask a lawyer.

When should I bring someone in?

  • The complaint comes from a regulator, a lawyer or a large customer's procurement team.
  • The sign-in or checkout screen cannot be completed at all with a screen reader.
  • Your developer cannot say which screens have labels and which do not.

How do I handle it?

  1. Test the real flowsI run sign-in, the core task and payment with TalkBack on Android and VoiceOver on iPhone, and write down every point where it breaks.
  2. Use the automated reports as a second opinionAccessibility Scanner and the Play pre-launch report catch labels, contrast and target sizes. They are a start, not a pass mark.
  3. Fix by screen, most used firstLabels, order of focus, target sizes and contrast are fixed screen by screen, starting with the journey that earns your money.
  4. Add it to the release checklistEach later update gets the same short screen reader check so the gaps do not return.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does passing an automated scan mean my app is accessible?

No. Android's own guide says to use manual testing, analysis tools, automated tests and user testing together.

Is this legal advice?

No. Whether a law applies to your app depends on your country and business, and a lawyer should answer that.

Which assistive tools matter most?

The screen readers built into the phone are the first thing to test: TalkBack on Android and VoiceOver on iPhone.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.