Your app has to meet the European Accessibility Act, and nobody on your team can see what a screen reader user runs into. We can
An app fails in different places than a website: screens instead of pages, gestures instead of a mouse, system settings instead of browser settings. We test on real devices, with the screen reader built into the operating system, and give you a report per component your developers can act on.
Apps we audited
What we test in an app
Labels, names and reading order
Buttons announced as “button” without saying what they do, icons without an accessible name, decorative images the screen reader picks up anyway. We also check the reading order: in code it often follows the structure of the view, not what the user sees on screen.
Real devices and system tools
- VoiceOver on recent iPhones and iPads
- TalkBack on recent Android devices
- System text size up to the largest setting
- Both orientations
- Reduced motion and other system settings
Actions that only work with a swipe, and targets too small to hit
Actions that only work with a swipe or a long press and have no alternative, and touch targets too small to hit reliably. For someone with a motor impairment or a tremor that is the difference between ordering and not ordering. We test the flows that matter: logging in, creating an account, buying a ticket, completing a payment, with the screen reader only, and check whether error messages are announced and whether you can get back to the field that was wrong.
The most common finding
- Fixed screen heights that cut off content at large text
- Labels truncated behind a button
- Screens designed in Figma that were never checked at 200% text size
EN 301 549 asks more of an app than WCAG does
The benchmark is EN 301 549, the European standard under the EAA. It adopts the WCAG success criteria and adds requirements that do not exist on the web: your app has to follow the text size the user set in the phone settings, and your screens have to work in both orientations. Those two points produce findings in most apps we test. We test against WCAG 2.2, one version ahead of the standard, at no extra cost.
How we get the app
- iOS: TestFlight or the App Store
- Android: an APK or the Play Store
- Native, React Native, Flutter or a webview wrapper: we test the result on the device
- A code review can be added on request
From quote to a report per platform
- 1
Quote
€2,150 per platform excl. 21% VAT. iOS and Android count separately, because they are written in different languages, VoiceOver and TalkBack behave differently, and even a hybrid app renders its own components on each platform. What passes on one can be a finding on the other.
- 2
Audit on real devices
Three to five weeks, planned around your release cycle. A senior auditor tests, a second auditor reviews, and every report is checked by three people before delivery.
- 3
Report and retest
A report per component with a user story per finding, the device and assistive technology used, a screenshot and a fix. Plus a CSV for your backlog. After your fixes we retest per finding.
Frequently asked questions
Are mobile apps covered by the European Accessibility Act?
Yes. The EAA has applied since 28 June 2025 and covers the apps of companies that offer covered services to consumers: banking, travel booking, ticketing, e-commerce and communication services. Which Dutch regulator supervises you depends on the service: the ACM for e-commerce and telecom, the AFM for financial services, the ILT for passenger transport.
Can you audit one platform only?
Yes. Many clients start with the platform most of their customers use and add the other later. Each platform gets its own report and its own sample of screens.
How is this different from a website audit?
We test on real devices with the native screen readers instead of in a browser. We test touch interaction, gestures, rotation and platform patterns that do not exist on the web, such as swipe navigation and system accessibility settings. If you also have a website, that is a separate audit with its own report.
Do we have to share the source code?
No. We use the app the way a user does, through TestFlight or the App Store on iOS and through an APK or the Play Store on Android. A code review can be added if you want it.
What does it cost?
€2,150 per platform, excl. 21% VAT. Two platforms is two audits and two reports. For the Rijksmuseum we audited two apps this way, each with its own report.
Get clarity on your digital accessibility — without stress
Schedule an introductory meeting. No commitments — just valuable insight into your risks and opportunities.
Schedule an introduction
