European Accessibility Act (EAA)

Understanding Digital Accessibility Compliance

The June 2025 EAA deadline has passed. If you offer digital products or services in the EU, accessibility compliance is now mandatory. This guide explains what digital accessibility means, who it helps, which businesses must comply, and practical steps to meet your obligations across WCAG, EAA, and ADA requirements.

Assess your compliance See common accessibility issues
Last updated: December 2, 2025 For businesses serving NL & EU markets

My Expertise

Government Compliance Experience

Former Digital Content Specialist at NY State Comptroller's Office

Tri-Market Expertise

Serving Netherlands, EU, and US compliance requirements

Standards Compliance

WCAG 2.2 AA | EN 301 549 | Section 508 | ADA Title III

Practical Focus

Accessibility that ships, not theoretical perfection

What is accessibility?

Digital accessibility means designing websites, apps, and documents so that people with disabilities can perceive, understand, navigate, and interact with them effectively.

This isn't about perfection or following every possible guideline. It's about removing barriers that prevent people from completing tasks—purchasing products, reading content, filling out forms, watching videos, or accessing information they need.

The practical reality is accessible design works better for everyone. What's necessary for some improves the experience for all.

Who benefits?

Accessibility considerations help people with various circumstances and abilities. Understanding who benefits helps prioritize the most impactful improvements.

Visual disabilities

People who are blind, have low vision, or are colorblind. They may use screen readers, screen magnification, or rely on sufficient color contrast.

Need: Alt text, proper heading structure, keyboard navigation, adequate contrast ratios

Auditory disabilities

People who are deaf or hard of hearing. They can't access audio-only content without text alternatives.

Need: Captions for videos, transcripts for audio content, visual indicators for sound alerts

Motor disabilities

People with limited dexterity, tremors, or paralysis. They may use keyboards, voice control, or adaptive devices instead of a mouse.

Need: Keyboard accessibility, large click targets, sufficient time to complete tasks

Cognitive disabilities

People with learning disabilities, memory challenges, or attention difficulties. Complex layouts or unclear language create barriers.

Need: Plain language, clear instructions, consistent navigation, error prevention

Situational disabilities matter too

Someone with perfect vision still can't watch an uncaptioned video in a noisy cafe. Someone with full mobility still struggles with tiny mobile buttons while standing on a moving train. Accessible design accounts for circumstances, not just permanent disabilities.

EAA vs WCAG vs ADA

These three frameworks work together but serve different purposes. Understanding how they relate helps you navigate compliance requirements across different markets.

Aspect EAA WCAG ADA
Creates legal obligation ✓ ✓
Defines technical rules ✓
Applies in EU ✓
Applies in US ✓
Used as accessibility benchmark ✓ ✓ ✓

European Accessibility Act (EAA)

EU law requiring accessibility for digital products and services. References EN 301 549 (which adopts WCAG 2.1 AA).

Web Content Accessibility Guidelines (WCAG)

International technical standard defining how to make web content accessible. Current version: WCAG 2.2.

Americans with Disabilities Act (ADA)

US civil rights law. Courts typically reference WCAG 2.1 AA as the compliance standard for digital properties.

The practical reality:

If you meet WCAG 2.2 Level AA, you satisfy the technical requirements for both EAA and ADA compliance. The frameworks differ in legal enforcement and scope, but converge on the same accessibility standards.

Is your business EAA compliant?

Answer these questions to understand your compliance obligations and current accessibility posture. This assessment provides guidance and is not legal advice.

Quick Reference: EAA Coverage

The European Accessibility Act applies to businesses that:

  • Serve EU consumers — You sell products, offer services, or provide digital content to people in EU member states
  • Operate in covered sectors — E-commerce, banking, telecommunications, transport, e-books, or digital services
  • Meet size thresholds — Companies with 10+ employees or €2M+ annual turnover (microenterprises may have exemptions)

Covered Industries

  • • E-commerce and online retail
  • • Banking and financial services
  • • Telecommunications
  • • Transport booking and ticketing
  • • E-books and digital publishing
  • • SaaS and cloud services

Key Deadlines

  • • June 28, 2025: New services must be compliant (passed)
  • • June 28, 2030: Existing services deadline
  • • Now: Enforcement is active
  • • Risk: Complaints trigger investigations

