The Executive Guide to EN 301 549
The "Hidden" Standard for Mobile Apps in Europe—and the Critical 2025 Deadline.
If you do business in Europe, WCAG is no longer enough. While the Web Content Accessibility Guidelines (WCAG) are the global benchmark, EN 301 549 is the legal standard. It is the rigorous technical specification that underpins the European Accessibility Act (EAA).
For organizations with Mobile Apps (iOS & Android), EN 301 549 contains critical requirements—specifically in Clause 11—that standard web audits completely miss.
What is EN 301 549?
EN 301 549 is the European Standard for accessibility requirements for ICT (Information and Communications Technology) products and services.
Unlike , which focuses primarily on web content, EN 301 549 covers the entire digital ecosystem:
Software
Including Native Mobile Apps (iOS & Android)
Hardware
Self-service kiosks, ATMs, ticket machines
Biometrics
Fingerprint & Face Scanners
Customer Support
Help desks, call centers
The Relationship with WCAG
Think of EN 301 549 as "WCAG Plus."
It incorporates as its foundation but adds specific clauses for hardware and software that does not run in a web browser.
The Trap
Many US companies believe "We are WCAG compliant, so we are safe in Europe." This is false. If your mobile app relies on FaceID without a fallback, or ignores the user's system font size, you are violating EN 301 549.
The Critical Deadline: June 28, 2025
The is a directive that forces private companies to ensure their digital products are accessible.
Who it affects:
Any business selling E-commerce services, Banking, Transport, or E-books to EU consumers.
The Penalty:
Fines vary by country (up to €100,000 in some regions) and regulators have the power to remove non-compliant products from the market.
The Standard:
To comply with the EAA, your product must conform to EN 301 549 V3.2.1 (or later).
The "Mobile Blindspot": Clause 11 & Biometrics
Most automated accessibility tools scan HTML code. They cannot "see" inside a compiled iOS or Android app. This leaves you exposed to unique EN 301 549 failures:
User Preferences
"Respect the User's Settings."
On a website, the browser handles text resizing. In a native app, you must handle it.
The Rule:
Your app must respect the user's platform settings for Font Size, Color, and Contrast.
The Failure:
If a user sets their iPhone to "Large Text" and your app's text doesn't grow, you fail Clause 11.7.
Biometrics
"Don't Lock Users Out with FaceID."
EN 301 549 explicitly addresses biometrics.
The Rule:
You cannot rely solely on a biological characteristic (fingerprint, face, iris) for identification.
The Failure:
An app that requires a fingerprint scan to login without offering a PIN or Password alternative is non-compliant. Users with physical disabilities (e.g., bandaged hands, tremors) may be unable to provide a fingerprint.
No Disruption of Accessibility Features
"Don't Break Platform Features."
Your app must work harmoniously with the operating system's accessibility tools.
The Rule:
Your app must not interfere with the platform's defined accessibility features.
The Failure:
An app that disables the "TalkBack" screen reader gestures to implement a custom "swipe" game mechanic.
EN 301 549 vs. WCAG: The Comparison
| Feature | (Web) | EN 301 549 (Europe) |
|---|---|---|
| Primary Scope | Web Content & Documents | ICT Products, Hardware, Software, & Apps |
| Biometrics | Not explicitly covered | Strictly Regulated (Must have alternatives) |
| Mobile Focus | Implicit (covered under general rules) | Explicit (Clause 11: "Software") |
| Legal Status | Guidelines (Voluntary until adopted by law) | The Law (Mandated by EAA & WAD) |
Primary Scope
Biometrics
Mobile Focus
Legal Status
The AUDITSU Approach: Commit, Audit, Rectify
The European Accessibility Act (EAA) deadline is rigid, but your path to compliance doesn't have to be. At AUDITSU, we advocate for a phased roadmap that establishes immediate legal defensibility while you work toward technical perfection.
Commit & Publish
"Acknowledge the journey." The EU specifically requires a detailed "Declaration of Conformity." You do not need to be 100% perfect today to protect your business, but you must be transparent about your status. The most critical first step is publishing a legally robust Accessibility Statement that cites the correct standard (EN 301 549).
The Action:
Use the AUDITSU Accessibility Statement Generator to create an EAA-compliant declaration for your apps and website. Our templates are designed to meet the specific reporting requirements of EU Directive 2016/2102.
The Benefit:
This acts as your "flag in the sand," signaling to EU regulators and consumers that you understand your legal obligations and are actively managing your compliance roadmap.
Audit & Validate
"Check the 'Clause 11' Blindspot." Once your commitment is public, you must validate your actual performance. Do not rely on standard web scanners—they often miss the strict mobile-specific requirements of EN 301 549 Clause 11 (such as Biometrics and Platform Adaptation).
The Action:
Conduct a "Human-First" audit (internally or with partners like our Audit Toolkit) specifically targeting mobile use cases. Ensure you test for critical EU failures like biometric lockouts (FaceID) and font scaling limits.
The Benefit:
You transform vague legal anxiety into a prioritized worklist, identifying the specific "blockers" that could risk your app being removed from the EU App Store.
Rectify & Win
"Secure Your Market Access." Accessibility in Europe is a condition of market entry. As you fix the mobile-specific issues identified in Phase 2, you update your Accessibility Statement to reflect your progress from "Partial Conformance" to full compliance.
The Action:
Systematically resolve your prioritized issues—starting with those that block basic access—and update your AUDITSU statement to show "Conformance" rather than just "Intent."
The Benefit:
You permanently secure your access to the European market while reducing the risk of fines or enforcement actions after the June 2025 deadline.
Is your mobile app ready for Europe?
The 2025 deadline is final. Take the first step toward a defensible legal position today.
Want to learn more first? or .