European Accessibility Act: 2025 Deadline Guide

What Is the European Accessibility Act?

The European Accessibility Act (EAA) — formally Directive (EU) 2019/882 — is an EU-wide law that sets binding accessibility requirements for products and services sold or provided within the European Union. It was adopted by the European Parliament and the Council on April 17, 2019.

The directive required all 27 EU member states to transpose the EAA into their national legislation by June 28, 2022. Businesses then had a three-year transition period to bring their products and services into compliance. That transition period ended on June 28, 2025 — enforcement is now active.

Unlike earlier EU accessibility directives — such as Directive (EU) 2016/2102, which applied only to public sector websites and mobile apps — the EAA extends to private sector businesses. Any company that offers covered products or services to consumers within the EU market must comply, regardless of where the company is headquartered.

The EAA's stated objective, per Article 1, is to "contribute to the proper functioning of the internal market by approximating laws, regulations and administrative provisions of the Member States as regards accessibility requirements for certain products and services." In practice, it eliminates the patchwork of differing national accessibility laws and creates a single standard across the EU.

Which Products and Services Does the EAA Cover?

The scope of the EAA is defined in Article 2 and Annex I. It covers both physical products with digital interfaces and purely digital services.

Products (Annex I, Section I)

Computer hardware and operating systems — desktops, laptops, tablets, smartphones, and their embedded operating systems
Self-service terminals — ATMs, ticketing machines, check-in kiosks, and interactive information terminals
Consumer terminal equipment for electronic communications — phones, routers, and modems with interactive user interfaces
Consumer terminal equipment for audio-visual media services — smart TVs, set-top boxes, and streaming devices
E-readers — dedicated hardware for reading digital publications

Services (Annex I, Section III–V)

E-commerce — any website or mobile app that sells products or services to consumers, including marketplaces, checkout flows, and account management
Banking and financial services — online banking portals, mobile banking apps, payment terminals, and investment platforms
Electronic communications services — consumer-facing telephony, messaging, and internet access services
Audio-visual media services — streaming platforms, on-demand video services, and electronic program guides
Transport services — websites, mobile apps, electronic tickets, real-time travel information, and self-service ticketing machines for air, bus, rail, and waterborne passenger transport
E-books and dedicated reading software — the digital publications themselves and the applications used to read them

A critical point: the EAA applies based on where the consumer is located, not where the business is incorporated. A US-based SaaS company selling subscriptions to EU customers through a website is subject to the EAA for that service.

Who Is Exempt? The Micro-Enterprise Exemption

Article 4(5) of the EAA provides a limited exemption for micro-enterprises, but only for service obligations — not product obligations.

Qualification Thresholds

A business qualifies as a micro-enterprise if it meets both conditions:

Fewer than 10 employees (full-time equivalent)
Annual turnover or annual balance sheet total does not exceed €2 million

These thresholds follow the definition in Commission Recommendation 2003/361/EC.

