All articles
WCAGCheck Editorial

The European Accessibility Act: What UK Businesses Need to Know in 2026

The European Accessibility Act affects UK businesses selling to EU customers. Here's what it means for your website and digital services.

The European Accessibility Act: What UK Businesses Need to Know in 2026

The European Accessibility Act (EAA) came into force across EU member states in June 2025. If you're a UK-based developer or agency, you might assume this doesn't affect you. After all, we're not in the EU anymore.

That assumption could cost your clients money and market access.

What the EAA Actually Requires

The EAA mandates accessibility standards for products and services sold within the EU. For digital services, this means:

  • E-commerce websites
  • Banking and financial services
  • Transport services (booking, ticketing, check-in)
  • E-books and e-readers
  • Streaming services
  • Telecommunication services

The technical standard? WCAG 2.1 Level AA, with some additional requirements around hardware and physical products.

If your UK client sells any of these services to EU customers, their website needs to meet these standards. Not "should" – needs to.

Why This Matters for UK Agencies

Let's be specific about who this affects:

E-commerce sites shipping to the EU: If a UK retailer sells to customers in Germany, France, or any other EU country, their checkout process, product information, and customer service channels need to be accessible.

SaaS companies with EU customers: That project management tool or accounting software you're building? If it has EU subscribers, the EAA applies.

Travel and hospitality: UK hotels, airlines, and tour operators selling to EU tourists need accessible booking systems.

Financial services: UK fintech companies serving EU clients face compliance requirements.

The enforcement mechanism varies by EU country, but penalties can include fines, market restrictions, and being barred from selling in specific member states.

The Technical Requirements

WCAG 2.1 AA compliance means meeting 50 success criteria. Here are the ones that catch most sites out:

Colour contrast (1.4.3): Text needs a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) needs 3:1. That light grey text on white? It probably fails.

Keyboard navigation (2.1.1): Every function available by mouse must work with keyboard alone. This includes custom dropdowns, modal dialogs, and interactive widgets.

Focus indicators (2.4.7): When users tab through your page, they need to see where they are. The default browser outline often gets removed for aesthetic reasons – that's a fail.

Form labels (1.3.1, 3.3.2): Every input needs a programmatically associated label. Placeholder text doesn't count.

Error identification (3.3.1): When form validation fails, users need to know what went wrong and where. "There was an error" isn't good enough.

Reflow (1.4.10): Content must be readable at 320px width without horizontal scrolling. This catches fixed-width layouts and tables.

What About UK-Only Sites?

Even if your client only serves UK customers, accessibility requirements still apply:

Public sector: The Public Sector Bodies Accessibility Regulations 2018 require WCAG 2.1 AA compliance for government and public body websites.

Equality Act 2010: Service providers must make "reasonable adjustments" for disabled people. Inaccessible websites increasingly fail this test in legal challenges.

Commercial sense: 22% of the UK population has some form of disability. An inaccessible site excludes potential customers.

Practical Steps for Compliance

1. Audit what you have

You can't fix what you haven't measured. Run automated scans to catch the obvious issues – colour contrast, missing alt text, form label problems. Automated tools typically find 30-40% of issues.

2. Manual testing

Automated scans miss context-dependent problems. Can you complete the checkout using only a keyboard? Does the tab order make sense? Do screen reader announcements make sense?

3. Prioritise by impact

Fix blocking issues first. A checkout that can't be completed with a keyboard is worse than a decorative image missing alt text.

4. Build accessible from the start

Retrofitting accessibility costs 10x more than building it in from day one. For new projects, WCAG compliance should be a non-negotiable requirement, not a nice-to-have.

5. Document your compliance

The EAA requires accessibility statements. Even for UK-only sites, documenting your accessibility efforts demonstrates due diligence under the Equality Act.

The Bottom Line

Brexit didn't create a force field around UK websites. If you're building sites for clients who sell to EU customers, the European Accessibility Act applies to you. And even for domestic-only sites, UK law and basic commercial logic point the same direction: accessible websites aren't optional.

The good news? WCAG 2.1 AA is a well-documented standard with clear success criteria. You don't have to guess what compliance looks like.

WCAGCheck scans your website for WCAG compliance issues and tells you exactly what to fix. Try it free at wcagcheck.co.uk