Mobile App Accessibility: Designer and Founder Checklist
Mobile app accessibility made practical: contrast, touch targets, Dynamic Type, VoiceOver and TalkBack labels, motion and a full pre-launch checklist.

This guide is for founders, PMs and designers who want their app to work for everyone who downloads it, without hiring an accessibility consultant on day one. You get the rules that matter on iOS and Android, the numbers to design against, how to test with the tools already on your phone, and a checklist you can run before every release.
TL;DR: Most mobile accessibility wins come from five things: text contrast of at least 4.5:1, touch targets of at least 44pt on iOS and 48dp on Android, layouts that survive large text sizes, a meaningful label on every control for VoiceOver and TalkBack, and never relying on colour or motion alone. Design for these from the first wireframe and test with the built-in screen readers before launch.
Why mobile app accessibility is a product decision, not a compliance task
The World Health Organization estimates that around 1.3 billion people, roughly one in six, live with a significant disability. Add the much larger group with situational limits (bright sunlight, one hand on a train strap, a cracked screen, reading glasses left at home) and accessibility stops being an edge case. It is how a large share of your users experience your app on an ordinary day.
There is also a legal side. In the US, the ADA has been applied to apps and websites in a steady stream of lawsuits. In the EU, the European Accessibility Act has applied since June 2025 to a range of consumer services, including e-commerce and banking, and it points to the harmonised standard EN 301 549, which in turn references WCAG. If you sell into either market, assume someone will eventually ask whether your app meets WCAG 2.x Level AA.
The good news: almost everything in this guide costs nothing if you decide it at the design stage, and a lot if you retrofit it after launch.
The standards in one table
You do not need to read WCAG end to end. You need to know which document says what.
| Source | What it covers | What you take from it |
|---|---|---|
| WCAG 2.2 (W3C) | Testable success criteria for web content, widely applied to apps | Contrast ratios, target size, labels, focus, motion, timing |
| Apple Human Interface Guidelines, Accessibility | iOS, iPadOS, watchOS, visionOS guidance | 44 by 44pt targets, Dynamic Type, VoiceOver, Reduce Motion |
| Material Design 3, Accessibility | Android and Material guidance | 48 by 48dp targets, TalkBack, font scaling in sp |
| EN 301 549 | EU procurement and EAA standard | References WCAG for software including mobile apps |
Level AA is the target almost every law and contract points to. Level AAA is aspirational for most products.
1. Colour and contrast
Low-contrast text is the single most common accessibility failure on the web, according to WebAIM's annual analysis of the top million home pages, and apps follow the same pattern. It is also the easiest to fix.
The numbers
| Element | WCAG AA minimum | Notes |
|---|---|---|
| Body text | 4.5:1 | Against its actual background, including images and gradients |
| Large text | 3:1 | 18pt regular or 14pt bold and above, in WCAG's definition |
| UI components and icons | 3:1 | Button borders, input outlines, toggle states, meaningful icons |
| Disabled controls | No requirement | But make sure users can tell they are disabled |
| Placeholder text | 4.5:1 if it carries meaning | Better: use a persistent label above the field |
Check pairs as you pick them with our contrast checker, which also tests against APCA and simulates colour-blindness. If you are building a palette from scratch, our guide to choosing a mobile app color palette shows how to build contrast into your tokens instead of fixing it screen by screen.
Never use colour alone
Around one in twelve men has some form of colour vision deficiency, most commonly red-green. If the only way to tell an error from a success is red versus green, those users lose the information.
- •Pair error colour with an icon and a text message: "Card number is too short."
- •Mark the selected tab with a filled icon or indicator, not just a tint.
- •In charts, use patterns, direct labels or different line styles alongside colour.
- •In status pills, include the word ("Paid", "Overdue").
Dark mode needs its own check
A palette that passes in light mode often fails in dark mode, especially secondary text and borders. Test both themes. A common trap is pure white text on pure black, which causes halation for some readers; an off-white on a dark grey is easier to read.
2. Touch targets and spacing
Small targets hurt everyone with limited dexterity, tremor, large fingers or a moving bus. The platform rules are clear:
| Platform | Minimum target | Recommended spacing |
|---|---|---|
| iOS (Apple HIG) | 44 by 44pt | Enough that adjacent targets are not hit by mistake |
| Android (Material 3) | 48 by 48dp | At least 8dp between targets |
| WCAG 2.2 AA (2.5.8) | 24 by 24 CSS px, or adequate spacing | The legal floor, not a design target |
| WCAG 2.2 AAA (2.5.5) | 44 by 44 CSS px | Close to the platform guidance |
The visible element can be smaller than the target. A 24pt icon can sit inside a 44pt tappable area. What matters is the hit region, so specify it in your handoff.
Common offenders:
- •Close "X" buttons in the corner of modals and paywalls.
- •Inline text links in dense paragraphs ("Terms" and "Privacy" next to each other).
- •Star ratings, steppers and small chevrons.
- •Icon rows in a toolbar with no spacing.
Thumb reach
Accessibility and ergonomics overlap. Put primary actions in the lower half of the screen where thumbs reach easily, and avoid placing destructive actions next to frequent ones.
3. Text size: Dynamic Type and font scaling
Many users increase their system text size. On iOS this is Dynamic Type; on Android it is the font size and display size settings, with text specified in sp so it scales. If your layout breaks at larger sizes, you have locked these users out.
What to design for
- •Use the platform text styles. On iOS, map your type scale to text styles like Body (17pt at the default size), Headline, Subheadline and Caption. On Android, use the Material type roles (Body Large is 16sp) in sp, never dp. Our mobile app typography guide covers the full scales.
- •Design at least two sizes. Mock up your key screens at the default size and at one of the largest accessibility sizes. On iOS, the largest accessibility sizes make body text dramatically bigger.
- •Let text wrap. Avoid fixed-height containers for text. Buttons should grow vertically; labels should wrap to two or three lines instead of truncating.
- •Stack when it gets tight. A horizontal row of icon, title and value often needs to stack vertically at large sizes. Apple's own Settings app does this.
- •Do not scale everything. Tab bar labels and navigation titles are often handled by the system (iOS shows a large preview when you long-press a tab bar item at accessibility sizes). Body content is where scaling matters most.
Readable text in general
- •Body text at 16 to 17pt or larger.
- •Line height of roughly 1.3 to 1.5 times the font size for paragraphs.
- •Left-aligned body text in left-to-right languages; avoid justified text.
- •Avoid all caps for anything longer than a short label.
Build your scale up from a readable base size rather than down from a display size.
4. Screen readers: VoiceOver and TalkBack
VoiceOver (iOS) and TalkBack (Android) read the screen aloud and let users move through elements with swipes, then activate them with a double tap. Designing for them is mostly about giving developers the right information.
Every control needs a label, role and state
| Element | Bad label | Good label |
|---|---|---|
| Icon button with a heart | "Button" or "heart_outline" | "Save to favourites" (state: "not saved") |
| Avatar in the top bar | "Image" | "Profile and settings" |
| Play button | "Play button button" | "Play" (role is announced automatically) |
| Product card | Each element read separately | "Linen shirt, 39 dollars, 4.5 stars" as one element |
| Progress bar | Silence | "Step 2 of 4" |
Rules of thumb for labels:
- •Describe the action or content, not the icon. "Search", not "magnifying glass".
- •Do not include the role ("button", "tab"); the screen reader adds it.
- •Keep labels short; put extra detail in a hint if needed.
- •Decorative images should be hidden from screen readers entirely.
Reading order and grouping
Screen readers move in a logical order, usually top-left to bottom-right. Custom layouts, overlapping cards and absolutely positioned elements can scramble this.
- •Annotate the intended focus order on complex screens, such as dashboards with cards.
- •Group related elements (an image, title and price in a card) into one focusable element where it makes sense.
- •Make sure modals and bottom sheets trap focus while open and return focus to the trigger when closed.
Announce changes
When something changes without the user moving focus (a toast appears, a form error is shown, a cart total updates), the screen reader needs an announcement. Mark these in your design notes: "Announce: Item added to cart."
Headings
Both screen readers let users jump between headings. Mark section titles as headings in your specs so users can skim a long settings page or article.
5. Forms and input
Forms are where accessibility failures cost conversions directly.
- •Visible labels. Keep a label visible above or inside the field after the user starts typing. Placeholder-only fields lose their meaning the moment someone types.
- •Errors in text, next to the field. "Enter a valid email address", announced to the screen reader, plus an icon. Not just a red outline.
- •Correct keyboard types. Email, number, phone and URL keyboards reduce typing effort for everyone.
- •Autofill and passkeys. Support password managers, one-time code autofill and passkeys. They help users with motor and cognitive disabilities as much as anyone. See our login screen design guide for the full pattern.
- •No time pressure. If a code or session expires, give a clear warning and a way to extend.
- •Avoid puzzle CAPTCHAs. WCAG 2.2 added criteria about accessible authentication; cognitive tests like transcribing distorted text are a barrier.
6. Motion, animation and media
- •Respect Reduce Motion. iOS and Android both let users reduce motion. When it is on, replace parallax, zooms and large slide transitions with fades or instant changes.
- •No flashing. Nothing should flash more than three times per second.
- •Pause controls. Auto-playing carousels and videos need a pause or stop control.
- •Captions and transcripts. Videos with speech need captions; audio content benefits from transcripts.
- •Do not hide meaning in animation. If a shake animation is the only sign of a wrong passcode, add text and a haptic.
7. Gestures and alternatives
Custom gestures are invisible and often impossible for users with motor impairments or screen readers.
- •Every swipe action (swipe to delete, swipe to archive) needs a visible alternative, such as an edit mode or a long-press menu. On iOS, these can also be exposed as custom actions for VoiceOver.
- •Avoid multi-finger and path-based gestures as the only way to do something. WCAG 2.2 requires single-pointer alternatives for dragging movements.
- •Do not disable system gestures like the back swipe or edge swipes without a good reason.
8. Layout and orientation
- •Support both portrait and landscape unless the content genuinely requires one (some users mount devices on wheelchairs in a fixed orientation).
- •Respect safe areas so content is not hidden under the notch, Dynamic Island or home indicator. Check every screen on the smallest and largest devices you support.
- •Keep consistent navigation across screens. Predictable placement is a cognitive accessibility win.
9. Cognitive accessibility
This is the least measurable area and one of the most impactful.
- •Plain language. Write at a level a tired, distracted person can follow.
- •One primary action per screen.
- •Show progress in multi-step flows ("Step 2 of 4").
- •Confirm destructive actions and offer undo.
- •Avoid onboarding that forces users to memorise information from earlier screens.
How to test mobile app accessibility yourself
You do not need special equipment. Every phone already has the tools.
On iOS
- •VoiceOver: Settings → Accessibility → VoiceOver. Set up the Accessibility Shortcut (triple-click the side button) so you can toggle it quickly. Try to complete your core task with your eyes closed.
- •Larger Text: Settings → Accessibility → Display and Text Size → Larger Text. Turn on the larger accessibility sizes and walk through every screen.
- •Reduce Motion, Bold Text, Increase Contrast: all in the same Accessibility menu.
- •Accessibility Inspector: in Xcode, it audits a running app for missing labels, small targets and contrast issues.
On Android
- •TalkBack: Settings → Accessibility → TalkBack. Learn the basic gestures before testing: swipe right to move forward, double tap to activate.
- •Font size and display size: Settings → Display. Set both to the maximum.
- •Accessibility Scanner: Google's free app scans a screen and flags small targets, low contrast and missing labels.
- •Remove animations: in Accessibility settings.
In design files
- •Run contrast checks on every text and background pair in your tokens.
- •Overlay a 44pt or 48dp grid on icon buttons to check targets.
- •Write labels for every icon button directly in your handoff notes.
With real people
Automated tools catch only part of the issues. The rest come from watching people use your app. Include at least one participant who uses a screen reader or large text in your usability testing.
The mobile app accessibility checklist
Run this before every release. Each line is a yes or no.
Visual
- • Body text contrast is at least 4.5:1 in light and dark mode
- • Large text and meaningful icons are at least 3:1
- • Input borders and toggle states are at least 3:1
- • No information is conveyed by colour alone
- • Body text is 16pt or larger at default size
Interaction
- • All targets are at least 44 by 44pt (iOS) or 48 by 48dp (Android)
- • Every swipe or drag action has a visible alternative
- • Primary actions are within easy thumb reach
- • Destructive actions are confirmed or undoable
Text scaling
- • Key screens tested at the largest accessibility text size
- • No text truncated where it carries meaning
- • Buttons and cells grow with text instead of clipping
Screen readers
- • Every interactive element has a label, role and state
- • Decorative images are hidden from screen readers
- • Reading order matches visual order
- • Section titles are marked as headings
- • Toasts, errors and dynamic changes are announced
- • Modals trap focus and return it on close
- • Core task completed end to end with VoiceOver and TalkBack
Forms
- • Persistent visible labels on all fields
- • Error messages in text, next to the field, announced
- • Correct keyboard types and autofill support
- • No time limits without warning and extension
Motion and media
- • Reduce Motion respected
- • Nothing flashes more than three times per second
- • Auto-playing content can be paused
- • Videos with speech have captions
Building accessibility into your workflow
The cheapest moment to fix accessibility is before a screen exists. A few habits make it automatic:
- •Bake it into tokens. Only approve colour pairs that pass contrast. Make the minimum button height 44pt or 48dp in your component library.
- •Wireframe with real content. Long names, long translations and large text break layouts early, when changes are cheap. Our guide on how to wireframe an app covers working with realistic content.
- •Add an accessibility section to every handoff. Labels, focus order, announcements and reduce-motion behaviour, per screen.
- •Make it part of QA. One person runs the checklist above on every release candidate.
If you generate first drafts of screens with AI, including in floow, treat accessibility the same way you would with a human designer's draft: run contrast checks, confirm target sizes and write the screen reader labels before handoff.
FAQ
What is the minimum touch target size for mobile apps?
Apple's Human Interface Guidelines recommend at least 44 by 44 points, and Material Design recommends at least 48 by 48dp. WCAG 2.2 sets a lower legal floor of 24 by 24 CSS pixels at Level AA, but you should design to the platform guidance.
Does WCAG apply to mobile apps?
WCAG was written for web content, but its principles and most success criteria are applied to native apps by regulators, courts and procurement standards. The EU's EN 301 549 explicitly applies WCAG-based requirements to software, including mobile apps.
How do I test my app with a screen reader?
Turn on VoiceOver on iOS or TalkBack on Android from the Accessibility settings, learn the basic swipe and double-tap gestures, then try to complete your core task without looking at the screen. Note anything that is unlabelled, out of order or impossible to reach.
What contrast ratio do I need for buttons?
Button text needs 4.5:1 against the button fill, or 3:1 if it qualifies as large text. The button's own shape needs 3:1 against the surrounding background if its boundary is needed to recognise it as a button.
Is accessibility expensive to add to an app?
It is cheap when designed in from the start, because most requirements are decisions about colour, size, labels and layout. It becomes expensive when retrofitted, since fixing contrast or text scaling after launch can touch every screen.
Design it with floow
Start your next app with accessible defaults instead of fixing them later. Describe your screens in floow and include the constraints, for example: "Design an iOS banking home screen with 17pt body text, 44pt minimum touch targets, text contrast of at least 4.5:1, a layout that works at large Dynamic Type sizes, and clear text labels next to every icon."
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Roundups22 November 2026ScreensDesign Alternatives: 9 Places for Real App ScreensScreensDesign alternatives compared: Mobbin, Page Flows, Refero and more, with what each library is best for and how to turn references into your own screens.By floow.design
Insights21 November 2026Music App Design: Player, Library and DiscoveryMusic app design guide: home and discovery, search, library, mini player, now playing, queue and offline, plus lock screen, car and widget surfaces, with.By floow.design
Insights21 November 2026Search UI Design: Suggestions, Filters and ResultsSearch UI design for mobile apps: entry points, recent and trending states, autocomplete, filter chips and sheets, result layouts and no-results recovery.By floow.design