Executive summary for leadership
One page shows how much of WCAG your app meets and how many critical issues it has. Decision-makers see the state of accessibility without reading the full report.
MOBILE ACCESSIBILITY AUDIT FOR IOS & ANDROID
Can everyone use your app?
The European Accessibility Act sets accessibility requirements for services such as e-commerce and banking. We audit your iOS and Android app against WCAG 2.1 AA and give you a clear plan to remove the barriers.
Book a 30-minute discovery call
When to run a mobile/web UX audit
The audit fits teams that run a mobile app and need a clear answer on accessibility. It works best in one of these situations:
01
You want an app everyone can use
About 1.3 billion people, or 1 in 6 worldwide, live with a significant disability, according to WHO. The audit shows where your app shuts them out and how to fix that.
02
Your app must comply with the European Accessibility Act
Since 28 June 2025, the EAA has covered e-commerce, consumer banking, telecoms, passenger transport, e-books, and video streaming, including their mobile apps. Microenterprises are exempt.
03
You plan a release or redesign
Fixing barriers before development costs less than reworking finished screens. The audit shows what to change before your team builds it.
04
Users have reported accessibility problems
Complaints about screen readers, contrast, or text size usually point to wider issues. We find the cause and every screen it affects.
05
You rely on automated scanners
Scanners find missing labels and low contrast, but they can’t show how VoiceOver or TalkBack read your screens. Focus order and reading logic need a person testing on a real device.
06
You need data for your accessibility statement
The statement should list which parts of your app aren’t accessible yet. The audit gives you that list, criterion by criterion.
1 of 6
Benefits of an accessibility audit
01
A clear WCAG 2.1 AA status
You get an assessment of how far your app meets WCAG 2.1 AA, the international accessibility standard.
02
A better experience for every user
People with disabilities get a better experience in your app. We identify the barriers that make it hard to use, so your team can easily remove them.
03
Clear priorities and ready fixes
The audit points to the areas that need improvement first, so your team knows where to start.
04
Lower legal risk
The audit helps you work towards requirements such as EN 301 549 and the European Accessibility Act, and reduce legal risk.
1 of 4
What you get
Every issue comes with the WCAG criterion it breaks, the screen where we found it and a recommended fix. Your product, design, and development teams can plan the work straight away.
Findings ranked by severity
Each issue is marked as critical or significant. A critical issue prevents a user from completing an action. A significant issue makes it much harder.
Evidence and a recommended fix
Every finding includes screenshots or screen recordings, a description, and a concrete recommendation. We also note whether the fix belongs to design, content or development.
Full WCAG 2.1 AA checklist
You get every success criterion marked as met, not met, or not applicable. The checklist gives your team the full picture beyond the issues shown in the report.
Prioritised action plan
We split the work into quick fixes and long-term improvements. Your team knows what to tackle first and can estimate it on the roadmap.
Input for your accessibility statement
The results show which parts of your app you should declare as not yet accessible. You can publish an honest statement and update it as fixes go live.
What we check in your app
We follow the four WCAG principles, known as POUR. Every finding in your report is grouped under one of them.
01
Perceivable
Can every user perceive your content? We check text alternatives for images and icons, reading order, colour contrast, text resizing, and captions for media.
02
Operable
Can every user navigate and take action? We check screen reader navigation, focus order, touch target sizes, and alternatives to complex gestures.
03
Understandable
Is the app clear and predictable? We check form labels, instructions, error messages, and consistent navigation.
04
Robust
Do assistive technologies interpret your app correctly? We check whether buttons, states, and roles are exposed properly to VoiceOver and TalkBack.
1 of 4
Our mobile accessibility audit framework
Every audit follows the same process, so results stay comparable between releases. How deep it goes depends on the access you can give us.
1. Scope and key user flows
We talk about your users, key flows such as login, payment, or search, and your tech stack. Together we choose the screens, the test devices, and the depth of the audit.
2. WCAG 2.1 AA review
Auditors check every screen in scope against WCAG 2.1 AA, as your users see and hear it. Automated scans catch repeating issues, and we verify every result manually.
3. Assistive technology testing
We complete app accessibility testing with VoiceOver on iOS and TalkBack on Android, on physical devices. We also check how the app responds to system text size. Beyond WCAG, we look at dark mode and high-contrast settings.
4. Report and action plan
Each issue gets evidence, a priority, a recommended fix, and the role responsible for it. We walk your team through the results and agree what to fix first.
Optional: code review
Some WCAG criteria can only be verified in the code. A Miquido developer reviews accessibility labels, roles and states in your native, Flutter, or React Native code, so every applicable criterion is covered.
Optional: UX expert review
Some barriers, such as inconsistent navigation, sit outside WCAG and still hurt usability. We add a heuristic review and log these issues separately.
1. Scope and key user flows
We talk about your users, key flows such as login, payment, or search, and your tech stack. Together we choose the screens, the test devices, and the depth of the audit.
2. WCAG 2.1 AA review
Auditors check every screen in scope against WCAG 2.1 AA, as your users see and hear it. Automated scans catch repeating issues, and we verify every result manually.
3. Assistive technology testing
We complete app accessibility testing with VoiceOver on iOS and TalkBack on Android, on physical devices. We also check how the app responds to system text size. Beyond WCAG, we look at dark mode and high-contrast settings.
4. Report and action plan
Each issue gets evidence, a priority, a recommended fix, and the role responsible for it. We walk your team through the results and agree what to fix first.
Optional: code review
Some WCAG criteria can only be verified in the code. A Miquido developer reviews accessibility labels, roles and states in your native, Flutter, or React Native code, so every applicable criterion is covered.
Optional: UX expert review
Some barriers, such as inconsistent navigation, sit outside WCAG and still hurt usability. We add a heuristic review and log these issues separately.
Choose your audit
The right audit depends on the question you want answered. Both can also run together.
01
Mobile accessibility audit (WCAG)
Best when you need to know how your app performs against WCAG 2.1 AA and what to fix first. We test it with VoiceOver and TalkBack on real devices.
02
UX/UI audit
Best when users drop off, get stuck, or leave negative reviews and you want to know what to fix first.
1 of 2
See how our mobile apps deliver real business impact
"They really dug deep to understand our industry and customer needs. They are truly engaged and always up for the next challenge."See our portfolio
Available for projects
Make your app usable for everyone
Tell us about your app and its key user flows. We’ll recommend the right audit scope and send you a quote.
Does the European Accessibility Act apply to my app?
Since 28 June 2025, the EAA has covered e-commerce, consumer banking, telecoms, passenger transport, e-books, and video streaming services, including their mobile apps. Microenterprises, with fewer than 10 employees and annual turnover of up to €2 million, are exempt from the rules for services. Each EU country enforces the act through its own national law, so penalties and procedures differ. Your legal team should confirm how the law applies to your product.
Will the audit make my app fully compliant?
No audit can guarantee compliance or protect you from penalties on its own. We review the app version you share with us against WCAG 2.1 AA, as thoroughly as the scope allows. When an issue repeats across many screens, we document representative examples and show where else to look. After the fixes, we recommend an independent re-check, just as you would run a separate security test before release.
Does the EAA apply if our company is outside the EU?
It can. The act covers services offered to consumers in the EU, wherever the provider is based. If your app serves EU users in one of the covered sectors, ask your legal team to check your obligations.
Which WCAG version and level do you test against?
We test against WCAG 2.1 at level AA. Level A covers the absolute minimum, while AA is the level referenced by the European standard EN 301 549. Most organisations that ask for “a WCAG audit” need exactly this level.
Do you need access to our source code?
Not for the design and content audit, which covers most criteria. Some criteria, such as accessibility labels and roles, can only be verified in the code. If you want a full audit, a Miquido developer reviews the code together with the design team.
Do you audit Flutter and React Native apps?
Yes. VoiceOver and TalkBack read the app your users install, so we test cross-platform apps the same way as native ones. During the code review, our developers check the framework’s own accessibility layer. In Flutter, we look at Semantics widgets and the labels, roles and states they expose. In React Native, we check props such as accessibilityLabel, accessibilityRole and accessibilityState. One codebase serves both platforms, so a single fix often removes an issue on iOS and Android at once. We still test on both systems, because the same code can behave differently in VoiceOver and TalkBack.
What do you need from us to start?
We need access to the app on iOS and Android, test accounts, and a list of your key user flows. A short interview helps us understand your users and your plans.
How do we keep the app accessible after the audit?
Every release can bring new barriers. Add accessibility checks to design reviews and QA, and test new features with VoiceOver and TalkBack before they go live. Update your accessibility statement as fixes are released.
Haven't you found the answers?
Talk to us