Contents
Accessible app development means that people with visual, hearing, motor or cognitive impairments can use your app fully – with a screen reader, large text or switch control. iOS and Android offer mature tools for this; what matters is using them consistently from the start. This article covers the key measures, typical mistakes and how to test accessibility.
Why accessibility is on the agenda now
Since 28 June 2025, Germany's Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG), which implements the European Accessibility Act, has applied. It obliges many providers of certain products and services – for example in e-commerce, banking or passenger transport – to offer accessible digital services, apps included. Whether and to what extent your app is affected depends on factors such as sector, audience and company size; our article on the BFSG and what it means for apps explains the details. This article is not legal advice.
Regardless of legal duties, accessibility pays off: larger text, good contrast and clear interaction also help older users, people with temporary impairments or anyone using the app in bright sunlight.
The technical foundation: WCAG and EN 301 549
The Web Content Accessibility Guidelines (WCAG) serve as the reference and, despite the name, are applied to apps as well. The European standard EN 301 549 largely refers to the WCAG level AA criteria for software and mobile applications. The four principles are:
- Perceivable: information is accessible to all senses, e.g. images with text alternatives, sufficient contrast.
- Operable: all functions work with different input methods, and time limits can be adjusted.
- Understandable: text, navigation and error messages are clear and predictable.
- Robust: the app works reliably with assistive technologies such as screen readers.
Key measures by area
| Area | Requirement | iOS implementation | Android implementation |
|---|---|---|---|
| Screen reader | All elements have meaningful labels, roles and states | VoiceOver; accessibilityLabel, traits | TalkBack; contentDescription, semantics in Compose |
| Text size | Text scales with system settings without breaking the layout | Dynamic Type with text styles | Font sizes in sp, flexible layouts |
| Contrast | At least 4.5:1 for normal text, 3:1 for large text and controls | Check colour tokens for light and dark mode | Same principle, check Material colour schemes |
| Touch targets | Sufficiently large, well-separated controls | Apple recommends at least 44 × 44 pt | Google recommends at least 48 × 48 dp |
| Focus and order | Logical reading order, sensibly grouped elements | Grouping with accessibility containers | Traversal order and merging in semantics |
| Motion | Animations can be reduced, no flashing | Respect "Reduce Motion" | Respect animation settings |
Flutter and React Native each provide their own accessibility properties (e.g. Semantics widgets, or accessibilityLabel and accessibilityRole) that map to the native interfaces. Accessibility is therefore achievable cross-platform as well, but must be tested on both systems.
Typical mistakes – and how to avoid them
- Icons without labels: a bin icon is read out as just "button". Fix: meaningful labels such as "Delete entry".
- Information conveyed only by colour: a red border as the only error indicator. Fix: add text and an icon.
- Fixed heights for text containers: text gets cut off at large sizes. Fix: dynamic layouts and testing at maximum text size.
- Custom controls without semantics: home-made toggles or sliders are invisible to assistive technologies. Fix: use standard components or set role, value and actions explicitly.
- Gestures without alternatives: swipe-to-delete is unreachable for some users without an alternative. Fix: add an action via menu or accessibility action.
- Vague error messages: "Invalid input" helps nobody. Fix: state exactly what to do and move focus to the field.
- Time limits: messages that disappear automatically or tight session timeouts. Fix: allow more time or keep messages until dismissed.
Building accessibility into the development process
Retrofitting is considerably more expensive than doing it right from the start. This approach has proven itself:
- Design: a colour palette with verified contrast, text styles instead of fixed sizes, states not distinguished by colour alone.
- Component library: build accessibility properly into reusable components once instead of solving it on every screen.
- Definition of done: a user story is only complete once it has been tested with a screen reader and large text.
- Automated checks: tools such as Xcode's Accessibility Inspector, Android's Accessibility Scanner and accessibility checks in UI tests catch many problems early. Coding agents can support such checks, as described in agentic coding and accessibility.
- Manual testing: automation doesn't find everything. A complete run through the core flows with VoiceOver and TalkBack is essential, ideally complemented by tests with people who rely on assistive technology.
Acceptance checklist
- All core flows (registration, login, purchase, contact) are fully usable with VoiceOver and TalkBack.
- At the largest system text size, no text is truncated and everything remains reachable.
- Contrast meets WCAG AA values in light and dark mode.
- All functional images and icons have text alternatives; decorative elements are ignored.
- Forms have visible labels and understandable error messages.
- Touch targets meet platform recommendations.
- Animations respect the system setting for reduced motion.
- An accessibility statement is prepared where required.
These points can go straight into your acceptance criteria – see acceptance testing and quality assurance.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
Accessible apps are not the result of an audit at the end of a project but of consistent implementation in design, components and testing. With VoiceOver, TalkBack, Dynamic Type and semantics APIs, the platforms provide everything you need; the key is to use them systematically. If you are planning an accessible app or want to retrofit an existing one, our offer wizard leads to a fixed-price quote after a free analysis.
Frequently Asked Questions
Which standard applies to accessible apps?
The WCAG level AA criteria serve as the reference; the European standard EN 301 549 largely refers to them for software and mobile applications.
Is accessibility possible with Flutter or React Native?
Yes. Both frameworks map their accessibility properties to VoiceOver and TalkBack, but testing on both platforms is still required.
How much extra effort does accessibility require?
Planned from the start, the extra effort is usually moderate because much of it is solved in reusable components. Retrofitting is considerably more work, especially with custom controls.
Are automated tests enough for accessibility?
No. Automated tools find many technical errors but cannot judge whether flows are understandable and read out sensibly. Manual screen reader testing is indispensable.