What enforcement looks like

  • Member state authorities: Each EU country designates enforcement bodies that can investigate complaints, conduct audits, and impose penalties.
  • Penalties vary by country: Fines can reach up to 4% of annual turnover in some jurisdictions, though initial enforcement typically focuses on compliance orders rather than maximum penalties.
  • Complaint-driven process: Most enforcement begins with accessibility complaints from users or advocacy organizations, not random audits.
  • Good-faith effort matters: Demonstrating active remediation work and a clear compliance roadmap can influence enforcement outcomes.

Good vs bad examples

Visual examples showing common accessibility barriers and their solutions. Each is prioritized by impact on users and compliance risk.

Critical

Form Labels

WCAG 3.3.2
Less Accessible Missing labels
<input type="text" placeholder="Email">

Screen reader users have no idea what to enter. This blocks form completion entirely.

More Accessible Clear, visible labels
<label for="email">Email</label>
<input id="email" type="text">

Every field has a label that's programmatically associated and visible to all users.

Critical

Color Contrast

WCAG 1.4.3
Less Accessible Low contrast text

This is important information about your account.

Please review carefully before proceeding.

Contrast ratio: 2.8:1 ❌

Thin, light gray text is unreadable for users with low vision. Fails WCAG AA (needs 4.5:1).

More Accessible Sufficient contrast

This is important information about your account.

Please review carefully before proceeding.

Contrast ratio: 12.6:1 ✓

Dark text on light background exceeds WCAG AA standards, readable for everyone.

Important

Focus Indicators

WCAG 2.4.7
Less Accessible No visible focus

Press Tab to try keyboard navigation

button:focus { outline: none; }

Keyboard users can't tell which button is active. Navigation becomes guesswork.

More Accessible Clear focus ring

Visible outline shows keyboard focus

button:focus {
  outline: 2px solid #000;
}

Visible outline shows which element has keyboard focus at all times.

Important

Error Messages

WCAG 3.3.1
Less Accessible Color-only error

Red border doesn't help screen reader users or people with color blindness understand what's wrong.

More Accessible Clear text error

⚠ Please enter a valid email address

Explicit text explains what's wrong and how to fix it. Works for everyone.

Enhancing

Heading Structure

WCAG 2.4.6
Less Accessible Visual-only hierarchy
Features
Security
Performance
<div class="big-text">Features</div>

Text is styled to look like headings but uses divs. Screen readers can't navigate document structure.

More Accessible Semantic heading levels

Features

Security

Performance

<h2>Features</h2>
<h3>Security</h3>

Proper h2/h3 structure creates logical outline. Screen readers can jump between headings.

Enhancing

Link Text

WCAG 2.4.4
Less Accessible Generic link text

Read our accessibility statement. Click here

<a href="/statement">Click here</a>

Screen readers can list all links. "Click here" provides zero context out of context.

More Accessible Descriptive link text

Learn about our commitment to digital accessibility. Read our accessibility statement

<a href="/statement">Read accessibility statement</a>

Link text describes the destination. Makes sense even out of context.

EAA adoption by industry

Estimated compliance readiness across key sectors as of November 2025

E-commerce ~40% compliant
Banking & Financial Services ~65% compliant
Transport & Ticketing ~50% compliant
Telecommunications ~55% compliant
Digital Publishing ~35% compliant
SaaS & Cloud Services ~45% compliant

Data based on industry surveys and compliance monitoring reports. Individual company compliance may vary.

Common questions

Can I use an accessibility overlay or plugin instead of fixing my site?

Short answer: No. Overlays do not provide compliance and often create additional barriers.

Accessibility overlays promise one-click compliance through JavaScript widgets that attempt to modify your site on the fly. In practice, they introduce new accessibility issues, don't address underlying problems, and create frustrating experiences for people actually using assistive technology.

Multiple disability advocacy organizations have explicitly stated that overlays are not acceptable solutions. Courts have found that websites using overlays are still not accessible. The only reliable path to compliance is fixing the actual code, content, and design.

Does my small business really need to comply with EAA?

