The European Accessibility Act is here, and it probably applies to you

ClearPath Team · 2026-07-18 · 6 min read

The European Accessibility Act, usually shortened to the EAA, sat on the calendar for years. As of 28 June 2025 it is no longer a future deadline. It is the law across all 27 EU member states, and plenty of business owners still have not heard of it.

If you sell to people in Europe, this is worth ten minutes of your attention. Not because the internet is about to end, but because the rules quietly changed, and the businesses that get ahead of it will save themselves a stressful year.

What the EAA actually is

Strip away the legal wording and the EAA is a simple promise: products and services sold in the EU should work for people with disabilities. That covers a lot of ground, from cash machines to e-books, but for most of us the important part is digital. Your website, your online store, and your app all need to be usable by someone who cannot see the screen, cannot hold a mouse, or reads with a screen reader.

The technical yardstick is a European standard called EN 301 549. If your site meets it, Article 15 of the law presumes you are compliant. EN 301 549 leans heavily on the Web Content Accessibility Guidelines, better known as WCAG. Right now the operative version is WCAG 2.1 at level AA. WCAG 2.2 is on its way into the standard, so if you are doing the work anyway, aim for 2.2 and you will already be ready when it lands.

Does it apply to you?

Two questions settle it. First, do you sell to consumers in the EU? If the answer is yes, keep reading, because the law follows the customer, not the company. A shop run out of Tel Aviv, New York, or London is covered the moment it takes an order from someone in Berlin or Madrid.

Second, how small are you? There is a narrow carve-out for microenterprises, meaning fewer than 10 people and under 2 million euro in yearly turnover, and even that only applies to the service side of the rules. Grow past that line and the exemption is gone. Most growing businesses should simply plan as if the EAA applies, because it very likely does.

What your website needs, in plain terms

The full standard runs long, but the everyday requirements come down to a handful of things you can actually picture:

• Every image that carries meaning has a short text description, so a screen reader can announce it.
• Text has enough contrast against its background to be read in real light, on a real phone.
• The whole site works with a keyboard alone, with a visible outline showing where you are.
• Forms have labels that are truly connected to their fields, and error messages explain how to fix the problem.
• Headings and landmarks are structured, so people can jump straight to what they want instead of wading through everything.

None of this is exotic. It is mostly good building practice that got skipped when the site was first put together.

ClearPath's adjustment tools address several of these directly for the visitor, offering keyboard focus outlines, contrast controls and text sizing among its 25 tools, though the underlying markup still needs to be fixed at the code level.

The honest part nobody likes to say out loud

You will run into a lot of tools that promise instant compliance. Stay a little skeptical. Automated checkers and accessibility widgets are genuinely useful, but on their own they catch somewhere around 30 to 40 percent of the barriers a real person would hit. The rest need a human to test the site the way a screen reader user moves through it.

So the honest plan is not "install one thing and forget it". It is "use tools to move fast on the parts they are good at, then test the parts they cannot see". Anyone telling you a single script makes you fully compliant is selling comfort, not accessibility, and regulators have started to notice.

ClearPath fits into this honest picture as one layer among several: it does not touch your code or markup, but it does give visitors real, immediate adjustments while you work on the deeper fixes.

A realistic plan to get moving

You do not need a six month project to make real progress. This order works well:

1. Run an audit to see where you stand. A quick automated scan is a perfectly good starting point, and it hands you a prioritized list.
2. Fix the quick wins first: alt text, contrast, form labels, and heading order. They are cheap, and they matter more than they look.
3. Give visitors real controls. A widget that lets people resize text, boost contrast, or navigate by keyboard helps someone today, while the deeper fixes happen in the background.
4. Publish an accessibility statement. It shows the steps you are taking, and it is expected under the standard.
5. Keep testing. Accessibility is not a certificate you frame on the wall. It is something you maintain as the site changes.

The takeaway

The EAA is not a reason to panic. It is a reason to finally do the thing that was always worth doing. An accessible site reaches more customers, tends to rank better, and reads as a business that pays attention to detail. Start with an audit, fix the obvious things, give people controls while you work, and keep at it. Future you will be glad you started this week, instead of after the first complaint letter arrives.