Blog ·

What is the European Accessibility Act? (2026 Guide)

If you sell products or services to consumers in the European Union — an online store, a banking app, an e-book platform, a ticketing site — the European Accessibility Act (EAA) is very likely your problem now, not a future one. The obligations set out in the EAA have applied since 28 June 2025, and enforcement is already under way in several member states. This guide explains what the law actually requires, who it covers, and what "accessible" means in practice.

What the EAA is

The European Accessibility Act is Directive (EU) 2019/882, adopted by the EU in 2019 to harmonise accessibility requirements for a defined list of products and services across the single market. Rather than leaving each of the 27 member states to invent its own accessibility rules, the directive sets a common baseline that every EU country transposes into national law. The goal is straightforward: people with disabilities should be able to use everyday digital products and services without running into unnecessary barriers.

Unlike public-sector accessibility rules that only apply to government websites, the EAA reaches into the private sector. That is what makes it different from earlier accessibility legislation, and why it caught a lot of businesses off guard.

Who must comply

The directive lists specific product and service categories, including:

If your business falls into one of these categories and serves consumers based in the EU, it doesn't matter where your company is legally headquartered — the obligation follows the customer, not the company's address.

There is one meaningful carve-out: microenterprises providing services — fewer than 10 employees and an annual turnover or balance sheet total under €2 million — are exempt from the EAA's service-related obligations. That exemption does not extend to products, and some member states expect microenterprises to document why the exemption applies if challenged. Mid-size and larger companies get no exemption at all.

Key dates

If your business missed the deadline, you're not alone — but "not alone" isn't a legal defence. See our breakdown of what enforcement looks like now that the deadline has passed for what to expect and how to catch up quickly.

What "accessible" means (WCAG 2.1 AA / EN 301 549)

The EAA doesn't invent a new accessibility standard from scratch. Instead, it points to EN 301 549, the European standard for ICT accessibility, as the technical yardstick used to demonstrate conformance. For websites and mobile apps, EN 301 549 in turn incorporates WCAG 2.1 at the AA level — the same Web Content Accessibility Guidelines used worldwide.

In practice, "accessible" means things like:

We go through this in detail in our WCAG 2.1 AA checklist, and explain exactly how the standard fits together in EN 301 549 explained in plain English.

Penalties

The EAA sets the framework, but each EU member state designs and enforces its own penalty regime — there is no single EU-wide fine. National market surveillance authorities can order corrective action, restrict or withdraw non-compliant products and services from the market, and in many countries issue direct fines that scale with company size and severity. We cover representative penalty ranges by country in EAA deadline & penalties: what businesses must know.

Beyond formal fines, non-compliance carries a quieter cost: lost customers who simply can't complete a purchase, higher support overhead from users who get stuck, and reputational risk if a compliance gap becomes public.

How to start

The realistic starting point for almost every business is the same: find out where you actually stand before deciding what to fix.

  1. Run an automated accessibility scan of your site or app to catch the majority of technical issues quickly.
  2. Supplement it with manual checks — keyboard-only navigation, screen reader spot checks, and a review of forms and checkout flows — because automated tools only catch part of the picture.
  3. Prioritise fixes that block task completion (checkout, sign-up, login) over cosmetic issues.
  4. Document what you tested and fixed, since an accessibility statement or conformance record is what you'll need if a regulator or customer asks.

We walk through this process step by step in how to check if your website is EAA compliant. Or, if you'd rather see where your own site stands right now, run a free 30-second scan against WCAG 2.1 AA and EN 301 549 and get a prioritised list of what to fix first.