European Accessibility Act and EN 301 549: Your Complete Compliance Guide

Learn how the EAA, EN 301 549 standard, and WCAG work together to define accessibility requirements in the EU—including compliance deadlines, scope, and the steps your organization needs to take.

Navigating accessibility rules in the EU can be complex. It requires understanding how the European Accessibility Act (EAA), European standards, and the Web Content Accessibility Guidelines (WCAG) relate to each other.

If you have a website, mobile app, or e-commerce platform serving customers in the EU, you are required to make your digital content accessible to everyone, including people with disabilities. The EAA sets out these requirements, and as of June 28, 2025, enforcement is now in effect.

This guide explains what the European Accessibility Act requires, what EN 301 549 is and how it functions as the harmonized standard for compliance, and the practical steps your organization needs to take to meet these accessibility requirements.

European Accessibility Act Overview

The European Accessibility Act is EU legislation requiring certain digital products and services to be accessible to all users, regardless of disability. Its main goal is to ensure equal access to digital solutions throughout the EU, benefiting both people with disabilities and businesses operating in the internal market.

EAA Compliance Timeline

The critical dates every organization should know:

• June 28, 2019 — EAA adopted by the European Parliament
• June 28, 2022 — Deadline for EU member states to transpose into national law
• June 28, 2025 — Enforcement began for most products and services
• June 28, 2030 — Extended deadline for certain self-service terminals

Since June 28, 2025, non-compliance can result in penalties, fines, and removal of products from the EU market. The exact consequences vary by member state, as each country implements its own enforcement mechanisms through national legislation.

Who Must Comply With the EAA?

The EAA applies to private-sector organizations selling products or services in the EU. Key sectors include:

• E-commerce — Online shops and marketplaces
• Banking and financial services — ATMs, online banking, payment terminals
• Telecommunications — Phone services, messaging apps, customer service
• Transportation — Booking systems, check-in kiosks, real-time travel information
• E-books and e-readers — Digital publications and reading devices
• Audio-visual media services — Streaming platforms and broadcast content

Does the EAA Apply to US Companies?

Yes. Any organization selling products or services to EU customers must comply, regardless of where the company is headquartered. A US-based e-commerce site serving European customers falls under EAA requirements. This cross-border reach makes the EAA relevant for multinational organizations managing compliance across multiple jurisdictions.

What Is EN 301 549?

EN 301 549 is the harmonized European standard for digital accessibility. It provides the technical specification that defines what "accessible" means under EU law.

The EN 301 549 standard covers accessibility requirements for ICT products and services, including websites, mobile applications, software, hardware, and electronic documents. Following EN 301 549 creates a "presumption of conformity" with the EAA—meaning regulators will presume your products meet legal requirements if you comply with the standard.

EN 301 549 Standard: Latest Version

The current version is EN 301 549 v3.2.1, published in 2021. This version aligns with WCAG 2.1 Level AA and extends beyond web content to address:

• Non-web software — Desktop applications, mobile apps, operating systems
• Non-web documents — PDFs, Word documents, spreadsheets, presentations
• Hardware — Self-service terminals, kiosks, telecommunications equipment
• ICT with closed functionality — Devices where users cannot install assistive technologies

EN 301 549 Scope: Beyond Websites

While websites and web applications are covered in Chapter 9 of EN 301 549, the standard addresses much more:

• Chapter 5 — Generic requirements including closed functionality, biometrics, and preservation of accessibility information
• Chapter 6 — ICT with two-way voice communication, including text-to-speech, real-time text, and video communication
• Chapter 7 — ICT with video capabilities, including audio description and closed captions
• Chapter 8 — Hardware requirements for physical products
• Chapter 9 — Web content (directly references WCAG 2.1)
• Chapter 10 — Non-web documents
• Chapter 11 — Non-web software
• Chapter 12 — Documentation and support services
• Chapter 13 — ICT providing relay or emergency services

This comprehensive scope means organizations must consider accessibility across their entire ICT ecosystem—not just their website.

What Is the Difference Between WCAG and EN 301 549?

WCAG (Web Content Accessibility Guidelines) is the internationally recognized framework for web content accessibility, developed by the W3C. EN 301 549 is the European standard that incorporates WCAG while adding requirements for non-web contexts.

How EN 301 549 Extends WCAG

For web content, EN 301 549 Chapter 9 directly references WCAG 2.1 Level A and AA success criteria. However, EN 301 549 goes further:

• Mobile applications — While WCAG applies conceptually, EN 301 549 Chapter 11 provides specific requirements for native mobile apps, including gesture alternatives and orientation support.
• Documents — EN 301 549 Chapter 10 addresses PDFs and office documents, requiring features like proper heading structure, reading order, and accessible tables.
• Hardware interfaces — Requirements for physical controls, displays, and audio output that WCAG doesn't cover.
• Biometrics — When biometric identification is used, alternatives must be provided for users who cannot use the biometric method.
• Real-time communication — Requirements for video calling, text-to-speech, and voice communication accessibility.

Understanding these differences is essential for organizations managing compliance across multiple product types.

What Is the Difference Between the ADA and the EAA?

Organizations operating in both the US and EU must understand how these laws differ:

Americans with Disabilities Act (ADA) — US civil rights law prohibiting discrimination against people with disabilities. For websites, courts have interpreted Title III to require accessibility, but the law doesn't specify technical standards. Most organizations reference WCAG 2.0 or 2.1 as the benchmark.

European Accessibility Act (EAA) — EU directive specifically addressing digital accessibility with explicit reference to harmonized standards (EN 301 549). More prescriptive about which products and services must comply.

Key differences:

