Foldwren

Accessibility in mobile apps

The basics of mobile app accessibility, covering text size settings, screen readers, colour contrast, touch targets and captions.

An accessible app is one that people can use regardless of how well they see, hear, move or concentrate. That covers people with permanent disabilities, and also a much wider group: anyone who has bumped up their phone's text size as their eyesight changed, anyone reading a screen in bright sun, anyone holding a baby in one arm.

Most accessibility work is ordinary good design done carefully. Here are the five areas that matter most on a phone.

Text size settings

Both iPhone and Android let people set a preferred text size for the whole device. Plenty do. An accessible app respects that setting, so when someone asks for larger text, your app's text grows too.

This is where many apps break. Text set at a fixed size ignores the preference entirely. Or the text grows but the boxes around it do not, so words are cut off, overlap, or vanish behind buttons.

What to ask for:

  • Text that scales with the device setting.
  • Layouts that stretch and reflow, with buttons growing taller and rows stacking when needed.

A quick test: turn your phone's text size up to the largest setting and open your app. If you can still read and complete the main task, you are in good shape.

Screen readers

People who are blind or have low vision often use a screen reader, built into the phone, that speaks whatever is on screen. On iPhone it is called VoiceOver. On Android it is TalkBack. The person swipes from item to item and double taps to activate.

For this to work, every element needs a sensible label in the code. A screen reader meeting a cart icon with no label might say only "button". With a label it says "Cart, two items, button".

The essentials:

  • Label every icon and image button with what it does.
  • Describe meaningful images. A photo of a menu item needs a short description. A decorative swirl should be hidden from the reader.
  • Keep a logical reading order. Top to bottom, heading before content.

You can try this yourself. Switch on the screen reader in your phone's accessibility settings, close your eyes, and try to book an appointment in your own app. It is humbling and very informative.

Colour and contrast

Low contrast text is one of the most common accessibility failures, and it affects nearly everyone at some point. Pale grey on white may look refined on a designer's large monitor. On a phone outdoors it disappears.

The widely used Web Content Accessibility Guidelines set minimum contrast levels between text and its background. For normal sized text the usual target is a ratio of 4.5 to 1. Free contrast checkers will tell you whether a pair of colours passes, and your designer should be using one.

One more rule: never rely on colour alone. A red border on a faulty field means nothing to someone who cannot distinguish red. Add an icon and a text message. The same goes for charts and status labels.

Brand colours sometimes fail contrast checks, particularly yellows, light greens and oranges with white text. The fix is usually to use a darker shade for text and buttons while keeping the brand colour for backgrounds and accents.

Touch targets

Small, crowded buttons are hard for everyone and impossible for some. People with tremors, arthritis or large fingers need room.

Apple and Google both recommend a minimum tappable size of roughly 44 to 48 points square, about the pad of a fingertip.

  • Make the tappable area generous even when the visible icon is small.
  • Leave space between neighbouring targets.
  • Do not make swipes, long presses or pinches the only way to do something. Always offer a plain button as well.

Captions and sound

If your app includes video or audio, people who are deaf or hard of hearing need another way in. So do the many people who watch with the sound off in a waiting room or on a train.

  • Caption every video that has speech. Automatic captions are a starting point and need checking, especially for names and technical terms.
  • Do not use sound as the only signal. If a chime means "order ready", show a message and trigger a vibration too.

A short checklist for your project

Raise accessibility at the start, not the end. Retrofitting it after launch costs far more than building it in. Ask your designer and developer:

  • Does text scale with the device setting, and have the layouts been tested at the largest size?
  • Has every screen been tried with VoiceOver and TalkBack?
  • Do all text and button colours pass a contrast check, in light and dark mode?
  • Are all touch targets at least the recommended minimum size?
  • Are videos captioned, and is nothing communicated by colour or sound alone?
  • Does the app respect the phone's reduce motion setting, for people who feel unwell with heavy animation?

In Australia, businesses also have obligations under disability discrimination law that can extend to digital services. The detail depends on your situation, so look at the official guidance from the Australian Human Rights Commission or ask an adviser. Legal reasons aside, an app more people can use is an app with more customers, and nearly every item on this list makes it nicer for everyone else too.

Your order