It depends on your business size, sector, and what you sell. Microenterprises (fewer than 10 employees AND under €2 million annual turnover) may qualify for exemptions in some member states, but this varies by country and service type.

However, even if you're exempt from EAA specifically, you may still face accessibility requirements under national disability discrimination laws, consumer protection regulations, or if you serve government clients.

The pragmatic view is by making your digital properties accessible expands your potential customer base and reduces business risk. The technical fixes that satisfy EAA also improve usability for all customers.

What happens if I'm not compliant?

Enforcement varies by EU member state, but typically begins with accessibility complaints from users or advocacy organizations rather than random audits.

The process usually starts with an investigation by national enforcement authorities. If found non-compliant, businesses typically receive a compliance order requiring specific fixes within a timeframe. Continued non-compliance can lead to fines—which can reach up to 4% of annual turnover in some jurisdictions.

More commonly, the real business impact comes from users abandoning inaccessible checkout processes, reputational damage from accessibility complaints, exclusion from government procurement, and increased support costs from users who can't complete tasks independently.

How long does accessibility remediation take?

It depends heavily on your starting point and site complexity. Here are realistic timelines:

Small business site (10-20 pages): 4-8 weeks for WCAG 2.2 AA compliance with focused effort.

Medium e-commerce site (50-100 pages): 3-6 months for comprehensive remediation, depending on custom components.

Large platform (1000+ pages): 6-18 months, typically tackled in phases prioritizing high-traffic and business-critical pages first.

The first 30 days can address the most critical barriers. Full compliance takes longer but doesn't mean you can't launch improvements incrementally.

Can I just make a separate accessible version of my site?

No. Separate "accessible versions" are explicitly not acceptable under EAA, ADA, and disability discrimination laws. They create "separate but equal" experiences that are inherently discriminatory.

Separate versions are also impractical and will require maintaining two codebases. This will inevitably diverge in content and features and signal to users with disabilities that they're second-class customers.

The correct approach is making your main site accessible to everyone. This is both legally required and better for your business.

Do I need to make PDFs and Office documents accessible too?

Yes. The EAA specifically includes document accessibility requirements. PDFs, Word documents, PowerPoint presentations, and Excel spreadsheets must all be accessible if they're provided to consumers.

For PDFs, this means proper tagging, reading order, alt text for images, and semantic structure. For Office documents, it means using built-in heading styles, adding alt text, ensuring tables are marked as data tables, and using sufficient color contrast.

Document accessibility is often overlooked but critical with many business processes rely on forms, invoices, product specifications, and user guides distributed as documents.

Is automated testing enough to prove compliance?

No. Automated testing tools can detect approximately 30-40% of accessibility issues. They're excellent for catching obvious problems like missing alt text, contrast failures, and HTML validation errors.

However, they can't evaluate whether alt text is actually descriptive, whether keyboard navigation follows a logical order, whether instructions are clear, or whether the experience makes sense to someone using a screen reader.

True compliance requires automated testing + manual keyboard testing + screen reader testing + review by people with disabilities when possible.

When to get professional help

While the resources above help with self-service accessibility improvements, some situations benefit from specialist guidance.

You might need professional help if:

  • You've received an accessibility complaint or legal notice
  • Your site serves thousands of users and needs systematic remediation
  • You need WCAG conformance testing for regulatory submission
  • Your development team lacks accessibility expertise
  • You're building a new product and want to avoid remediation costs
  • You need accessibility documentation for procurement

Services available:

WCAG 2.2 Audits

Comprehensive evaluation against WCAG 2.2 Level AA standards with detailed remediation guidance.

Remediation Support

Hands-on development assistance to fix accessibility issues in existing sites.

Training & Workshops

Team education on accessible development practices and testing methods.

Ongoing Compliance

Monthly accessibility reviews and testing as new features ship.

About this guide

This guide was created by Joe Gullo, a digital accessibility consultant based in Leiden, Netherlands. I bring 16+ years of digital experience to Dutch, European, and US markets, including 6 years as Digital Content Specialist at the New York State Comptroller's Office where I specialized in accessibility compliance. My approach emphasizes accessibility that actually ships, with solutions that fit real development timelines and workflows.

Schedule free consultation Learn more about me