Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app does not work properly with VoiceOver or TalkBack

Short answer

When VoiceOver or TalkBack gets stuck in an app, the cause is usually missing labels, a reading order that does not match the screen, or controls the reader cannot activate. Turn the screen reader on, try your main journey, and note exactly where it stops.

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

Does this sound like your situation?

  • The screen reader says only 'button' or 'image' on many controls.
  • It reads things in a confusing order, or skips parts of the screen.
  • A pop-up, error message or confirmation is never spoken aloud.
  • A user cannot get past the sign-in or the payment screen.
  • Some actions only work by swiping or dragging, with no alternative.

Why does this happen?

  1. Elements are missing descriptive labels

    Android's guide asks whether the spoken feedback for each element conveys its content or purpose. Icon-only buttons without a label fail this.

  2. Focus order does not follow the layout

    The same guide lists traversal order that does not match the logical arrangement of elements as an implementation problem that makes it harder for accessibility services.

  3. Temporary messages are not announced

    Android's guide tells testers to check whether alerts and other temporary messages are read aloud. Snack bars and error banners often are not.

  4. Gestures with no alternative

    Switch Access testing in the guide asks whether everything available through touch gestures is also available as selectable controls or custom actions.

What can I do about it today?

  1. Turn the reader onOn Android: Settings, Accessibility, TalkBack, On. Android notes that a tutorial opens the first time. On an iPhone use the VoiceOver setting under Accessibility. Learn the tutorial first or you will lose your way.
  2. Walk the core journeyOpen the app, swipe from element to element and try to sign in and complete the main task. Write down the screen where it breaks.
  3. Record a short screen videoRecord the screen with the reader on. A real recording tells a developer more than a description.
  4. Send details, not a verdictGive your developer the phone model, the OS version and the screens. Ask which controls have labels, not whether the app is accessible.

When should I bring someone in?

  • The sign-in, checkout or booking screen cannot be completed with a screen reader.
  • Your developer says accessibility is not possible in the framework the app uses.
  • The problems return after each update.

How do I handle it?

  1. Reproduce with both readersI run the flow with TalkBack and VoiceOver on real phones, because behaviour differs between platforms.
  2. Fix labels, order and actionsDescriptions, reading order and custom actions are added in the shared code where possible and natively where a plugin falls short.
  3. Announce state changesErrors, confirmations and loading states are made audible, not only visible.
  4. Retest and keep a checklistThe same journey is checked on the build before release.

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?

Is a Flutter app a problem for screen readers?

Not by itself. The same labelling and ordering work applies, and I test it on real devices rather than assume.

Do I need a user with a disability to test?

Android's guide lists user testing as one of four approaches and suggests local organisations as a way to find testers.

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.

Next step

Want this off your desk?

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