European Accessibility Act (Directive (EU) 2019/882)

Record: software-cert-032 — EU European Accessibility Act
Issuing body / enforcer: EU legislature; transposed into national law by each Member State; enforcement by national market-surveillance/designated authorities under national penalty regimes
Jurisdiction: EU/EEA — applies to products placed on and services provided in the EU market, including by non-EU companies serving EU consumers
Record type / importance: regulation / license
Last verified: 2026-09-30

What it is

The EU's harmonized accessibility law for the private sector: mandatory accessibility requirements for a defined list of everyday products and services. It is a directive, so the obligations land through national transpositions (e.g., Ireland's 2023 Regulations), with penalties and procedures varying by Member State — but the technical core is harmonized around EN 301 549 (anchored to WCAG 2.1). For software teams building consumer-facing digital products, the EAA has been binding since mid-2025.

Scope: who/what it applies to, triggers, thresholds

Products: consumer computer hardware and operating systems, payment terminals, self-service terminals (ATMs, ticketing, check-in machines), consumer terminal equipment for telecom and audiovisual services, e-book readers.
Services: electronic communications, access to audiovisual media, passenger transport (air/bus/rail/water) service elements, consumer banking, e-books, and e-commerce — the last being the broad catch-all for B2C digital storefronts.
Exemptions: microenterprises (<10 employees AND ≤€2M turnover) providing services are exempt; no microenterprise exemption for products. Disproportionate-burden and fundamental-alteration defenses exist but must be documented and reassessed.
Threshold: applies to products placed on the market and services provided from June 28, 2025. Transitional provisions (Art. 32) let some pre-existing products/services and existing self-service terminals run out their lifecycle under conditions — national implementations differ, so check per-market.

Key requirements and compliance obligations

Functional accessibility requirements (Annex I): products and services must be perceivable, operable, understandable, and robust for persons with disabilities — in practice delivered via EN 301 549 v3.2.1 (the harmonized standard; incorporates WCAG 2.1 AA for web/software) giving presumption of conformity.
Information and documentation: providers must prepare and keep available information explaining how the service meets the requirements; maintain technical documentation for products; CE marking applies to products in scope.
Ongoing duty: conformity is not frozen at audit — releases, third-party components, content, and design-system changes can reintroduce barriers; market-surveillance authorities follow up complaints and can verify remediation.
Service-provider obligations: design and provide services per the requirements, publish accessibility information, handle complaints, and cooperate with authorities.

Penalties and consequences

Set nationally — fines, product withdrawal, service-remediation orders, and publication of non-compliance. As of mid-2026, no confirmed EAA fine had been publicly verified — authorities have signaled they will use withdrawal orders, mandated audits, and naming before fines. The exposure is real but the fining track record is still forming; procurement exclusion and B2B contract flow-down (in-scope customers pushing obligations onto vendors) are the nearer-term commercial risks.

Version/edition status and LIVE changes (verified 2026-09-30)

Applying since June 28, 2025 — now in its second year of application; teams are past the "prepare" phase into maintenance and market-surveillance exposure.
Technical anchor EN 301 549 v3.2.1 (2021) remains current; it references WCAG 2.1 (not 2.2) — a common source of confusion.
Live 2026 theme: authorities moving from guidance to complaint-driven enforcement; B2B SaaS vendors are discovering EAA scope indirectly through enterprise customers' accessibility questionnaires even when the vendor's own product is B2B-only.

No catalogue software certification tests EAA/EN 301 549 content specifically. CISSP (software-cert-010) does not cover accessibility. This is a gap: accessibility competence in software is carried by specialist credentials (e.g., IAAP CPACC/WAS), which were not in the catalogue's flagship tier.

Honest flags

The "no confirmed EAA fine as of mid-2026" status comes from a practitioner standards repository, not an official EU source — treat as best-available, not authoritative. National penalty maxima were not verified per Member State and are deliberately not quoted here.

Original ETS reference writing, verified against public sources on 2026-09-30. Thin sourcing is flagged inline. Not legal advice — confirm current editions with the issuing body.

European Accessibility Act (Directive (EU) 2019/882)