The European Accessibility Act has applied since June 28, 2025, and one of the most common questions from businesses is also one of the most misunderstood: who actually enforces it? There is no single EU regulator knocking on doors. Instead, enforcement runs through each member state, which makes the practical experience of an EAA action different from a US lawsuit in ways worth understanding before a customer complaint arrives. This article explains how EAA enforcement works, what action against inaccessible PDFs tends to look like, and what non-EU companies need to know. This is general information, not legal advice.
The EAA applies — and is enforced country by country
The European Accessibility Act (EAA, Directive (EU) 2019/882) has been in force since its obligations began applying on June 28, 2025. That date has passed; covered businesses are expected to be compliant now, not preparing to be.
Because the EAA is a directive rather than a regulation, it does not enforce itself uniformly across the bloc. Each member state had to transpose it into national law and designate its own authorities to enforce it. The substantive requirements are common everywhere — that is the point of harmonization — but the enforcement mechanics and penalties vary by country. There is no central EU agency that polices the act; the company you answer to is a national authority in the member state where the issue arises.
The technical benchmark is consistent, though. The EAA points to the harmonized standard EN 301 549, which incorporates WCAG 2.1 Level AA for web content and documents. So while the enforcer changes by country, the bar a PDF must clear does not. We cover the substance of the deadline in the companion guide on the EAA deadline for customer-facing PDFs.
The three enforcement mechanisms
In practice, EAA enforcement reaches a business through three channels, often in sequence.
Consumer complaints
The most common starting point. A consumer who cannot access a covered service — including its documents — can complain to the relevant national authority, and in many member states can also raise the matter through consumer-protection or equality bodies. A single complaint about an unreadable statement or invoice can be enough to put an organization on an authority's radar.
Market surveillance authorities
Each member state designates market surveillance authorities responsible for monitoring whether products and services on the market meet the EAA's requirements. They can act on complaints or on their own initiative, request evidence of conformity, inspect a service, and order a business to bring non-compliant offerings into line. This is administrative oversight, not court litigation — closer to how a regulator polices product safety or data protection than how a US accessibility lawsuit unfolds.
Penalties
Where a business fails to comply, member states impose penalties under their national transposition. The directive requires that penalties be effective, proportionate, and dissuasive, but the specific amounts, formats, and escalation steps differ from country to country. There is no single EU-wide fine schedule, so the financial exposure of the same failure can look different depending on where the affected consumer is.
| Element | How the EAA handles it |
|---|---|
| Who enforces | Member-state authorities (no single EU body) |
| Typical trigger | Consumer complaint or market-surveillance review |
| Mechanism | Administrative orders to correct, plus penalties |
| Penalty amounts | Set per country; "effective, proportionate, dissuasive" |
| Technical standard | EN 301 549 / WCAG 2.1 AA |
Which PDFs are in scope
The EAA is not limited to app screens and web checkout flows. Its requirements extend to the customer-facing documents that a covered service provides to consumers. For most organizations, that means the high-volume PDFs generated automatically from templates:
- Account and bank statements
- Invoices and billing documents
- Contracts, terms, and conditions
- E-commerce order confirmations and receipts
- Transport tickets and booking confirmations
This is where a lot of exposure hides. A single inaccessible statement template, multiplied across millions of customers, is exactly the systemic barrier the EAA is meant to remove — and it is the kind of thing a market surveillance authority can act on at scale. Because financial documents sit squarely in scope, financial services accessible PDFs is worth reading alongside this guide. The benchmark for each of these is EN 301 549's WCAG 2.1 AA requirements: a real text layer, tags, logical reading order, alt text, and labeled fields.
The microenterprise-services nuance
The EAA recognizes that the smallest businesses cannot carry the same compliance burden as large enterprises, but the relief is narrower than many assume.
Microenterprises that provide services — generally fewer than 10 employees and annual turnover or balance-sheet total not exceeding €2 million — are exempt from the EAA's service obligations. Two cautions matter:
- The exemption is for services, and it does not extend to products in the same way. A very small manufacturer does not automatically escape the product obligations.
- "Fewer than 10 employees" is a hard cliff. Grow past it and the exemption disappears — and any organization large enough to issue statements, invoices, or contracts at scale will almost certainly exceed it.
In short, the microenterprise carve-out helps genuine micro-service-providers, but most businesses sending customer documents at volume will not qualify.
What non-EU companies should know
A frequent and costly misconception is that the EAA is "an EU company's problem." It is not. The act is about the EU market, not the seller's headquarters. If your organization sells covered products or provides covered services to consumers in the EU, you are within reach of the act regardless of where you are based.
For a company headquartered outside the EU, the practical implications are:
- Geography of the customer, not the company, governs. Serving EU consumers brings you into scope even with no EU office.
- Enforcement is local to the consumer. A complaint and any resulting action arise in the member state where the affected consumer is, under that country's transposition and penalties.
- Your documents travel with your service. If your statements, invoices, or contracts reach EU customers as PDFs, those files must meet EN 301 549 / WCAG 2.1 AA.
For US-based organizations, the good news is that the technical work overlaps heavily with domestic obligations. A document remediated to WCAG 2.1 AA for the ADA or Section 504 is, for the most part, already meeting the EAA's document benchmark. The pillar guide on PDF accessibility lawsuits and the new wave of regulation maps how the EAA fits alongside the US regimes.
Key takeaways
- The EAA has applied since June 28, 2025 and is enforced by each member state, not a single EU body.
- Enforcement runs through consumer complaints, market surveillance authorities, and penalties that vary by country.
- Customer-facing documents — statements, invoices, contracts, tickets — are in scope, benchmarked to EN 301 549 / WCAG 2.1 AA.
- The microenterprise exemption covers small service providers under 10 employees, but most businesses issuing documents at scale will not qualify.
- Non-EU companies selling into the EU are in scope; geography of the customer governs, and WCAG 2.1 AA work done for US rules largely satisfies the EAA's document bar.
