European Accessibility Act

The European Accessibility Act (EAA) represents one of the most significant regulatory shifts for digital products and services in recent years. If you're building websites, apps, or digital experiences for users in the European Union, this legislation directly affects how you design, develop, and deliver your products.

Imagine trying to book a ticket online, only to find the website impossible to navigate with a screen reader. Or standing at a self-service kiosk that doesn't respond to voice commands when you need it most. 

For millions of people with disabilities, these aren't minor frustrations. Instead, they're barriers to participating fully in daily life. The EAA aims to eliminate these barriers by establishing consistent accessibility requirements across all EU member states.

This guide walks you through everything you need to know about the European Accessibility Act: what it covers, who it applies to, and how to prepare your digital products for compliance. 

Whether you're a UX researcher validating designs with real users, a product manager prioritizing your roadmap, or a designer creating inclusive experiences, understanding the EAA is essential for building products that work for everyone.

Key takeaways

• The European Accessibility Act (EAA) took effect on June 28, 2025, requiring products and services sold in the EU to meet accessibility standards. It applies to any business serving EU consumers, regardless of where the company is based.

• The EAA covers a wide range of digital products and services, including websites, mobile apps, ecommerce platforms, banking services, e-books, transport ticketing, and hardware with digital interfaces. Microenterprises providing services (fewer than 10 employees, under €2 million turnover) are exempt, but product manufacturers must comply regardless of size.

• The directive's requirements align with the four WCAG principles: perceivable, operable, understandable, and robust. Meeting WCAG 2.1 Level AA through the harmonized European standard EN 301 549 is widely considered the practical path to compliance.

• Products and services already on the market have a transition period until June 28, 2030, but delaying compliance carries risks including fines (up to €100,000 per violation in Germany), market access restrictions, and reputational impact.

• Preparing for compliance involves auditing your digital products, prioritizing gaps by user impact, implementing fixes systematically, and testing with real users who have disabilities. Automated tools catch only a portion of accessibility issues, so user research is essential.

• Lyssna helps teams validate EAA compliance by recruiting participants with specific accessibility needs from a panel of over 690,000 people across 124 countries. Combine usability testing, preference testing, first click tests, and surveys in a single study to identify barriers that automated audits miss.

What is the European Accessibility Act?

The EAA is the EU's most comprehensive accessibility legislation to date. Here's what it involves and why it matters.

Definition of the EAA

At its core, the EAA is a directive – meaning each EU member state must transpose it into national law. Unlike a regulation (which applies directly), the directive sets minimum requirements that countries implement through their own legislation. This approach allows some flexibility in how requirements are enforced while ensuring a consistent baseline across the EU.

Purpose and background

The EAA emerged from a recognition that accessibility requirements varied significantly across EU countries, creating barriers for both businesses and consumers. According to Craftzing's 2025 Digital Trust Index, 93% of European websites fail accessibility requirements, highlighting the urgent need for harmonized standards. Companies faced a patchwork of different national standards, while people with disabilities encountered inconsistent experiences depending on which country's products or services they used.

By harmonizing accessibility requirements, the EAA aims to:

• Remove barriers for an estimated 107 million people with disabilities in the EU – roughly one in four adults

• Create a level playing field for businesses operating across member states

• Replace fragmented national rules with unified standards, reducing regulatory complexity

• Enable businesses to operate more seamlessly across borders and deliver a consistent customer experience throughout Europe

Why the EU introduced it

The EU introduced the EAA because accessibility is a fundamental right. The directive aligns with the EU's commitments under the UN Convention on the Rights of Persons with Disabilities, which recognizes that people with disabilities have the right to participate fully in society.

Beyond rights, there's a compelling business case. An aging population means accessibility features benefit an increasingly large portion of consumers. According to the Return on Disability Group's 2024 report, people with disabilities in North America and Europe control over $2.6 trillion in disposable income – a market that businesses with inaccessible products are effectively locking out. Features designed for accessibility – like voice controls, high-contrast displays, and simplified navigation – often improve the experience for everyone.

Relationship to inclusive and accessible design

The EAA reinforces what UX researchers and designers have long understood: designing for accessibility means designing for everyone. The directive's requirements align closely with inclusive design principles that consider the full range of human diversity from the start of the design process.

Meeting EAA standards is an investment in the growth and sustainability of your business – and an opportunity to make accessibility a core strength. You'll expand your reach to a broader customer base, enhance user satisfaction, and establish your brand as a leader in inclusivity.

Test for accessibility with real users

