The EAA and the ADA are two separate laws with different origins, scopes, and enforcement models, but both push companies toward the same technical standard: WCAG conformance. The European Accessibility Act (EAA) is an EU directive that went into effect on June 28, 2025, and applies to specific products and services sold in EU member states. The Americans with Disabilities Act (ADA) is a US civil rights law from 1990 that has been applied to websites and digital assets through court interpretation and newer regulations like the ADA Title II web rule. If your company sells into both markets, you need to meet both sets of requirements.
| Factor | EAA | ADA |
|---|---|---|
| Jurisdiction | EU member states | United States |
| Type of law | EU directive, transposed nationally | Federal civil rights statute |
| Covered entities | Companies selling listed products and services in the EU | Public accommodations (Title III) and state or local government (Title II) |
| Technical standard | EN 301 549, which references WCAG 2.1 AA | WCAG 2.1 AA (Title II rule); courts generally apply WCAG 2.1 AA for Title III |
| Key date | Went into effect June 28, 2025 | ADA enacted 1990; Title II web rule deadlines in 2026 and 2027 |
| Enforcement | National market surveillance authorities, fines, product withdrawal | DOJ action, private lawsuits, demand letters |
What the EAA covers
The EAA is a directive that each EU member state transposes into national law. It targets specific products and services, including ecommerce websites, banking services, e-books and reading software, ticketing and check-in machines, passenger transport services, and consumer computing hardware.
A US company is not outside the scope of the EAA because it is based in the US. If you sell covered products or services to consumers in the EU, the directive applies to that activity. Microenterprises providing services get a limited exemption, but product manufacturers do not.
The technical reference is EN 301 549, the European accessibility standard for ICT. For web content and mobile apps, EN 301 549 points to WCAG 2.1 Level AA as the conformance target.
What the ADA covers
The ADA is broader in purpose and narrower in its explicit mention of digital content. Title II covers state and local government entities. Title III covers places of public accommodation, which courts have extended to most commercial websites operated by private businesses.
The DOJ finalized the ADA Title II web rule in 2024, setting WCAG 2.1 AA as the required standard. Larger public entities have a compliance date of April 24, 2026, and smaller entities have until April 26, 2027. Title III has no codified technical standard, but WCAG 2.1 AA is the practical benchmark used in settlements and court rulings.
Enforcement on the private side is driven heavily by plaintiff-side law firms. Demand letters and lawsuits most often target ecommerce, retail, restaurants, and hospitality.
How do the standards actually compare?
Both regimes land on WCAG 2.1 AA for web content, which means the day-to-day work for a website or mobile app is largely the same. A thorough (manual) accessibility evaluation against WCAG 2.1 AA identifies the issues you need to address for both.
The differences show up around the evaluation. EN 301 549 includes requirements that go beyond WCAG, covering hardware, two-way voice communication, and certain functional performance statements. For a pure web or mobile project, most of that extra material is not in play, but it can matter for ICT products.
The ADA, by contrast, does not add technical requirements on top of WCAG. It adds legal exposure: private lawsuits, demand letters, and DOJ action if a public entity misses the Title II deadlines.
Documentation and how companies prove conformance
For the EAA, companies placing products on the EU market need technical documentation and, for products, an EU declaration of conformity. Services in scope need accessibility information made available to consumers.
For US procurement and private-sector conformance claims, the common artifact is an Accessibility Conformance Report (ACR) produced using a VPAT template. The WCAG edition of the VPAT is the default for most SaaS companies. The EN 301 549 edition is the right fit when the buyer is an EU public body or a company asking specifically about EAA scope.
A single evaluation against WCAG 2.1 AA can feed both an ADA-facing ACR and EAA documentation, provided the evaluator maps results to the correct criteria for each.
Which one applies to your company?
Both can apply at once. A US ecommerce brand shipping to consumers in Germany is subject to ADA exposure in the US and EAA obligations in the EU. A European SaaS product sold to US public universities maps to the EAA at home and ADA Title II on the buyer side.
The practical approach is to confirm your digital assets against WCAG 2.1 AA through a real evaluation, then layer the jurisdiction-specific documentation on top. That covers the common technical ground and then addresses the legal and procurement requirements that differ between the two regimes.
Frequently asked questions
Does meeting the ADA mean I meet the EAA?
Not automatically. The web and mobile overlap is strong because both reference WCAG 2.1 AA, but the EAA covers product categories and documentation requirements that the ADA does not address. If your product is in EAA scope, you need EAA-specific documentation regardless of your ADA posture.
If I am a small US business with no EU customers, do I need to worry about the EAA?
No. The EAA applies when you place covered products or offer covered services in the EU market. If you do not sell into the EU, your focus is the ADA and any state-level accessibility laws that apply to you.
Which WCAG version should my evaluation target?
WCAG 2.1 AA is the baseline for both the EAA (through EN 301 549) and the ADA Title II web rule. Some buyers and private-sector contracts now request WCAG 2.2 AA, which is a superset of 2.1 AA and a reasonable forward-looking target.
Can one evaluation support both EAA and ADA documentation?
Yes. A single WCAG 2.1 AA evaluation of your website or mobile app can support an ACR for US buyers and feed the accessibility information required under the EAA. The evaluator needs to know both outputs are in scope so results are mapped correctly.
The EAA and the ADA answer different questions in different legal systems, but the technical work underneath is nearly the same. Get the evaluation right against WCAG 2.1 AA and the jurisdiction-specific documentation becomes a much smaller lift.
Contact Accessible.org to discuss EAA and ADA conformance for your digital assets: Contact Accessible.org.
