For most product organisations, accessibility has lived on the roadmap as a quality aspiration. In the European Union it became a condition of market access on 28 June 2025.
Who Is Covered
Directive (EU) 2019/882, the European Accessibility Act, "applies to the following services provided to consumers after 28 June 2025," including electronic communications, passenger transport (explicitly "mobile device-based services including mobile applications"), consumer banking, e-books and e-commerce. The exemption is narrow: microenterprises, meaning fewer than 10 persons and turnover or balance sheet of no more than EUR 2 million, providing services. Contracts signed before the date may run "no longer than five years," and legacy products have a transitional period "ending on 28 June 2030."
The audience is not a niche. The WHO estimates that "1.3 billion people experience significant disability," one in six people worldwide, and the European Commission counts "around 87 million" in the EU.
The Cost of Getting It Wrong Is Set Nationally
The directive requires penalties that are "effective, proportionate and dissuasive" and scaled to "the number of persons affected." Transpositions vary widely. Germany's BFSG allows fines up to EUR 100,000 for offering a non-compliant service. Ireland's S.I. No. 636/2023 makes it a criminal offence, with fines up to EUR 60,000, imprisonment up to 18 months, or both on indictment. The larger cost is commercial: a release that cannot ship into a market until it is fixed.
The Standard Just Moved
On 7 September 2026 the Commission's AccessibleEU centre announced EN 301 549 v4.1.1, which "adopts WCAG 2.2 as the accessibility benchmark." Until the Commission cites it in the Official Journal, v3.2.1 (WCAG 2.1 AA) "remains" the reference. Organisations building to 2.1 today are building to a standard that is already being replaced. One clarification matters for hybrid apps: web views embedded in a mobile app are assessed as software, not as web pages (ETSI).
What Leadership Should Ask For
- A scoping decision per product and market, made with counsel, not assumed.
- Automated accessibility checks in the build, so regressions fail before release. Android's UI testing tools support this from Compose 1.8.0 (Google).
- Evidence on file. Article 13 requires providers to "explain how the services meet the applicable accessibility requirements." That is a document someone has to be able to write.
This is an engineering and operations view, not legal advice.
-Rocky
#Accessibility #EAA #Compliance #EngineeringDreams #StrategiaX
Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X.
