Does the European Accessibility Act Apply to UK Businesses Selling to the EU?

This is the question that catches sensible UK founders off guard. You are not an EU company. You do not have an office in Dublin or Berlin. So surely a European directive is somebody else's problem. The honest answer is that it usually is not — and the reasoning is the same one that brought GDPR to your inbox a few years ago.

The European Accessibility Act (EAA) follows the market, not the map. Its scope is set by who buys from you. If consumers in the EU can reach your checkout, your app, your e-book or your booking flow, the obligation reaches you too. Below, we set out exactly when the EAA applies to UK businesses, what the standard actually asks for, and how to judge your real exposure before a regulator does it for you.

The short answer on whether the EAA applies to UK businesses

The deciding factor is customer location. As accessibility specialists Askem put it plainly, "Brexit does not change this — if your customers are in the EU, the EAA applies to you." The logic mirrors GDPR: where your company is registered is irrelevant; where the consumer sits is what counts.

So the question "does the EAA apply to UK sellers" resolves into a simpler one. Do you make a covered product or service available to consumers in any EU member state? If the answer is yes — and for most online businesses with EU traffic it is — then you are in scope. The 28 June 2025 deadline has already passed, which means this is no longer a future planning item. The obligation is live now.

Which products and services are actually covered

The EAA does not cover everything. It targets a defined list of products and services that European institutions judged central to participating in modern life. For most UK companies, the relevant categories are:

• E-commerce — any website or app where an EU consumer can buy a product or service. This is the one that sweeps in the broadest set of UK sellers.
• Banking and financial services aimed at consumers.
• Electronic communications and telecommunications services.
• Transport services — booking, ticketing and real-time travel information.
• E-books and dedicated reading software.
• Consumer computing hardware and operating systems, plus self-service terminals such as payment kiosks.

If you run a direct-to-consumer shop, a SaaS product with EU sign-ups, a fintech app, or you sell digital books into Europe, you should assume you are in scope until you can show otherwise. The phrase to internalise here is EAA selling to EU customers: the moment a French or German consumer can transact, the rules engage.

What EAA compliance means in practice: WCAG 2.1 AA

For digital services, the Act does not invent a brand-new rulebook. It points to the harmonised European standard EN 301 549, which in turn adopts the Web Content Accessibility Guidelines — specifically WCAG 2.1 Level AA. So the working target for an EN 301 549 UK seller is a familiar one to anyone who has touched accessibility before.

In practical terms, WCAG 2.1 AA asks that your site and product be:

• Perceivable — text alternatives for images, captions for video, sufficient colour contrast, content that reflows on a phone without horizontal scrolling.
• Operable — every function reachable by keyboard alone, no traps, visible focus, enough time to complete tasks.
• Understandable — clear labels, predictable navigation, error messages that say what went wrong and how to fix it.
• Robust — clean, semantic markup that screen readers and assistive technology can parse reliably.

There is a quiet bonus for UK companies here. The Equality Act 2010 already expects services not to discriminate against disabled users, and WCAG 2.1 AA is the de facto benchmark courts and regulators reach for. So building to EAA WCAG 2.1 AA in the UK is not double work — it largely satisfies your domestic obligation at the same time. As Askem note, "Fix it once and you're covered for both." This is the heart of EAA UK ecommerce compliance: one standard, two jurisdictions.

The micro-enterprise exemption — and its trap

There is a carve-out, but it is narrower than the headlines suggest. The EAA micro-enterprise exemption applies to businesses with fewer than 10 employees and an annual turnover under €2 million. Cross either threshold and the exemption falls away entirely.

Two details trip people up. First, the exemption is generous for services — a qualifying micro-enterprise providing a service is fully relieved of the requirements. For products, it is far more limited: micro-enterprises get reduced documentation obligations, not a clean pass on accessibility itself. Second, "fewer than 10 employees" is a low ceiling. A growing UK e-commerce brand with a dozen staff and modest revenue is already outside it.

So treat the exemption as a precise legal test, not a comfortable assumption. If you are close to either line, the safer reading is that you will cross it soon and should build to the standard anyway. We would rather tell you that plainly now than have you discover it during a complaint.

Is anyone actually enforcing this?

This is the fair, sceptical question — and the answer, as of 2026, is yes. The early pattern across Europe is real, and it is not theoretical fines on a distant horizon. Deque's tracking of early enforcement shows movement in several member states:

• The Netherlands — the regulator ACM set an October 2025 reporting deadline for non-conformance, and companies that failed to report face prioritised audits from spring 2026.
• Sweden — the Post and Telecom Agency began inspecting e-commerce services, with reviews running through 2026.
• France — disability organisations filed interim court proceedings against four major grocers in November 2025 over missed deadlines.
• Ireland — formal complaints are being processed, including a case against a telecom provider.

The early posture from regulators is corrective rather than punitive — ACM stated that "fines and penalties are absolutely not the goal," preferring audits and structured oversight first. But the penalties behind that posture are not trivial, and they vary by country because the EAA leaves each member state to set its own rules under Article 30. Germany's BFSG provides for fines up to €100,000 per violation. Ireland is more striking still: up to €60,000 in fines and, in serious cases, up to 18 months' imprisonment for service providers who fail to comply after notice. That makes Ireland the one confirmed jurisdiction where non-compliance can carry criminal liability.

The realistic risk for a UK seller, then, is rarely a surprise fine on day one. It is a complaint, an audit request, or interim court proceedings in a single member state — any of which can pull a small team into a legal process it is poorly equipped to handle, while competitors who built accessibly carry on selling.

How to work out your own exposure

You do not need a law firm to make a first, honest assessment. Walk through four questions in order:

• Do EU consumers reach a covered product or service through us? Check your analytics for EU traffic and conversions, and confirm your offering sits in one of the covered categories.
• Are we genuinely a micro-enterprise under both tests? Fewer than 10 staff and under €2 million turnover — and even then, only services are fully exempt.
• Where do we stand against WCAG 2.1 AA today? An automated scan finds perhaps a third of issues; a manual audit with keyboard and screen-reader testing finds the rest. You need both for an honest picture.
• Can we keep it compliant? Accessibility regresses with every new feature and content change, so the question is not a one-off audit but ongoing monitoring.

If you reach the end of that list and find you sell only to UK customers, in a non-covered category, as a true micro-enterprise — then the EAA may genuinely not touch you, and we would say so. There is no value in manufacturing urgency. But if EU consumers can buy from you, the threshold for "this is our problem" is lower than most founders assume, and the cost of acting before a regulator decides is far smaller than the cost of acting after.