Mandatory Digital Accessibility 2025: Affected Sectors

June 28, 2025: the deadline

Directive (EU) 2019/882, the European Accessibility Act (EAA), requires digital products and services marketed in the EU to meet accessibility requirements starting June 28, 2025. Every member state has transposed it into national law, and the deadlines are firm.

This is not a recommendation. It is a legal obligation with an enforcement regime. And it affects more businesses than most realize.

Who is affected

The EAA applies to consumer-facing digital services. The sectors with the highest exposure:

Hospitality. Online booking systems, check-in applications, self-service kiosks, tourist information platforms. A hotel offering web bookings or a guest app falls within scope. Chains with presence across multiple EU countries must comply in all of them.

Retail and e-commerce. Every online store selling to EU consumers. This covers the full journey: catalog browsing, cart, checkout, and order tracking. Marketplace platforms are included as well.

Fintech and banking. Online banking services, payment applications, self-service terminals, ATMs. PSD2 already required certain standards, but the EAA significantly broadens the scope.

Transport. Ticket booking platforms, real-time information, navigation apps. Airlines, rail operators, and bus companies are directly affected.

Telecommunications. Communication services, routers, modems, and set-top boxes.

What exactly is required

The technical reference standard is EN 301 549, which incorporates the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. In practical terms:

• Perceivable: content accessible through at least two senses. Alt text on images, video captions, sufficient contrast (minimum 4.5:1 ratio for normal text).
• Operable: full keyboard navigation, no focus traps, adequate time to complete tasks.
• Understandable: clear language, predictable behavior, error guidance in forms.
• Robust: compatible with assistive technologies (screen readers, magnifiers, alternative input devices).

For hardware (kiosks, terminals), requirements include accessible touch interfaces, speech output, and wheelchair-compatible design.

The real state of the European market

Across Europe, accessibility compliance remains low. In Spain, the Web Accessibility Observatory found only 15% of corporate websites meet WCAG 2.1 AA. In hospitality, the number is worse: fewer than 10% of Spanish hotel websites pass a basic accessibility audit. The UK, Germany, and France show better numbers but still well below universal compliance.

The most frequent issues we find in audits:

1. Booking forms without accessible labels (85% of cases)
2. Insufficient contrast on CTAs and secondary text (72%)
3. Broken or incomplete keyboard navigation (68%)
4. Images without descriptive alt text (61%)
5. Videos without captions or audio description (89%)

These are not cosmetic issues. They are real barriers for the 87 million people with disabilities in the EU and the millions of travelers with accessibility needs who visit European destinations each year.

Penalties and risk

Enforcement varies by member state but follows a common pattern. In Spain, penalties range from EUR 10,000 for minor infractions to EUR 100,000 for severe ones. Germany and France have similar scales. The UK, post-Brexit, has its own regime under the Equality Act 2010.

Beyond fines, there is reputational risk and litigation risk. In the US, web accessibility lawsuits exceeded 4,600 in 2023. Europe is heading in that direction. And there is direct commercial risk: 71% of users with disabilities leave websites they find inaccessible, according to WebAIM. Those are lost customers.

What to do now

Months remain, not years. The pragmatic roadmap:

Immediate audit. Automated tools like Axe, WAVE, or Lighthouse catch 30-40% of issues. The rest requires manual testing with screen readers (NVDA, VoiceOver) and keyboard-only navigation. A full audit takes 2 to 4 weeks depending on site size.

Prioritize by impact. Not everything needs fixing at once. Critical flows first: booking, checkout, registration, login. Then editorial content. Then secondary features.

Integrate into the pipeline. Accessibility testing tools (axe-core, pa11y, jest-axe) integrate into CI/CD to prevent regressions. If a PR breaks accessibility, it does not merge. This is far more efficient than periodic audits.

Train the team. Design, development, and content teams need accessibility training. Not everyone needs to become an expert, but everyone should know the basic principles and identify obvious issues. An 8-hour workshop changes a team’s dynamic.

Accessibility is not just a legal obligation. It is a design and architecture decision that improves product quality for all users. Accessible sites tend to be faster, better structured, and easier to maintain. Compliance is the push, but the benefit extends far beyond it.