What the Exemption Covers (and Doesn't)

Micro-enterprises are exempt from the service accessibility requirements in Section III–V of Annex I. They are not exempt from the product requirements in Section I. A small company that manufactures self-service kiosks, for example, must still meet the product accessibility requirements regardless of its size.

The exemption is also narrow in practice. If a micro-enterprise grows beyond either threshold, it must comply within one year of exceeding the limit. Companies near the boundary should plan for compliance proactively rather than relying on the exemption as a long-term strategy.

The Disproportionate Burden Defense

Separately from the micro-enterprise exemption, Article 14 provides a "disproportionate burden" defense. Any business — regardless of size — may argue that a specific accessibility requirement would impose a disproportionate burden if:

The cost of compliance is disproportionate to the overall revenue of the product or service
The requirement would necessitate a fundamental alteration of the product or service

This defense requires documented justification, must be reassessed at least every five years, and must be reported to the relevant market surveillance authority upon request. It is not a blanket exemption — it applies requirement by requirement.

What Does the EAA Actually Require?

The EAA's technical requirements are defined in Annex I and structured around four functional accessibility principles that align with the WCAG framework.

Functional Performance Requirements

All covered products and services must, per Annex I, Section I and III:

Support usage without vision — content and controls must work with screen readers and other assistive technologies
Support usage with limited vision — sufficient contrast, resizable text, and no reliance on color alone
Support usage without perception of color — information must not be conveyed by color alone
Support usage without hearing — captions, transcripts, and visual alternatives for audio content
Support usage with limited hearing — volume controls, high-quality audio, and noise reduction
Support usage without vocal capability — text-based alternatives to voice-based interfaces
Support usage with limited manipulation and strength — large touch targets, keyboard alternatives, and no timed interactions requiring physical dexterity
Support usage with limited reach — physical products must position interactive elements within accessible reach ranges
Minimize photosensitive seizure triggers — no content that flashes more than three times per second
Support usage with limited cognition — clear language, predictable navigation, error prevention, and consistent layouts

For Digital Services Specifically

Digital services (e-commerce, banking, transport, media, e-books) must additionally provide:

Accessibility statements — a publicly available document describing the service's conformance status, known limitations, and contact information for accessibility issues
Feedback mechanisms — a way for users to report accessibility barriers and request content in accessible formats
Compatible with assistive technologies — services must work with screen readers, magnifiers, speech recognition, and switch devices in current common use
Accessible documentation — if user documentation is provided, it must itself be accessible

How Does the EAA Relate to EN 301 549?

The EAA itself does not specify line-by-line technical criteria. Instead, Article 15 establishes that products and services conforming to harmonised European standards are presumed to comply with the directive's requirements.

The primary harmonised standard the EAA references is EN 301 549 — "Accessibility requirements for ICT products and services," published by ETSI (European Telecommunications Standards Institute). The current version is EN 301 549 V3.2.1 (2021-03).

What EN 301 549 Contains

EN 301 549 is a comprehensive technical standard covering:

Chapters 5–13: Detailed testable requirements for ICT products and services, including closed functionality systems, web content (incorporating WCAG 2.1 by reference), non-web documents, and software
Chapter 9 (Web): Directly maps to WCAG 2.1 Level AA — if your web content meets WCAG 2.1 AA, it satisfies Chapter 9 of EN 301 549
Chapter 10 (Non-web documents): Applies WCAG 2.1 principles to PDFs, Word documents, and other non-web content
Chapter 11 (Software): Applies WCAG 2.1 principles to native software, including mobile apps
Chapter 12 (Documentation and support): Requires accessible product documentation and technical support services
Chapter 13 (ICT providing relay or emergency service access): Requirements for real-time text and relay services

Presumption of Conformity

If a product or service meets EN 301 549, it is presumed to conform with the EAA. This is not an absolute guarantee — a market surveillance authority can still challenge conformity in specific cases — but in practice, EN 301 549 compliance is the clearest path to demonstrating EAA compliance.

For web-based products and services, the chain is: EAA → EN 301 549 Chapter 9 → WCAG 2.1 Level AA. Meeting WCAG 2.1 AA satisfies the web accessibility component of the EAA.

What Are the Penalties for Non-Compliance?

The EAA delegates enforcement and penalty setting to individual member states under Article 30. Penalties must be "effective, proportionate, and dissuasive" — the same language used in the GDPR.

How Enforcement Works

Each member state designates market surveillance authorities (for products) and authorities responsible for checking the compliance of services (for services). These authorities can:

Require corrective actions within a specified timeline
Restrict or prohibit the sale of non-compliant products on the national market
Order the withdrawal or recall of products already on the market
Issue fines based on the severity, duration, and intentionality of the infringement

Penalties by Country

Because each member state sets its own penalties, the consequences vary:

Germany (Barrierefreiheitsstärkungsgesetz — BFSG): Fines up to €100,000 per infringement, with the Federal Network Agency (Bundesnetzagentur) as the enforcement body for digital services
France (transposed via modifications to the Consumer Code): Penalties aligned with consumer protection enforcement, with DGCCRF (Direction générale de la concurrence, de la consommation et de la répression des fraudes) as the responsible authority
Ireland (European Union (Accessibility Requirements for Products and Services) Regulations 2022): Market surveillance authority can issue compliance notices, prohibition notices, and seek High Court orders
Netherlands (transposed into existing accessibility legislation): The Dutch Authority for Digital Infrastructure (RDI) oversees compliance for digital services

Third-Party Complaints

Under Article 29, member states must ensure that consumer organizations and persons with disabilities can bring complaints against non-compliant businesses to the relevant national authority. Competitors can also initiate proceedings in some member states. This creates multiple enforcement vectors beyond government-initiated actions.

The deadline of June 28, 2025 has passed. Enforcement is now live in transposed member states.

How Does the EAA Differ from Section 508 and the ADA?

Organizations operating in both the US and EU markets face overlapping but distinct accessibility obligations.

EAA vs. ADA (Americans with Disabilities Act)

| Aspect | EAA | ADA | |--------|-----|-----| | Scope | Private sector products and services sold in the EU | Places of public accommodation (increasingly interpreted to include websites) | | Technical standard | EN 301 549 / WCAG 2.1 AA | No single mandated standard; courts and DOJ reference WCAG 2.1 AA | | Accessibility statement | Required — must be published and include contact information | Not explicitly required | | Feedback mechanism | Required — users must be able to report barriers | Not explicitly required | | Enforcement | Administrative (market surveillance authorities) | Litigation-driven (private lawsuits under Title III) | | Penalties | Fines set by member states | Court-ordered remedies; no statutory damages under Title III |

EAA vs. Section 508

Section 508 of the Rehabilitation Act applies only to US federal agencies and their contractors. It references the Revised Section 508 Standards, which incorporate WCAG 2.0 Level AA (not 2.1). The EAA applies to private sector businesses, references WCAG 2.1 AA via EN 301 549, and covers a broader range of products and services.

Practical Overlap

Since both the EAA and ADA effectively reference WCAG 2.1 AA as the technical benchmark, a single compliance effort addresses both frameworks for web content. The key additional steps for EAA compliance are publishing an accessibility statement with the required content and implementing a feedback mechanism — neither of which the ADA mandates.

What Should You Do Before the Deadline? A Compliance Checklist

The June 28, 2025 deadline has passed, but organizations that have not yet achieved compliance should treat this as an urgent priority. Enforcement is ramping up.

Immediate Actions

[ ] Determine if you're in scope — review Article 2 of the EAA and Annex I to confirm whether your products or services fall under the directive's requirements
[ ] Identify your EU market exposure — any service accessible to EU consumers is potentially in scope, regardless of your company's location
[ ] Check the micro-enterprise exemption — verify whether your business meets both the employee count (fewer than 10) and revenue (under €2M) thresholds

Audit and Documentation

[ ] Run a WCAG 2.1 AA accessibility audit — scan every web property and mobile app covered by the EAA. VPATify's scanner performs automated WCAG 2.1 and 2.2 checks and generates a detailed violation report organized by criterion
[ ] Map results to EN 301 549 — for full EAA presumption of conformity, your audit should cover EN 301 549 chapters 9–11, not just WCAG web criteria. VPATify maps scan results directly to EN 301 549 criteria
[ ] Generate an Accessibility Conformance Report — a VPAT (Voluntary Product Accessibility Template) in the EN 301 549 format documents your conformance status. VPATify auto-populates a VPAT from your scan results in the correct EN 301 549 template format

Publish and Communicate

[ ] Publish an accessibility statement — per the EAA, your statement must include:
- A description of which parts of the service are accessible
- Known limitations and a timeline for remediation
- Contact information for accessibility feedback
- A reference to the enforcement authority in the relevant member state
[ ] Implement a feedback mechanism — provide a visible, accessible way for users to report barriers (a form, email address, or both)
[ ] Document your internal process — maintain records showing how accessibility requirements are assessed, implemented, and monitored

Remediate and Verify

[ ] Prioritize violations by severity — address critical blockers first (keyboard traps, missing form labels, zero-contrast text). VPATify categorizes violations as Critical, Serious, Moderate, or Minor
[ ] Fix and rescan — after remediation, run follow-up scans to verify fixes and catch regressions
[ ] Test with real users — automated tools catch 30–40% of accessibility issues. Conduct manual testing with keyboard-only navigation, screen readers (NVDA, JAWS, VoiceOver), and ideally with participants who rely on assistive technologies daily

Ongoing Compliance

[ ] Schedule recurring audits — accessibility is not a one-time project. New content, features, and design changes can introduce regressions
[ ] Reassess disproportionate burden claims — if you have invoked Article 14, you must reassess at least every five years or when the product/service is significantly modified
[ ] Monitor national transposition updates — member states may update their national implementing legislation; track changes in the countries where you have significant EU customer bases

How VPATify Helps with EAA Compliance

VPATify is built to support the specific documentation requirements the EAA creates.

EN 301 549 Mapping

VPATify's scanner maps accessibility violations directly to EN 301 549 criteria — not just WCAG success criteria. This means your scan results align with the technical standard the EAA references for presumption of conformity.

VPAT Generation in EN 301 549 Format

The VPAT template comes in three editions: WCAG (US-focused), Section 508, and EN 301 549 (EU/international). VPATify generates the EN 301 549 edition, which is the correct format for documenting EAA compliance. Your conformance report is auto-populated from scan data, reducing the manual effort of filling out the template criterion by criterion.

Accessibility Statement Generator

VPATify generates an EAA-compliant accessibility statement directly from your VPAT data. The generated statement includes all elements required by the directive: conformance status, known limitations, contact information, and enforcement body references.

Continuous Monitoring

VPATify supports scheduled recurring scans so you can detect accessibility regressions as they are introduced — before an enforcement authority or a consumer complaint surfaces them.