• The ADA applies to "places of public accommodation" (interpreted to include websites); the EAA lists specific product/service categories
• The ADA enforcement primarily comes through private lawsuits; the EAA uses market surveillance and regulatory enforcement
• The EAA explicitly references EN 301 549; the ADA has no official technical standard (though WCAG is commonly used)

ADA Changes for April 2026

Note that the US Department of Justice finalized new ADA Title II regulations requiring state and local government websites to meet WCAG 2.1 Level AA by April 2026 (or April 2027 for smaller entities). While this applies to public-sector websites rather than the private-sector focus of the EAA, it signals global momentum toward WCAG-based accessibility requirements.

The Five Major Accessibility Standards

For organizations managing global compliance, understanding the landscape of accessibility standards helps prioritize efforts:

1. WCAG (Web Content Accessibility Guidelines) — International standard for web accessibility, developed by W3C. Current version is WCAG 2.2.
2. EN 301 549 — European harmonized standard incorporating WCAG plus additional ICT requirements.
3. Section 508 — US federal accessibility requirements for government ICT, aligned with WCAG 2.0 Level AA.
4. AODA (Accessibility for Ontarians with Disabilities Act) — Canadian provincial standard requiring WCAG 2.0 Level AA compliance.
5. ISO 40500 — International standard identical to WCAG 2.0, providing ISO recognition of the guidelines.

For most organizations, meeting WCAG 2.1 Level AA provides a strong foundation that satisfies requirements across multiple jurisdictions.

EN 301 549 Accessibility Requirements: What You Must Do

Meeting EN 301 549 requirements involves both technical implementation and documentation. Here's a step-by-step approach:

Step 1: Assess Your Scope

Identify all ICT products and services that must comply:

• Websites and web applications
• Mobile apps (iOS, Android)
• Self-service terminals and kiosks
• Electronic documents (PDFs, forms)
• E-commerce platforms
• Customer support systems

Step 2: Audit Current Accessibility

Conduct a comprehensive accessibility audit against EN 301 549 requirements. For web content, this means testing against WCAG 2.1 Level AA success criteria.

Tools like Acquia Web Governance provide automated scanning to identify accessibility issues, referencing relevant WCAG criteria and highlighting potential barriers. However, automated tools detect only 30-40% of issues—manual testing and user testing with people with disabilities are essential.

Step 3: Prioritize and Remediate

Focus remediation efforts on:

• High-impact pages — Homepage, key landing pages, checkout flows, account management
• Critical user journeys — The paths users take to complete essential tasks
• Common issues — Low contrast, missing alt text, keyboard traps, form labeling

Step 4: Create Your Declaration of Conformance

EN 301 549 Annex B and C outline requirements for accessibility statements and declarations of conformance. Your declaration should include:

• Scope — Which products/services the declaration covers
• Standards referenced — EN 301 549 version, WCAG level
• Conformance status — Full conformance, partial conformance with exceptions, or non-conformance
• Known limitations — Documented accessibility barriers with remediation plans
• Contact information — How users can report accessibility issues
• Date — When the assessment was conducted

This documentation demonstrates good-faith compliance efforts and provides evidence for regulators.

Step 5: Establish Ongoing Monitoring

Accessibility isn't a one-time project. As content and code evolve, new issues can emerge. Schedule regular automated scans, periodic manual audits, and ongoing team training to maintain compliance.

Common Pitfalls to Avoid

Relying Only on Automation

Automated tools detect barriers that are testable in a binary manner—whether images have alt text, whether form fields have labels. But tools cannot determine whether alt text is meaningful or whether content is actually understandable. Manual reviews and user testing (especially with people with disabilities) are essential.

Ignoring Non-Web Content

Organizations often focus exclusively on websites while ignoring mobile apps, PDFs, and other ICT products covered by EN 301 549. Ensure your compliance program addresses the full scope of covered products.

Treating Accessibility as a One-Time Project

Even after initial fixes, new accessibility issues emerge as content changes. Country-specific requirements may also evolve as member states refine their implementation. Build accessibility into ongoing workflows rather than treating it as a project with an end date.

Lack of Team Training

Without adequate training, teams inadvertently introduce accessibility barriers during day-to-day work. Content editors, developers, designers, and procurement managers all need to understand accessibility requirements relevant to their roles.

Why Accessibility Matters Beyond Compliance

Digital accessibility is the business imperative we can't ignore. Crafting accessible digital experiences isn't just about meeting legal standards—it's about creating inclusive experiences for every user.

Consider the business case:

• Market reach — Over 100 million people in the EU have some form of disability. Accessible products serve this significant market.
• SEO benefits — Accessible websites often rank better because clean code, proper headings, and descriptive content help search engines understand your site.
• Improved UX — Accessibility improvements benefit all users, not just those with disabilities. Clear navigation, readable text, and logical layouts make sites easier for everyone.
• Reduced legal risk — Proactive compliance avoids costly litigation, regulatory fines, and reputational damage.

Take the Next Step in Your Accessibility Strategy

Successfully meeting EU accessibility obligations means understanding how the European Accessibility Act, the harmonized standard EN 301 549, and WCAG guidelines work together. With the June 28, 2025 deadline now passed, organizations that haven't yet achieved compliance need to act immediately.

Using a tool like Acquia Web Governance helps you test and prioritize web accessibility in line with these requirements. But remember that automated checks alone aren't enough. Regular reviews, manual assessments, and ongoing training for your team are essential for staying compliant and delivering accessible digital experiences.

Don't wait to create inclusive digital experiences for all. Get a free website scan with Acquia Web Governance and start your compliance journey today.