Recruit participants with specific accessibility needs from a panel of 690,000+ people across 124 countries.

Sign up for free

Sign up for free

Sign up for free

Who does the European Accessibility Act apply to?

The EAA casts a wide net. Understanding whether your organization falls within its scope is the first step toward compliance.

Companies operating in the EU

Any business operating within the EU that provides covered products or services must comply with the EAA. This includes companies headquartered in EU member states, subsidiaries of international companies operating in the EU, and businesses with a physical presence in EU countries.

Businesses selling digital products or services to EU users

Here's where it gets interesting for global companies: the EAA applies to businesses selling to EU consumers, regardless of where the company is based. If you're a US-based software company with European customers, or an Australian ecommerce platform shipping to EU addresses, the EAA likely applies to you.

This extraterritorial reach mirrors other EU regulations like GDPR and reflects the EU's approach to protecting its consumers regardless of where businesses are located.

Public vs private sector scope

The EAA primarily targets private sector businesses, but it doesn't exist in isolation. The EU's Web Accessibility Directive (WAD) already requires public sector websites and mobile apps to meet accessibility standards. The EAA extends similar requirements to the private sector, creating a more comprehensive accessibility landscape across both sectors.

Microenterprise exemption

It's worth noting that the EAA includes an exemption for microenterprises that provide services. If your business employs fewer than 10 people and has an annual turnover (or balance sheet total) of no more than €2 million, you're exempt from the service-related requirements. However, this exemption doesn't apply to manufacturers of products covered by the EAA – they must comply regardless of size.

Cross-border implications

The harmonized nature of the EAA simplifies cross-border commerce within the EU. Instead of navigating 27 different national accessibility frameworks, businesses can work toward a single set of requirements that apply across all member states.

The following table provides a snapshot of the key industries affected by the EAA:

What products and services are covered by the EAA?

The EAA covers a specific list of products and services that the EU considers essential for daily life. Understanding what's covered helps you assess your compliance obligations.

Websites and mobile apps

Digital services delivered through websites and mobile applications fall squarely within the EAA's scope. This includes corporate websites with customer-facing functionality, mobile applications for iOS and Android, web-based applications and SaaS platforms, and customer portals and account management interfaces.

Ecommerce platforms

Online shopping platforms must ensure that users with disabilities can browse products, complete purchases, and manage their accounts. This covers everything from product catalogs and search functionality to shopping carts, checkout processes, payment interfaces, and order tracking.

Banking and financial services

Financial services have specific accessibility requirements under the EAA. This spans online and mobile banking platforms, ATMs and self-service banking terminals, payment terminals, and investment and trading platforms.

E-books and digital reading services

Digital publishing falls within the EAA's scope, covering e-book readers and reading applications, digital content distribution platforms, and accessible formatting for digital publications.

Transport and ticketing services

Transportation services must ensure accessibility across their digital touchpoints, including ticket booking websites and apps, self-service check-in kiosks, real-time travel information displays, and journey planning tools.

Hardware with digital interfaces

The EAA also covers physical products with digital components, including consumer electronics (smartphones, tablets, computers, smart TVs), self-service terminals (ticketing kiosks, check-in machines), and e-readers and digital media devices.

What's not covered

The EAA does include some notable exclusions. Pre-recorded media and office file formats published before June 28, 2025 are exempt, as are online maps (provided essential information is available in an accessible digital format) and archived website content that isn't updated or edited after June 28, 2025. B2B products and services that aren't available to consumers are also outside the EAA's scope.

European Accessibility Act requirements

The EAA's accessibility requirements align closely with established accessibility principles. While the directive doesn't mandate specific technical standards, its requirements map directly to the four principles of the Web Content Accessibility Guidelines (WCAG).

The following table summarizes the four key requirement areas and what they mean in practice:

Perceivable information

Users must be able to perceive the information being presented through at least one of their senses. Requirements include:

• Text alternatives for non-text content (images, icons, buttons)

• Captions and transcripts for audio and video content

• Sufficient color contrast between text and backgrounds

• Resizable text that maintains functionality when enlarged

• Content that conveys meaning through multiple cues, not color alone

Operable interfaces

Users must be able to operate the interface using their preferred input method. This includes:

• Keyboard accessibility for all functionality

• Sufficient time to read and use content

• Avoidance of content that causes seizures (such as flashing elements)

• Clear navigation and ways to find content

• Input modalities beyond keyboard (touch, voice where applicable)

Understandable content

Users must be able to understand the information and operation of the interface. Requirements include:

• Readable text at appropriate reading levels

• Predictable navigation and functionality

• Input assistance that helps users avoid and correct mistakes

• Consistent identification of components across the interface

• Clear instructions and error messages

Robust and compatible technology

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. This means:

• Valid, well-structured code that assistive technologies can parse

• Compatibility with screen readers and other assistive devices

• Proper use of semantic HTML and ARIA attributes

• Status messages that can be programmatically determined

European Accessibility Act and WCAG

While the EAA establishes legal requirements, WCAG provides the technical roadmap for meeting them. Understanding the relationship between these frameworks is essential for practical compliance.

How WCAG 2.1/2.2 aligns with the EAA

The Web Content Accessibility Guidelines, developed by the World Wide Web Consortium (W3C), provide detailed technical criteria for web accessibility. WCAG 2.1 Level AA is widely recognized as the benchmark for EAA compliance, though WCAG 2.2 (released in October 2023) adds nine additional success criteria that strengthen accessibility further, particularly for users with cognitive disabilities and limited fine motor skills.

In the EU, compliance is typically demonstrated through EN 301 549, the harmonized European standard for ICT accessibility. EN 301 549 incorporates the full text of WCAG 2.1 Level AA and is being updated to align with WCAG 2.2.

The EAA's functional requirements map directly to WCAG's four principles:

Why WCAG is the practical standard for compliance

Although the EAA doesn't explicitly mandate WCAG compliance, meeting WCAG 2.1 Level AA is the most practical path to demonstrating compliance. Here's why:

• Established and well-documented: WCAG provides clear, testable success criteria that leave little room for ambiguity.

• Widely adopted: Tools, training, and expertise are readily available across the accessibility industry.

• Internationally recognized: WCAG aligns with accessibility standards worldwide, making it a reliable benchmark for global organizations.

• Regularly updated: The W3C continues to evolve WCAG based on new technologies and user needs.

Differences between legal requirements and technical guidelines

The EAA is a legal requirement, while WCAG is a technical guideline. The EAA establishes what must be achieved (accessible products and services), while WCAG provides detailed guidance on how to achieve it.

This distinction matters in practice:

• Compliance is assessed against EAA requirements, not WCAG specifically.

• WCAG conformance provides strong evidence of meeting EAA requirements, but isn't the only path.

• Some EAA requirements extend beyond WCAG, particularly for hardware and non-web software.

• National implementations may reference WCAG directly or establish equivalent standards.

• EN 301 549 bridges this gap by incorporating WCAG while adding requirements for ICT products and services beyond web content.

EAA compliance deadlines and timeline

Understanding the EAA's timeline helps you plan your compliance efforts effectively and avoid last-minute scrambling.

Key enforcement dates

The European Accessibility Act took effect on June 28, 2025. From this date, new products and services placed on the EU market must meet the directive's accessibility requirements. Each of the 27 EU member states has transposed the directive into national law, meaning specific enforcement mechanisms and penalties vary by country.

Transition periods

The EAA includes transition provisions for products and services that were already on the market before the enforcement date:

• Products already on the market before June 28, 2025 may continue to be sold until June 28, 2030 under certain conditions.

• Service contracts concluded before June 28, 2025 may continue unchanged until June 28, 2030.

• Self-service terminals already in use may continue operating until the end of their economic life, up to a maximum of 20 years.

Risks of delaying compliance

Even with transition periods in place, waiting to address accessibility creates significant risks:

• Legal penalties: Non-compliance can result in fines, sanctions, or restrictions on selling products and services within the EU. Penalties vary by member state – for example, Germany allows fines of up to €100,000 per violation, while France permits penalties of up to €75,000 or 4% of annual revenue. In the US, over 4,000 digital accessibility lawsuits were filed in 2024 alone, signaling a global trend toward increasing legal enforcement.

• Market access restrictions: Non-compliant products may be removed from the EU market, limiting opportunities in one of the world's largest economies.

• Reputational impact: Customers increasingly view accessibility as a reflection of an organization's values. Demonstrating a commitment to inclusive design builds trust and loyalty.

• Reduced customer reach: Inaccessible products exclude a significant portion of the population, limiting your potential audience and reducing engagement.

How to prepare for European Accessibility Act compliance

Accessibility compliance is an ongoing commitment, not a checkbox exercise. The following step-by-step approach can help you prepare your digital products and services for EAA requirements.

Audit your digital products

Start by understanding your current accessibility status:

1. Inventory your digital products – List all websites, apps, and digital services that fall within the EAA's scope.

2. Conduct automated testing – Use tools like axe, WAVE, or Lighthouse to identify common accessibility issues.

3. Perform manual testing – Automated tools catch only a portion of issues, so manual review by accessibility specialists is essential.

4. Test with assistive technologies – Verify functionality with screen readers, keyboard navigation, and other assistive tools.

Identify and prioritize accessibility gaps

Document where your products fall short of requirements, then prioritize based on factors like user impact, frequency, legal risk, and effort to fix. A practical approach is to categorize issues by severity and map them to specific WCAG success criteria, noting which user groups are most affected by each issue. This helps your team focus resources where they'll have the greatest impact.

Design and implement fixes

Address accessibility issues systematically:

• Update your design system to include accessible components by default.

• Train your team on accessibility best practices.

• Integrate accessibility into your development workflow rather than treating it as an afterthought.

• Document accessibility decisions for future reference.

Test with real users and assistive technologies

Automated testing and expert review are valuable, but they're not enough on their own. Nucleus Research found that blind users abandon approximately two-thirds of their ecommerce transactions due to inaccessibility, highlighting the gap between technical compliance and real-world usability.

Real-world validation should include:

• Usability testing with users who have disabilities – This reveals issues that technical testing misses.

• Testing with multiple assistive technologies – Screen readers, voice control, switch devices, and magnification software.

• Gathering feedback on the actual user experience – Not just whether something technically works, but whether it works well.

Tools like Lyssna let you recruit participants who use assistive technologies, so you can validate real-world usability alongside technical compliance.

Maintain ongoing compliance

Accessibility requires continuous attention, especially as your products evolve:

• Establish regular audit schedules to catch new issues.

• Monitor for regressions when making updates.

• Stay informed about evolving standards and regulatory changes.

• Keep detailed records of your accessibility initiatives, including audit findings, updates, and user testing results.

Common accessibility issues to watch for

Certain accessibility problems appear repeatedly across digital products. Being familiar with these common issues helps you catch them early – whether through automated audits, manual review, or usability testing with real users.

The following table provides a quick overview of the most frequently encountered issues:

Color contrast

Insufficient contrast between text and background makes content difficult to read for users with low vision or color blindness. WCAG specifies the following minimum contrast ratios:

• 4.5:1 for normal text

• 3:1 for large text (18pt or 14pt bold)

• 3:1 for UI components and graphical objects

Alternative text for images

Every meaningful image needs alt text so screen reader users can understand visual content. Best practices include:

• Descriptive alt text that conveys the image's purpose

• Empty alt attributes (alt="") for purely decorative images

• Extended descriptions for complex images like charts or infographics

Keyboard navigation

Users who rely on keyboards for navigation need every interactive element to be fully operable. Common problems include:

• Interactive elements that don't receive focus

• Focus order that doesn't match visual order

• Missing visible focus indicators

• Keyboard traps that prevent users from navigating away

Form accessibility

Forms are critical interaction points that deserve special attention:

• Missing or improperly associated labels

• Error messages that screen readers don't announce

• Required fields that aren't clearly indicated

• Insufficient guidance for complex inputs

Heading structure

Headings provide structure that helps users navigate content efficiently, particularly those using screen readers. Issues to watch for include:

• Skipped heading levels (jumping from H1 to H3)

• Headings used for visual styling rather than structure

• Missing headings that would help users understand content organization

• Multiple H1 elements on a single page

How UX research and testing support EAA compliance

Technical compliance is necessary but not sufficient. Automated audits and code reviews verify that your product meets standards on paper, but user research ensures your accessibility efforts actually work for real people. By combining technical testing with research methods like usability testing, interviews, and surveys, you can identify gaps that automated tools miss and validate that your solutions genuinely improve the experience.

Accessibility usability testing

Usability testing with participants who have disabilities reveals whether your accessible design works in practice. This testing should:

• Include participants with diverse disabilities (visual, auditory, motor, cognitive)

• Use realistic tasks that reflect actual user goals

• Observe how participants use their preferred assistive technologies

• Gather both quantitative metrics and qualitative feedback

Run moderated usability testing or unmoderated usability studies to identify challenges on your websites, apps, or devices that could impact users with diverse needs.

Screen reader testing

Screen reader testing is essential for validating that your content is accessible to blind and low-vision users:

• Test with multiple screen readers (NVDA, JAWS, VoiceOver)

• Verify that all content is announced in a logical order

• Confirm that interactive elements are properly labeled

• Check that dynamic content updates are announced appropriately

User interviews

User interviews provide a deep understanding of the lived experience of using your products. Through interviews, you can learn about the workarounds users have developed, uncover pain points that testing alone might miss, and discover opportunities to exceed minimum compliance. These conversations also help your team develop a more grounded understanding of accessibility needs, which informs better design decisions over time.

Task-based testing

Structured task-based testing measures whether users can accomplish specific goals:

• Define key tasks that represent core user journeys

• Measure success rates, time on task, and error rates

• Compare performance across users with different abilities

• Identify specific barriers that prevent task completion

Surveys for accessibility feedback

Surveys help you gather accessibility feedback at scale:

• Ask users about their accessibility needs and preferences

• Collect feedback on specific features or recent changes

• Measure satisfaction among users with disabilities

• Identify areas where accessibility improvements would have the most impact

How Lyssna helps teams meet accessibility requirements

Meeting EAA requirements goes beyond checking boxes. It's about creating products that genuinely work for everyone. 

Lyssna is a remote user research platform that helps teams validate accessibility compliance through usability testing, surveys, and user interviews with real people. With tools designed for both moderated and unmoderated research, Lyssna makes it possible to test whether your digital products meet accessibility standards before enforcement deadlines.

Validate accessibility with real users

Technical audits tell you whether your code meets standards. User testing tells you whether your product actually works for people with disabilities. To test accessibility with real users, you can use the Lyssna research panel to recruit participants who use assistive technologies like screen readers, voice controls, and switch devices.

The Lyssna panel includes over 690,000 active participants across 124 countries, with targeting across 395+ demographic attributes. Most panel orders are fulfilled in under 30 minutes, so you can gather accessibility feedback quickly and keep pace with development cycles.

With Lyssna, you can:

• Recruit participants with specific accessibility needs, including screen reader users, people with motor impairments, and users with low vision

• Conduct remote usability testing that accommodates participants' preferred assistive technologies

• Capture screen, webcam, and audio recordings during unmoderated accessibility tests to see exactly how users interact with your interface

Test clarity and usability

Accessibility and usability go hand in hand. Clear, intuitive experiences benefit all users, including those who rely on assistive technologies. 

Remote user research platforms like Lyssna offer multiple testing methods you can combine in a single study to evaluate clarity and comprehension:

• Use preference testing to compare design alternatives for readability, contrast, and visual hierarchy

• Run first click tests to validate that navigation is intuitive for users with diverse abilities

• Conduct five second tests to assess whether key information is immediately comprehensible, which directly supports WCAG success criteria for readability and predictability

Identify friction points

Discover where users struggle before those struggles become compliance issues:

• Watch session recordings to observe where users encounter barriers with forms, navigation, or interactive elements

• Analyze task completion rates and time-on-task metrics to pinpoint problematic flows

• Collect open-ended feedback about specific accessibility challenges users face in your product

Pro tip: Use Lyssna's demographic filters to recruit participants with specific accessibility needs, such as screen reader users or people with motor impairments, so you can validate your designs with the people who will be most affected by accessibility decisions.

Support inclusive, user-centered design

Lyssna helps you build accessibility into your design process from the start, so compliance becomes a natural outcome rather than a last-minute scramble:

• Test early concepts with diverse users before investing in development

• Validate that accessibility improvements actually enhance the user experience

• Build a culture of inclusive design through regular user feedback

For teams preparing for EAA compliance, Lyssna combines fast participant recruitment, flexible research methods, and built-in analysis tools in a single platform, reducing the need to piece together multiple tools to validate accessibility.

Start testing for EAA compliance today 

Try Lyssna for free to run usability tests with participants who use assistive technologies – and catch barriers automated audits miss.

Sign up for free

Sign up for free

Sign up for free

FAQs about the European Accessibility Act

What is the European Accessibility Act?

When does the EAA take effect?

Does the EAA apply to businesses outside the EU?

What's the difference between the EAA and WCAG?

Do I need to meet WCAG 2.1 or WCAG 2.2?

What are the penalties for non-compliance?

Are there any exemptions from the EAA?

How do I know if my product is compliant?

How often should I audit my products for accessibility?

Pete Martin

Content writer

Pete Martin is a content writer for a host of B2B SaaS companies, as well as being a contributing writer for Scalerrs, a SaaS SEO agency. Away from the keyboard, he’s an avid reader (history, psychology, biography, and fiction), and a long-suffering Newcastle United fan.