OOmnistu

Blog / Security

Security

European Accessibility Act: what it means for your website or app

Directive (EU) 2019/882 has applied since 28 June 2025 and names e-commerce as a covered service. How to check whether it applies to you, the microenterprise services exemption, the narrow transitional measures to 2030, and where WCAG/EN 301 549 fit.

OOmnistu
Reviewed 2026-11-20 · 5 min read

The European Accessibility Act (EAA), Directive (EU) 2019/882, has applied across the EU since 28 June 2025. If your business sells to consumers in the EU through a website or app, it is worth knowing what the Act covers, because e-commerce is one of its named service categories - and whether it applies to you is a set of concrete scope checks, not a default assumption.

This article is a plain-language orientation from primary EU sources (EUR-Lex and the European Commission), checked on 20 November 2026. It is not legal advice; the binding obligations are in each member state's national law transposing the directive.

What the Act covers

Per the Commission's overview, the EAA sets common accessibility requirements for products and services considered most important for persons with disabilities, including computers and operating systems, ATMs and ticketing machines, smartphones, telephony services, access to audiovisual media services, passenger transport services, banking services, e-books and e-commerce. The Commission's 27 June 2025 statement confirms the Act entered into application on 28 June 2025. For an app or web business, the most relevant categories are e-commerce (online selling to consumers), e-books, banking and telephony-related services; the detailed requirements for each are in the directive's Annex I and the national laws that implement it.

Checking whether you are in scope

Article 2 of the directive applies it to named services provided to consumers after 28 June 2025. For a web or app business, three checks decide most cases:

If a listed consumer service, no exemption and no transitional measure all point the same way, the service accessibility requirements apply as transposed nationally. If a check fails, the directive may not apply to you at all - which is why the checks, not an assumption of liability, are the right starting point.

The microenterprise exemption, exactly

Article 4(5) exempts microenterprises providing services from the service accessibility requirements and the obligations tied to them. Article 3(23) defines a microenterprise as an enterprise that employs fewer than 10 people and has either an annual turnover or an annual balance sheet total not exceeding €2 million - the headcount test plus one of the two financial tests. Two limits matter: the exemption covers services only (microenterprises dealing with products get lighter documentation duties, not an exemption), and for everyone else a documented disproportionate-burden or fundamental-alteration assessment (Article 14) can limit specific obligations case by case - it is not a blanket opt-out.

Transitional measures: narrow, not a grace period

The directive's dated transitions are specific carve-outs, not a general delay of the June 2025 start for websites and apps:

What "accessible" points to in practice

The directive sets functional requirements rather than mandating one technical checklist. For websites and apps, the widely used technical yardstick is the harmonised standard EN 301 549, which incorporates WCAG criteria; national laws reference it for presumption of conformity. Our existing guides on website accessibility basics, mobile app accessibility checks and fixing LCP/CLS cover the practical side once you know you are in scope.

What this means for a small app or web business

Sources

Drafted with AI assistance from these sources. This is orientation, not legal advice: applicability and penalties depend on national transposition, so confirm your obligations with the text of your member state's law or a qualified adviser.