Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

App design · 17 Nov 2026 · 5 min read

App accessibility basics for iOS and Android

Accessible apps work for people who see, hear, move or think differently, and they tend to be better for everyone else too. Here is where to begin.

The short answer

App accessibility means designing and building an app so people with different vision, hearing, movement and thinking needs can use it. It covers screen reader labels, text size, contrast, touch targets, captions and motion. You can test much of it yourself by switching on VoiceOver or TalkBack and enlarging the text.

What app accessibility covers

App accessibility is the practice of making an app usable by people with a wide range of abilities and in a wide range of situations. Some users are blind or have low vision. Some are deaf or hard of hearing. Some have limited movement, tremor or use one hand. Some have dyslexia, memory problems or attention difficulties. Others are simply in bright sun, on a noisy train or holding a baby.

The main areas are: how the app is read aloud by a screen reader, how text and layouts respond to larger sizes, how colours and contrast are chosen, how big and how well spaced the touch targets are, how audio and video are captioned and how motion is handled. Both platforms publish their own guidance, and the international web guidelines are often used as a reference for the thinking, even though they were written for websites.

How screen readers use an app

On iPhone the built-in screen reader is VoiceOver, and on Android it is TalkBack. A user swipes from one element to the next, and the phone reads out what each one is. A button might be announced as, for example, search button. A switch is announced with its state. The user double-taps to activate whatever has focus.

The screen reader can only say what the app tells it. That means each interactive element needs a short, meaningful label, a role such as button or heading, and a state where relevant, such as selected or off. An icon-only button with no label is read out as just button, or sometimes as nothing helpful, which makes it a dead end.

The order matters as well. Focus normally follows the visual order from top to bottom, but custom layouts can scramble it. Decorative images should be skipped, and grouped elements, such as a product card with a title and a price, should be read in a sensible chunk instead of one fragment at a time.

The practical basics for designers and developers

  • Labels. Give every control that has no visible text a clear spoken label. Make labels describe the action, not the picture.
  • Headings. Mark screen and section titles as headings, so screen reader users can jump between them.
  • Text size. Respect the user's system text size setting, and make layouts wrap and scroll instead of cutting text off.
  • Contrast. Choose text and background colours with enough difference, and check them against the contrast guidance in the current web accessibility guidelines.
  • Colour is not the only signal. If an error is shown only in red, people who cannot tell red from other colours will miss it. Add an icon or text.
  • Touch targets. Make tappable areas large enough and spaced out. Both platforms publish minimum sizes, which are worth checking in their current documentation.
  • Captions and transcripts. Provide captions for video and a text alternative for audio.
  • Motion. Honour the system setting to reduce motion, and avoid flashing content.
  • Time limits. Give people enough time to read and act, or let them extend it.
  • Forms. Link every field to a visible label and give clear error messages that say what to fix.

What you can test yourself

You do not need a specialist to spot the biggest problems. Try these on a real phone, on the main journeys of your app:

  1. Turn on the screen reader, then close your eyes or use the screen-off option if the phone offers it. Try to sign in, find an item and complete the main action.
  2. Set the system text size to the biggest setting and look for cut-off text, overlapping items and buttons that have moved out of reach.
  3. Switch on dark mode and any high contrast or bold text options, and check that nothing disappears.
  4. Turn on reduce motion and check that animations are toned down.
  5. Try the whole app with one hand, then with the phone held at arm's length.
  6. Look at the app in greyscale, to check that meaning does not depend on colour alone.
  7. Turn on captions and play every video.

Write down what fails and fix the blockers first, which are the places where a user cannot continue at all. Then repeat after each release. Expert review and testing with disabled users find far more than a self-check, and are worth planning for when the product matters to many people.

Bring accessibility into the process early

Fixing accessibility at the end is slow and expensive, because it touches the structure of every screen. It is much easier to build it into design reviews, into the definition of done for each feature and into the checklist before each release. Add a few accessibility cases to the beta; include testers who use screen readers or large text.

Our guide to asking for camera, location and contacts permissions well applies here too. The system dialogs are already accessible, but your own explanation screens are not, so test them with the screen reader.

Rules, reviews and legal questions

Accessibility requirements can come from law, from contracts and from the store. Rules differ by country, apply differently to different kinds of organisation and change over time, so ask a qualified lawyer or the official source about your own situation. Do not assume that passing an automated check means an app is compliant, because automated tools find only a part of the problems.

The stores publish their own guidance, and a very broken experience can lead to poor reviews even where no review rule is involved. See why apps get rejected from app stores for the review side.

Keep it working after launch

Accessibility regresses quietly. A new screen ships without labels, a redesign shrinks the touch targets and a new library breaks focus order. Treat accessibility checks as part of every release, and include them in the plan described in app maintenance after launch. New system versions bring new accessibility settings and sometimes change old ones, so read release notes with that in mind. Each update, including small ones, goes through the process in app updates and versioning.

Store listings can also describe the accessibility features your app supports, if they are true and have been tested; check the current rules for how each store handles this, and read app store optimisation basics for how listing text is used.

If you want accessibility built into a new app from the start, the mobile app development page describes what Liftup Technologies builds.

Related guides

Questions and answers

What does app accessibility cover?

It covers how well people with different vision, hearing, movement and thinking needs can use the app. The main areas are screen reader labels and order, text size, contrast, touch targets, captions, motion, forms and time limits.

How do screen readers use an app?

VoiceOver on iPhone and TalkBack on Android move focus from one element to the next and read out each element's label, role and state. They can only say what the app provides, so unlabelled icons and tangled focus order become dead ends.

What can I test myself?

Turn on the screen reader and try the main journeys without looking. Set text to its biggest size, try dark mode and reduce motion, use the app one-handed and in greyscale, and play videos with captions. Fix the places where a user cannot continue first.

Is app accessibility a legal requirement?

It can be, depending on the country, the type of organisation and the contract. Rules differ and change, so ask a qualified lawyer or the official source. Passing an automated check does not prove compliance.

Do web accessibility guidelines apply to apps?

They were written for websites, but their principles on contrast, text alternatives, keyboard and focus, and clear forms are widely used as a reference for apps. Each platform also publishes its own guidance, which you should check.

When should accessibility work start?

At design stage. Adding it at the end touches every screen and costs far more. Put it in design reviews, in the definition of done for each feature and in the pre-release checklist.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote