In short: Since 28 June 2025, the European Accessibility Act for websites has been binding law for businesses offering digital consumer services such as online shops, banking, or booking platforms. The technical standard is EN 301 549, which for websites points to WCAG 2.1 Level AA. Microenterprises with fewer than 10 employees and under €2 million in annual turnover are exempt from most obligations, and for everyone else, the grandfathering period for older services ends in 2030 at the latest. We at Okapi Digital in Frankfurt break down who's actually covered and how to get a website compliant step by step.
Web accessibility used to be a topic mostly for public-sector sites. With the European Accessibility Act (Directive (EU) 2019/882) and its national implementations, including the BFSG in Germany, it now reaches private businesses too. Since 2025, companies selling or booking online across the EU face a concrete question: does the European Accessibility Act for websites apply to us, and if so, what actually has to change? This article walks through the deadlines, exemptions, and technical requirements without the scare tactics.
What is the European Accessibility Act, and why does it cover websites?
The EAA is an EU directive requiring that digital products and services be usable by people with disabilities in the same way as everyone else: buying something online, paying a bill, booking an appointment. For websites and apps, the technical standard EN 301 549 points to the Web Content Accessibility Guidelines (WCAG), version 2.1, Level AA. That's the same benchmark public-sector sites in the EU have followed for years under earlier accessibility rules, now extended to private businesses offering the services listed in the directive.
Which businesses does the EAA website requirement actually cover?
The Act names specific product and service categories. For websites, the ones that matter most are:
| Area | Example |
|---|---|
| E-commerce | Online shops, including offers sold through marketplaces |
| Consumer banking services | Online banking, account opening |
| Telecommunications services | Mobile and internet contracts, customer portals |
| Passenger transport | Ticket booking for bus, rail, air, or ferry |
| E-books and related software | Digital books, reading software |
A plain company website with no checkout, payment function, or booking service doesn't automatically fall under this list. The moment visitors can buy, book, or sign up for something on the site, it's worth checking the details rather than assuming either way.
Does the small business exemption apply to your website?
Not unconditionally. The EAA exempts microenterprises from most service-related obligations when both conditions are met:
- fewer than 10 employees
- annual turnover or balance sheet total of no more than €2 million
Businesses below that threshold don't have to meet the EAA's technical requirements for services. The exemption applies per company, not per website, and only to services, not to every product category in the Act. For growing businesses, it's still worth looking at this early: a company just under the threshold today may cross it next year, and building accessibility in from the start is far easier than retrofitting it later.
What's the actual deadline for an existing website?
Two dates matter here:
| Date | What applies |
|---|---|
| 28 June 2025 | New products and services must fully meet the requirements |
| 28 June 2030 | Transition period ends for services already in use before 28 June 2025 |
In practice: a new website or online shop launching today has to comply from day one. A site that was already live before June 2025 technically has a grace period, but that grandfathering runs out by 2030 regardless. Anyone already planning a website redesign can fold accessibility into that project instead of treating it as a separate task later.
What does WCAG 2.1 Level AA actually require?
The requirements are concrete and usually straightforward once accounted for from the start:
- Sufficient color contrast between text and background, including on buttons and form fields
- Full keyboard operability, with no mouse required
- Meaningful alt text for images that describes content, not file names
- Clearly labeled form fields with understandable error messages
- Captions or transcripts for videos with audio
- A clean heading structure and semantic HTML so screen readers can read the page correctly
None of these is particularly heavy on its own. Together, they decide whether a website is actually usable for people with visual, motor, or hearing impairments, rather than compliant only on paper.
What happens if a website doesn't meet the requirements?
National market surveillance authorities are responsible for enforcement. They can order corrections, set deadlines, and impose fines for continued or serious non-compliance. On top of that, a breach of accessibility rules frequently counts as a competition law violation as well, which opens the door to formal warnings from competitors or consumer protection bodies, independent of any regulatory proceeding. That's one more reason to deal with this proactively instead of waiting to see if it gets noticed.
What disclosure obligations do businesses have?
Beyond the technical work, the EAA also requires businesses to explain how their service meets the accessibility requirements. In practice, that means a clearly findable statement, usually published on the website itself, plus a simple way for users to report barriers or ask questions. If you've seen an accessibility statement on a public-sector site before, this is the same idea, just extended to private businesses instead of government bodies.
Why an accessible website pays off beyond compliance
Accessibility pays off commercially too. Many of the technical requirements, color contrast, semantic HTML, meaningful alt text, overlap heavily with established SEO fundamentals: search engines read a page in ways that resemble how a screen reader does. A site built consistently to WCAG 2.1 AA often loads faster, is easier to use on keyboard and mobile, and reaches visitors who would otherwise have bounced off a poorly built page. Treating the European Accessibility Act for websites as a reason to clean up a site technically pays back in more than just legal certainty.
How do you actually make a website accessible?
Getting a website compliant follows a fairly predictable path:
- A review checks the current site against WCAG 2.1 AA criteria and lists concrete issues by page.
- Contrast, keyboard navigation, and alt text are usually the quickest fixes; forms and complex interactions tend to take more work.
- Depending on the starting point, implementation ranges from targeted fixes on the existing CMS to a full website redesign built accessible from the ground up.
- Accessibility isn't a one-time checkbox. It belongs in ongoing website maintenance as new content and features get added.
If your site is overdue for an update anyway, our website redesign guide covers how to plan accessibility into that project from the start instead of bolting it on later. For sites already live, our website maintenance cost breakdown shows how accessibility fits into ongoing care. And if you're still deciding who should handle a project like this, our guide on how to choose a web design agency in Frankfurt covers what to look for.
The bottom line
The European Accessibility Act for websites has been enforceable law since 28 June 2025 for businesses running digital consumer services. If your site handles e-commerce, bookings, or contracts, check whether the microenterprise exemption applies, and if it doesn't, start working toward WCAG 2.1 AA before a regulator or a warning letter forces the timeline. It's technically manageable, plannable, and pairs well with a redesign you were probably going to do anyway.
Not sure whether or how your website is affected? Book a free discovery call. We'll take an honest look at your site and tell you exactly where you stand on accessibility.



