What Does the European Accessibility Act Mean for Developers?

European Accessibility Act (EAA) compliance is mandatory by June 28, 2025, for any digital product used in Europe. Here’s what you need to know to make that happen.

Accessibility in digital experiences has long been a goal for developers, but the European Accessibility Act (EAA) introduces legal mandates that make it an imperative. With the EAA coming into effect on June 28, 2025, developers need to verify that their digital products and services comply with its accessibility standards.

In this article, we’ll break down:

• What the European Accessibility Act entails
• How it affects developers and businesses
• Recommended solutions to streamline accessibility implementation

Understanding the European Accessibility Act (EAA)

The European Accessibility Act (EAA) is a directive designed to improve accessibility across digital products and services within the European Union. It builds upon existing regulations like the Web Accessibility Directive, expanding requirements beyond public sector websites to private companies that offer digital goods and services to EU consumers. The EAA applies to various industries, including:

• Software companies – Compliance is required if you and your team build websites, mobile apps or software used in the EU.
• Ecommerce and online services – Businesses selling online must provide accessible shopping experiences.
• Banking and financial services – Digital banking apps, ATMs and payment services must be accessible.
• Transport and travel services – Ticket booking platforms, airport kiosks and travel apps must accommodate all users.

Even if a business is not based in the EU, if an app or service is used by EU residents, compliance with the EAA is required!

Technical Standards: WCAG 2.1 Level AA and EN 301 549

The European Accessibility Act (EAA) is based on WCAG 2.1 Level AA and EN 301 549, both of which define the technical accessibility requirements for digital products and services.

WCAG 2.1 Level AA (Web Content Accessibility Guidelines) establishes four core principles to test whether content is accessible to all users:

• Perceivable – Content must be presented in a way that all users can understand, including those with visual, auditory or cognitive impairments. This includes implementing alt text, captions and high-contrast themes.
• Operable – Users must be able to navigate and interact with the app using keyboards, screen readers or alternative input methods. All UI components should be focusable and usable.
• Understandable – Information should be easy to read and process. Forms, error messages, and instructions must be clear, consistent and concise.
• Robust – The app should work with assistive technologies and be compatible with evolving accessibility tools. Semantic HTML should be used to help enable compatibility across different platforms.

While WCAG 2.1 Level AA provides the foundation for web accessibility, EN 301 549, a European standard developed by ETSI under the mandate of the European Commission, extends these requirements by defining broader technical specifications, particularly for software applications, hardware and Information and Communication Technology (ICT ) products.

Under EN 301 549, additional compliance areas include:

• Assistive technology support – Verifying that software is compatible with screen readers, braille displays and alternative input methods.
• Real-time text and audio descriptions – Requirements for live captions, text transcripts and alternative communication channels.
• Hardware and operating system accessibility – Covering physical device interfaces, operating system-level features and compatibility with accessibility settings.

If your application already adheres to WCAG 2.1 Level AA, it partially meets EAA requirements. However, full compliance may require additional modifications, particularly in software interoperability, documentation and hardware integration, as outlined in EN 301 549.

For a full understanding of the technical requirements and compliance obligations, be sure to read the European Accessibility Act in detail.

What Developers Need to Do to Build Compliant Apps

The European Accessibility Act does not necessitate a complete redesign, but developers must make structured enhancements to meet compliance. Here are some areas developers can focus on to make their applications accessible:

Conduct an Accessibility Audit

Assess whether your product meets WCAG 2.1 Level AA standards using tools like axe DevTools, Lighthouse and WAVE. Perform manual testing of keyboard navigation, form usability and screen reader compatibility.

Improve Keyboard Navigation & Assistive Tech Support

Verify that all interactive elements—buttons, forms, modals, dropdowns—are fully keyboard-accessible and work with screen readers like NVDA, VoiceOver and JAWS.

Enhance Color Contrast & Readability

Maintain a minimum contrast ratio for text and avoid using color alone to indicate status. Tools like Stark and Contrast Checker can help validate contrast levels.

Use an Accessible UI Component Library

Instead of developing accessibility features from scratch, developers can accelerate compliance by integrating pre-tested, WCAG-compliant UI components. Progress Telerik and Kendo UI offer a robust set of accessibility-ready components for technologies including React, Angular, Vue and Blazor, reducing development effort in meeting compliance with WCAG 2.1, Section 508 and EN 301 549 standards.

For more details on how Telerik and Kendo UI support accessibility compliance, be sure to explore Progress’ Accessibility and Security Compliance Resources.

Curious how the Progress Telerik and Kendo UI component libraries can help? Accessibility compliance comes baked in, giving developers one less thing to figure out.

Learn more

Wrap-up

The European Accessibility Act (EAA) marks a significant step toward creating a more inclusive digital landscape. With compliance becoming mandatory by June 28, 2025, developers and businesses must prioritize accessibility in their applications. Verifying that your digital products meet WCAG 2.1 Level AA and EN 301 549 standards aligns with legal obligations, enhances user experience, broadens audience reach and reinforces a commitment to inclusivity.

By conducting accessibility audits, improving keyboard navigation, enhancing contrast and readability, and leveraging accessible UI component libraries like Telerik and Kendo UI, development teams can efficiently meet EAA requirements while streamlining implementation.

Lastly, accessibility is not just about compliance—it’s about providing equal access for all users. Taking proactive steps now can help future-proof your applications while fostering a more usable, inclusive and legally compliant digital environment.

For more details on accessibility best practices and security compliance, be sure to explore the following resources:

• European Accessibility Act (EAA) – Full Legal Text
• Human-Centered Software Design: A State of the Marketplace Report | Whitepaper
• Accessibility and Digital Experience | Fireside Chat with Neil Milliken, or watch it below: