Mobile app accessibility: a practical guide for iOS and Android

How to make mobile apps usable for people with disabilities, using platform accessibility features, good design and testing with screen readers.

By the UK Technology Hub teamPublished 4 minute read

The short answer

An accessible app works with screen readers like VoiceOver and TalkBack, supports larger text sizes, has enough colour contrast, uses touch targets large enough to tap easily, doesn't rely on colour or gestures alone, captions media and respects reduced motion settings. Build with native accessibility features from the start and test with real assistive technology.

Many people rely on accessibility features on their phones: screen readers, larger text, voice control, switch access and more. Accessible apps serve them, reach more customers and often meet legal requirements. The good news is that iOS and Android provide strong accessibility tools; your app just needs to use them well.

Standards to aim for

The Web Content Accessibility Guidelines (WCAG) are widely applied to mobile apps, with level AA as the common target. Apple and Google also publish accessibility guidelines for their platforms. Some laws and contracts require accessible apps, particularly for public services and large organisations.

Screen readers

VoiceOver on iOS and TalkBack on Android read screen content aloud and let users navigate by swiping.

  • Label every control: icons need text labels, such as "Search" for a magnifying glass.
  • Describe images that convey information; mark decorative images to be ignored.
  • Group related elements so they're read together sensibly.
  • Set a logical reading order.
  • Announce changes, such as errors or loading states.
  • Use native components where possible; they come with accessibility built in.

Text size

Users can increase text size system-wide. Support Dynamic Type on iOS and scalable text on Android so text grows with user settings, and test layouts at the largest sizes to make sure nothing is cut off or overlaps.

Colour and contrast

  • Text should meet WCAG contrast ratios: at least 4.5:1 for normal text.
  • Don't rely on colour alone to convey information, such as red for errors; add icons or text.
  • Test in dark mode and with system colour filters.

Touch targets

Small buttons are hard to tap, especially for people with motor impairments. Apple recommends minimum targets of 44 by 44 points, and Android recommends 48 by 48 density-independent pixels. Leave enough space between targets.

Gestures and motion

  • Provide alternatives to complex gestures like multi-finger swipes or long presses.
  • Respect the system's reduce motion setting.
  • Avoid flashing content.
  • Don't use time limits without ways to extend them.

Forms

  • Clear labels for every field.
  • Error messages that explain how to fix problems.
  • Appropriate keyboard types.
  • Support for autofill.

Media

  • Captions for videos.
  • Transcripts for audio content.
  • Controls to pause media.

Testing

  1. Use VoiceOver and TalkBack to complete key tasks.
  2. Test with maximum text size.
  3. Check contrast with tools.
  4. Use accessibility scanners: Xcode's Accessibility Inspector and Google's Accessibility Scanner flag common issues.
  5. Test with switch control and voice control for key flows.
  6. Involve users with disabilities in testing.

Our guide to accessibility testing tools covers web tools that complement mobile testing.

Accessibility in cross-platform apps

Frameworks like React Native and Flutter support accessibility properties, but developers must use them. Test on both platforms, as behaviour can differ.

Accessibility and localisation

Accessible apps are easier to localise, and localised apps must stay accessible. Labels need translating, and longer text in other languages must fit at large sizes. Our guide to app localisation explains more.

Build it in early

Fixing accessibility after launch costs far more than designing for it. Include accessibility in design reviews, component libraries, definitions of done and testing.

Common accessibility mistakes in apps

  • Icon-only buttons with no labels.
  • Custom controls that screen readers can't operate.
  • Text that doesn't scale or gets cut off at larger sizes.
  • Important information shown only in images.
  • Gestures with no alternative.
  • Low-contrast text on brand-coloured backgrounds.
  • Error messages that aren't announced to screen readers.

Accessibility statements and feedback

Publish an accessibility statement for your app, describing the standard you aim for and known issues, and give users an easy way to report problems. Respond quickly; feedback from people using assistive technology is invaluable.

Small fixes, big impact

Many accessibility improvements are quick: adding labels to icon buttons, increasing tap target sizes, fixing contrast and supporting larger text. Start with the screens people use most, such as sign-in, home and checkout.

How we help

Our mobile app development team builds accessible iOS and Android apps, our UI/UX design team designs accessible components and flows, and our app development service includes accessibility testing with VoiceOver and TalkBack.

Frequently asked questions

Do mobile apps need to meet WCAG?

WCAG is widely used as the benchmark for app accessibility, and some laws and contracts require it.

How do I test my app with a screen reader?

Turn on VoiceOver on iOS or TalkBack on Android and try to complete key tasks without looking at the screen.

Are cross-platform apps accessible?

They can be, if developers use the accessibility properties provided by frameworks like React Native and Flutter.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides