The European Accessibility Act (EAA) moved from paper to practice in June 2025, and through 2026 enforcement has been becoming real across member states. I've now done accessibility work for several clients whose apps serve European users, and the pattern is consistent: teams either ignored it entirely or panicked disproportionately. Both are wrong. Here's the calm version.
Who Actually Has to Comply
The EAA covers products and services sold to consumers in the EU — and for apps, the relevant categories include e-commerce, banking and financial services, e-books, transport booking, and electronic communications. If your app sells to EU consumers in those categories, the law applies regardless of where your company sits: an Indian company with EU customers is in scope. Microenterprises (fewer than ten employees and under €2 million turnover) are exempt from the service requirements — a genuine relief for small startups, but one you outgrow, so building accessibly from the start remains the smart play.
What the Law Actually Requires
The EAA doesn't prescribe pixel-level rules; it requires that services be perceivable, operable, understandable, and robust — the same four principles behind WCAG, and in practice conformance is assessed against the harmonised European standard EN 301 549, which for apps largely maps to WCAG 2.1 AA. Concretely for mobile: every interactive element reachable and labelled for screen readers (TalkBack and VoiceOver), sufficient colour contrast, touch targets large enough, text that scales without breaking layouts, no information conveyed by colour alone, and forms with proper labels and error messaging.
What Compliance Costs in Practice
For a well-built app, an accessibility retrofit is smaller than teams fear: audit plus remediation for a mid-size app typically runs ₹1.5–4 lakhs, most of it in labelling, contrast fixes, focus order, and dynamic-type layout repairs. For apps built with custom-drawn UI and no semantic structure, it can run several times that — the cost isn't accessibility, it's paying down the shortcut of ignoring platform conventions. Built in from day one, accessibility adds low single-digit percentages to a project. The expensive version is always the retrofit.
Flutter, Compose and SwiftUI Made This Easier
Good news: modern UI toolkits carry accessibility in their bones. Flutter's semantics tree, Compose's semantics modifiers, and SwiftUI's accessibility API all expose structured meaning to screen readers by default for standard components — most of the work is covering the custom widgets and verifying flows end-to-end with TalkBack and VoiceOver actually switched on. My rule for every project: the developer navigates the core user journey with the screen reader on before any release. Ten minutes of that finds what audits charge for.
Beyond Compliance: The Business Case
Around one in six people live with some form of disability, and situational impairment — bright sunlight, a broken arm, a noisy room — affects everyone. Accessible apps are simply better products: clearer hierarchy, larger targets, readable contrast, sensible focus order help every user. There's also an SEO-adjacent effect: the semantic clarity that helps screen readers also helps the AI systems that increasingly summarise and recommend apps. Compliance is the floor; the ceiling is an app more people can actually use.
A Pragmatic Compliance Path
First, establish scope: does your app fall into an EAA-covered category and do you serve EU consumers? Second, audit against WCAG 2.1 AA — automated tools catch perhaps a third of issues; manual screen-reader testing catches the rest. Third, remediate in priority order: blockers in core journeys first, cosmetic issues later. Fourth, publish an accessibility statement describing your conformance status — the EAA expects transparency, and an honest statement with a roadmap beats silence. Fifth, wire accessibility checks into your release process so you don't regress.
If Your App Serves EU Users
Don't wait for a complaint to force the issue — member-state authorities respond to user complaints, and remediation under deadline pressure is the most expensive kind. An audit is cheap relative to the exposure, and most findings are fixable in a normal release cycle. I offer accessibility audits for Android, iOS, and Flutter apps, with a prioritised remediation plan and realistic costs — reach out through the contact form if your app is in scope and you'd like clarity on where you stand.