If you’re trying to meet the digital accessibility requirements of the European Accessibility Act (EAA), the WCAG 2.1 AA standard simplifies the process. While the EAA doesn’t require WCAG conformance, it’s technical requirements for purely digital assets aligns with WCAG.
For websites, apps, e-books, and other digital services covered by the EAA, following WCAG 2.1 AA is the most straightforward way to comply. And, if you opt for the WCAG 2.2 AA standard, you can future proof your efforts against regulatory updates.
Keep in mind that there are other administrative requirements beyond the EAA’s technical accessibility requirements so EAA compliance is not just about technical accessibility.
Why WCAG 2.1 AA Works for the EAA
The EAA sets out functional requirements for accessibility. It doesn’t prescribe specific technologies or testing methods. Instead, it focuses on outcomes—such as content being perceivable, operable, understandable, and robust.
These four principles are the exact foundation of WCAG (Web Content Accessibility Guidelines). This means WCAG 2.1 AA effectively maps to the digital accessibility expectations in Annex I of the Directive.
By implementing WCAG 2.1 AA, organizations address:
- Visual access (text alternatives, contrast, scaling)
- Keyboard operation and focus order
- Navigation clarity
- Input assistance and error identification
- Compatibility with screen readers and assistive technology
In short, WCAG covers the types of accessibility barriers the EAA is trying to remove.
What WCAG Covers Under the EAA
WCAG 2.1 AA helps ensure conformance for these EAA-covered digital services:
- Websites and web apps
- Mobile applications
- Online banking and financial services
- E-commerce platforms
- E-books and their reading software
- Transport service websites and apps
- Interfaces for audiovisual media (like TV guides)
All of these are required to be accessible under the EAA—and all can meet their obligations using WCAG 2.1 AA as a technical reference.
What WCAG Does Not Cover
WCAG is focused on web accessibility, so it doesn’t cover everything the EAA regulates. It doesn’t apply to:
- Hardware (e.g., ATMs, ticket machines)
- Operating systems
- Consumer electronic devices
- Built environments (physical locations)
- Emergency communication devices and interfaces
For those, the EAA provides additional functional requirements in its annexes. WCAG can’t replace those criteria but can supplement them for any digital interface component.
WCAG 2.1 AA as Your Foundation
If you’re delivering digital services in the EU, WCAG 2.1 AA offers a clear, internationally accepted, and widely supported framework to follow.
It makes conformance with the EAA’s digital requirements simpler, more predictable, and more defensible.
For most product and service providers, meeting the EAA’s technical requirements is as simple as WCAG 2.1 AA conformance.
Services and Training
Our WCAG Course can train your team on the Web Content Accessibility Guidelines.
Also, our Accessibility Tracker app allows you to track progress of your accessibility project and demonstrate compliance.
We also offer audits and consulting to help with EAA compliance. Just send us a message and we’ll be right back with you.
