The European Accessibility Act: What It Means for Your Website and When to Act

The European Accessibility Act (EAA) — Directive 2019/882 — is the most significant accessibility regulation in European history. It became applicable on June 28, 2025, and requires a wide range of products and services to meet accessibility standards. If you operate a digital product or service accessible to EU consumers, this affects you.

What the EAA requires

The EAA mandates that certain products and services be accessible to persons with disabilities. For digital services, this means conforming to the harmonized European standard EN 301 549, which in turn references WCAG 2.1 Level AA.

• E-commerce services — Any website or app that sells products or services
• Banking services — Online banking, payment terminals
• Telecommunications — VoIP, messaging services
• Transport services — Booking systems, ticketing, real-time travel information
• E-books and e-readers — Digital publishing platforms
• Audio-visual media services — Streaming platforms

Who it applies to

The EAA applies to economic operators — manufacturers, importers, distributors, and service providers — that offer covered products or services in the EU market. There's a microenterprise exemption for service providers with fewer than 10 employees and annual turnover under €2M, but this exemption is narrow.

Key point: You don't need to be based in the EU. If EU consumers can access your service, you're in scope.

WCAG 2.1 AA in practice

• Perceivable — Information must be presentable in ways all users can perceive (alt text, captions, sufficient contrast)
• Operable — Interface components must be operable by all users (keyboard navigation, no time limits, no seizure-inducing content)
• Understandable — Information and interface must be understandable (readable text, predictable behavior, input assistance)
• Robust — Content must be robust enough to work with assistive technologies (semantic HTML, ARIA attributes)

EN 301 549: The European standard

• Web content (mapped to WCAG 2.1 AA)
• Non-web software (mobile apps, desktop applications)
• Hardware products
• Documentation and support services

For web-based services, compliance with WCAG 2.1 AA satisfies the EN 301 549 web content requirements. But EN 301 549 goes further — it also covers software, documentation, and customer support accessibility.

Enforcement and penalties

• Fines — Administrative penalties, often proportional to revenue
• Market surveillance — Products and services can be removed from the market
• Consumer complaints — Users can file accessibility complaints with national authorities
• Legal action — Some member states allow private lawsuits

Practical steps to prepare

• Audit your website against WCAG 2.1 AA using automated tools and manual testing
• Fix critical issues first — Missing alt text, keyboard traps, insufficient contrast, form label issues
• Publish an accessibility statement — This is required under the EAA and should describe your conformance level, known issues, and contact information
• Establish a process — Accessibility isn't a one-time fix. Build it into your design, development, and QA processes
• Train your team — Developers, designers, and content creators all play a role

The accessibility statement

• Conformance level (full, partial, or non-conformant)
• Known accessibility limitations
• Remediation timeline for known issues
• Contact mechanism for accessibility feedback
• Link to the relevant enforcement body

ShieldPage's upcoming accessibility module will generate compliant accessibility statements linked to your trust center — making it easy to maintain and update as your accessibility posture improves.