Which regulations require a mobile app to be accessible, which WCAG and EN 301 549 criteria are checked and how to audit it step by step on Android and iOS.
Why a mobile app needs its own accessibility review
Many organisations review the accessibility of their website and assume the app ‘inherits’ the result. It does not. A native app is built with different components, is operated with touch gestures, changes orientation, depends on system settings (text size, contrast, screen reader) and is published in app stores with its own release cycle.
That is why the regulations treat applications for mobile devices as a separate channel, and why reviewing them requires different techniques and tools. In this guide you will see which regulations apply to you, which technical standard is used to measure compliance, which failures appear most often and how to organise an audit of an app on Android and iOS.
This article is for information only and does not replace legal advice on your specific case.
Which regulations require an app to be accessible
In Spain two frameworks coexist, depending on who is responsible for the app.
Public sector: Royal Decree 1112/2018
Royal Decree 1112/2018, which transposes Directive (EU) 2016/2102, applies to public administrations and the institutional public sector (Article 2). Its Article 4 defines applications for mobile devices as software applications designed and developed to be used by the general public, and excludes software that controls the devices themselves, such as operating systems. According to its fifth final provision, all provisions relating to mobile applications have applied since 23 June 2021.
As well as meeting the technical requirements, the body must publish an accessibility statement for the app (Article 15) and review it periodically (Article 17).
Private sector: Law 11/2023 and the European Accessibility Act
Law 11/2023 transposes Directive (EU) 2019/882 and applies to certain services provided to consumers from 28 June 2025: e-commerce, consumer banking services, electronic communications, services providing access to audiovisual media services, e-books and passenger transport, among others, with some transitional periods running until 28 June 2030. In the case of transport, the law itself expressly mentions ‘mobile device-based services, including mobile applications’.
Annex I of Directive (EU) 2019/882 requires websites and mobile device-based services, including apps, to be accessible in a consistent and adequate way, that is, perceivable, operable, understandable and robust. Microenterprises providing services are exempt (Article 3.3 of the law) and there is an exception for disproportionate burden, which must be justified and documented (Article 16).
| Aspect | Public sector (RD 1112/2018) | Private sector (Law 11/2023) |
|---|---|---|
| Who is obliged | Administrations, the institutional public sector and the Administration of Justice, among others | Companies providing the services covered by the law, except microenterprises |
| Since when (apps) | 23 June 2021 | 28 June 2025 |
| Technical reference | EN 301 549 (UNE-EN 301549 in the Observatorio methodology) | Harmonised standards once published in the Official Journal of the EU or, failing that, technical specifications (Article 17) |
| Main exceptions | Third-party content neither funded, developed nor controlled by the body (Article 3.4) | Microenterprises providing services (Article 3.3) and justified disproportionate burden (Article 16) |
| Accessibility statement | Mandatory, updated at least once a year (Article 15) | Not governed by the Royal Decree 1112/2018 model |
Which technical standard is used to measure compliance
Neither regulation lists, button by button, what an app must do. They refer to technical standards, and the reference in Europe is EN 301 549, which sets out the accessibility requirements for ICT products and services. Its clause 11 is devoted to software, which is where native apps fit, and its annex mapping it to Directive (EU) 2016/2102 includes a specific table for mobile applications.
Which version applies
• EN 301 549 V3.2.1 (2021-03): this is the harmonised standard cited in the Official Journal of the EU for Directive (EU) 2016/2102. Its Spanish version, UNE-EN 301549:2022, is the basis of the Observatorio de Accesibilidad Web (Web Accessibility Observatory) methodology for reviewing apps.
• EN 301 549 V4.1.1 (2026-09): published by ETSI in September 2026, it is aligned with WCAG 2.2. According to Ireland’s National Disability Authority, its reference in the Official Journal of the EU is expected on 16 December 2026 and, until then, V3.2.1 remains in force as the reference.
The role of WCAG
The software requirements of EN 301 549 adapt the WCAG criteria to non-web contexts. The W3C makes this clear: it has no separate guidelines for mobile; WCAG also applies to content used on mobile devices. To translate them to apps there are two informative W3C documents:
• WCAG2ICT, a group note published on 8 October 2024, which explains how to apply the WCAG 2.0, 2.1 and 2.2 success criteria to non-web technologies, including apps.
• WCAG2Mobile, a draft note dated 6 May 2025, which proposes taking each screen of the application, rather than each web page, as the unit of evaluation.
The WCAG criteria that matter most in an app
All level A and AA criteria count, but some have a particular impact on small touch screens. This table summarises the ones worth examining closely, with their number and level in WCAG 2.2 (using the official W3C names).
| WCAG 2.2 criterion | Level | What to check in the app |
|---|---|---|
| 1.1.1 Non-text Content | A | Icons, images and graphical buttons have an accessible label that the screen reader announces |
| 1.3.4 Orientation | AA | The app works in portrait and landscape, unless one orientation is essential |
| 1.4.3 Contrast (Minimum) | AA | A ratio of at least 4.5:1 for normal text and 3:1 for large text |
| 1.4.4 Resize Text | AA | With the system text size increased, text grows without being cut off or losing functionality |
| 2.5.1 Pointer Gestures | A | Anything done with multi-finger or path-based gestures has a single-tap alternative |
| 2.5.4 Motion Actuation | A | Functions triggered by shaking or tilting the phone have an alternative and can be disabled |
| 2.5.7 Dragging Movements | AA | Anything that requires dragging can also be done with simple taps |
| 2.5.8 Target Size (Minimum) | AA | Touch targets of at least 24 by 24 CSS pixels or with sufficient spacing, subject to the criterion’s exceptions |
| 3.3.8 Accessible Authentication (Minimum) | AA | Signing in does not require remembering or transcribing information without an alternative |
| 4.1.2 Name, Role, Value | A | Each control exposes its name, role and state to assistive technologies |
Watch out for the CSS pixel: it does not exist as such in a native app. This is where documents such as WCAG2ICT and WCAG2Mobile help to interpret the criteria in each platform’s own units.
Which failures are most common in public sector apps
The Observatorio de Accesibilidad Web publishes aggregated reports on the in-depth monitoring of public sector apps. The 2023 report analysed 55 applications using the methodology based on UNE-EN 301549:2022: 4 were fully compliant (7.27 %), 49 partially compliant (89.09 %) and 2 non-compliant (3.64 %), with an average score of 7.89 out of 10.
The requirements that most apps failed were these:
| UNE-EN 301549 requirement | Apps non-compliant with the requirement |
|---|---|
| 11.1.4.3 Contrast (minimum) | 52.73 % |
| 11.1.1.1.1 Non-text content | 47.27 % |
| 11.1.3.1.1 Info and relationships | 47.27 % |
| 11.1.3.4 Orientation | 41.82 % |
| 11.1.4.4.1 Resize text | 36.36 % |
| 11.4.1.2.1 Name, role, value | 32.73 % |
The practical takeaway is clear: almost all the apps reviewed did part of the job well, but very few achieved full compliance. And the most frequent failures are not exotic: colours, labels, structure, orientation and text size.
How to audit an app step by step
The Observatorio methodology gives a good hint on how to organise the work: it evaluates requirement by requirement, takes the app’s screens as the unit of analysis and reviews each operating system separately. A requirement is considered compliant if at least 90 % of the screens to which it applies pass it. From there, a practical audit can follow these steps:
1. Define the scope. Which app, which version, on which platforms (Android, iOS or both) and against which reference: EN 301 549 and WCAG 2.2 level AA is the norm.
2. Choose the screens and flows. Include the key tasks end to end: sign-up or sign-in, search, main form, payment or procedure, settings and help. A failure in a single step can block the whole journey.
3. Run the automated tools. Run Accessibility Inspector on iOS and Accessibility Scanner on Android on each selected screen and save the results.
4. Test with the screen reader. Go through the flows with VoiceOver and TalkBack: check that everything is announced with an understandable name, that the order makes sense and that state changes are communicated.
5. Test other ways of using the app. Increase the system text size, rotate the device, use an external keyboard or Switch Access and check that no functions depend solely on complex gestures or phone movements.
6. Review the documents and content the app opens. PDFs, videos or embedded web pages also count, with their own requirements.
7. Document each finding. Screen, requirement affected, impact, priority and proposed fix, so that the development team can act.
8. Verify the fixes. Repeat the tests on the new version before publishing it in the stores.
If possible, complement the technical review with testing by users with disabilities: Android’s own testing guide recommends it as a source of information that the other techniques do not provide.
Automated tools: what they detect and what they miss
The platforms’ own tools are the best starting point because they are free and fit into the development team’s day-to-day work.
On iOS
Accessibility Inspector, included in Xcode, lets you audit a screen and detects, among other things, problems with element descriptions, hit area size, contrast, text clipped at large sizes and support for Dynamic Type. The same audits can be automated in UI tests with the performAccessibilityAudit function. Apple’s own documentation warns that clearing all warnings does not guarantee a fully accessible app and recommends always testing with assistive technologies such as VoiceOver.
On Android
Android’s testing guide recommends combining manual testing with TalkBack, Switch Access and Voice Access; analysis tools such as Accessibility Scanner or Compose UI checks; automated testing; and the Google Play pre-launch report, which checks touch target size, low contrast and content labelling, among other aspects.
• What they usually detect well: unlabelled controls, insufficient contrast, small touch targets and clipped text.
• What needs human review: whether a label is understandable, whether the reading order makes sense, whether a complete flow can be finished with the screen reader and whether error messages are clear.
The same applies to accessibility widgets or overlays that promise to fix everything: they do not replace fixing the code, nor do they guarantee compliance.
After the audit: fix, declare and maintain
An audit is only useful if it turns into a work plan. These are the tasks that usually follow:
• Prioritise and fix. First whatever blocks key tasks; then whatever makes use difficult.
• Publish or update the accessibility statement. In the public sector, Article 15 of Royal Decree 1112/2018 states that it must be on the website of the body that developed the app, next to the download link, or provided with the information available when downloading it from distribution platforms, and updated at least once a year.
• Review with every release. Article 17 of the same royal decree provides for periodic reviews and mentions technological updates to apps. Building automated audits into UI tests helps avoid regressions.
• Train the team. Design, development and content staff need to know the criteria so they do not reintroduce the same errors.
If you need a full diagnosis of your app on Android and iOS against EN 301 549 and WCAG 2.2, Tu Web Accesible’s digital accessibility audit service combines automated tools with expert manual review, and the accessibility remediation team can then support you with the fixes.
Sources
• Royal Decree 1112/2018 on the accessibility of public sector websites and mobile applications (BOE) (https://www.boe.es/buscar/act.php?id=BOE-A-2018-12699)
• Law 11/2023 of 8 May (BOE) (https://www.boe.es/buscar/act.php?id=BOE-A-2023-11022)
• Directive (EU) 2019/882 on the accessibility requirements for products and services (EUR-Lex) (https://eur-lex.europa.eu/legal-content/ES/TXT/HTML/?uri=CELEX:32019L0882)
• EN 301 549 V3.2.1 (ETSI) (https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf)
• EN 301 549 V4.1.1 (ETSI) (https://www.etsi.org/deliver/etsi_en/301500_301599/301549/04.01.01_60/en_301549v040101p.pdf)
• Publication of EN 301 549 V4.1.1 (National Disability Authority, Ireland) (https://nda.ie/news/en301549-published)
• WCAG 2.2 (W3C) (https://www.w3.org/TR/WCAG22/)
• Mobile accessibility at W3C (WAI) (https://www.w3.org/WAI/standards-guidelines/mobile/)
• Publication of WCAG2ICT (W3C WAI) (https://www.w3.org/WAI/news/2024-10-08/wcag2ict/)
• WCAG2Mobile, draft note (W3C) (https://www.w3.org/TR/wcag2mobile-22/)
• Web Accessibility Observatory methodology for mobile applications (PAe) (https://administracionelectronica.gob.es/pae_Home/va/dam/jcr:b08fc29b-4a60-4e24-879e-548bcac21b1d/2022_Metodologia-OAW_Aplicaciones-moviles.pdf)
• 2023 aggregated report on in-depth monitoring of apps (PAe) (https://administracionelectronica.gob.es/pae_Home/dam/jcr:6820a779-354d-403d-b902-b33e3a0d8058/2023_Informe_agregado_seguimiento_profundidad_APPS.pdf)
• Performing accessibility audits with Accessibility Inspector (Apple) (https://developer.apple.com/documentation/accessibility/performing-accessibility-audits-for-your-app)
• Test your app’s accessibility (Android Developers) (https://developer.android.com/guide/topics/ui/accessibility/testing)