In just a few months, the European Accessibility Act (EAA) becomes enforceable across the EU. And if your business offers digital services—whether you're selling products online, building software, or running a media platform—this affects you.
Until now, accessibility requirements in the EU have mostly applied to public sector websites. That’s about to change. Starting June 28, private sector websites, apps, platforms, and digital tools will be held to a higher standard, with real consequences for non-compliance.
So, what’s changing, and what should you do about it?
More businesses, more products, more responsibility
The biggest shift in 2025 is the scope. The EAA now applies to a wide range of
private sector companies offering digital services to EU consumers. This includes:
• eCommerce sites and marketplaces
• Banking and financial apps
• Video streaming platforms
• Booking and travel services
• eBook platforms and e-readers
• Mobile apps, desktop software, and even self-service kiosks
If you’re selling or providing a digital service in Europe, chances are you’re on the list.
And no, you don’t have to be headquartered in the EU for this to apply. If you serve EU users, you’re expected to meet the standard.
WCAG is no longer “nice to have”
The EAA doesn't create entirely new technical rules from scratch. Instead, it leans on existing global standards, most notably the Web Content Accessibility Guidelines (WCAG).
WCAG 2.1 Level AA is the benchmark here, and if you’re not familiar with it, it’s essentially the international rulebook for making websites and apps usable by people with disabilities. That includes users who rely on screen readers, keyboard navigation, voice control, or specific color and contrast requirements.
Many businesses have treated WCAG compliance as a recommendation rather than a requirement. That changes in 2025. The expectation is clear: digital products must be accessible, and WCAG is how compliance will be measured.
What “accessible” actually means in practice
This isn’t just about checking a few boxes or installing a plug-in. Accessibility affects how your website is structured, how users navigate it, and how information is communicated.
For example:
• Can someone complete a checkout or booking flow using only a keyboard?
• Are images and UI elements properly labeled for screen readers?
• Is there enough color contrast for text to be readable by low-vision users?
• Does your mobile app support users with cognitive or motor impairments?
These are the kinds of issues regulators (and users) will be looking for. They’re also the areas where many websites still fall short.
What happens if you don’t comply?
Non-compliance under the EAA isn’t just a theoretical risk. Starting in June, EU member states will begin enforcing the rules, with penalties, fines, and potential legal action for businesses that don’t meet the standard.
Even beyond the legal consequences, the reputational cost can be significant. Accessibility lawsuits are increasingly public, and digital inclusivity is becoming a baseline expectation, especially in markets like banking, travel, and ecommerce.
How to get ahead of the deadline
If you’re already thinking about this, you’re ahead of the curve. But accessibility takes time, especially if you haven’t built it into your process before. Here’s where to
start:
• Audit your current site or app for WCAG 2.1 Level AA compliance
• Fix critical issues (especially anything blocking navigation, form completion, or readability)
• Set up ongoing testing—accessibility isn’t a one-time project
• Train your team so accessibility is part of your workflow, not an afterthought
And if you need help: that’s where we come in. Askem is built to simplify compliance: running scans, surfacing issues, and giving your team clear, actionable fixes so you’re not scrambling in June.
