Website Accessibility Laws in 2026: What Every UK Business Needs to Know

In June 2025, the European Accessibility Act (EAA) came into force. If you're a UK business — especially one selling into Europe — this changes your legal obligations.

But it's not just about the European rules. The UK Equality Act 2010 already requires websites to be accessible, and enforcement is increasing. Recent years have seen a sharp rise in accessibility lawsuits against UK businesses, particularly smaller companies who thought they were flying under the radar.

The good news? Making your website accessible is straightforward. The bad news? Ignoring it is now a real legal and financial risk.

This guide covers everything UK business owners need to know about website accessibility laws in 2026 — what the rules are, who needs to comply, what could go wrong, and how to fix it.

The Legal Framework: What's Changed in 2026?

1. The European Accessibility Act (EAA) — June 2025

The EAA is the EU's major accessibility legislation. Even though the UK left the EU, this matters if you do any business in Europe or have EU customers.

What it requires:
Websites must meet WCAG 2.1 AA accessibility standards
Digital products must be accessible (including apps)
Applies to all businesses with ≥10 employees and €2M+ annual turnover

Scope: Any UK business selling into the EU, offering services to EU customers, or operating within EU borders.

Penalties: €10,000-50,000 fines, depending on severity and repeat violations.

Timeline: Full compliance required by June 2025 (now here). There's no flexibility.

2. UK Equality Act 2010

The UK Equality Act has been law since 2010, but enforcement has ramped up significantly in recent years. This applies to every UK business, regardless of size.

What it requires:
Make "reasonable adjustments" to accommodate disabled people
This includes website accessibility
Covers people with: visual impairments, hearing loss, mobility issues, cognitive disabilities, and more

Scope: All UK businesses, charities, and public sector organisations.

Penalties: Civil litigation (you can be sued), damages awards, and legal costs. Recent settlements have ranged from £5,000-50,000+.

Key principle: You don't have to be perfect, but you must make "reasonable" adjustments. What's reasonable? That's determined by guidance documents and case law.

3. WCAG 2.1 AA Standard

Both the EAA and UK Equality Act reference WCAG 2.1 AA as the compliance standard.

WCAG = Web Content Accessibility Guidelines

This is an international standard maintained by the World Wide Web Consortium (W3C). It's not a legal document itself, but it's the technical specification that defines accessibility.

What does WCAG 2.1 AA cover?

The standard has 50 individual criteria across four categories:

Perceivable: Information must be perceivable by the user (not invisible to screen readers, not dependent on colour alone, etc.)
Operable: Users must be able to use the website with keyboard, voice, or assistive devices (not just mouse)
Understandable: Text must be clear, instructions must be obvious, errors must be explained
Robust: The code must work with assistive technologies (screen readers, magnifiers, voice controls, etc.)

The levels:
A: Basic accessibility
AA: Enhanced accessibility (recommended standard, what laws require)
AAA: Optimal accessibility (gold standard, rarely required legally)

For legal compliance, you need AA level.

Who Needs to Comply? Exemptions Explained

Here's the critical question: Does your business need to comply?

All UK Businesses: Yes (Equality Act 2010)

The UK Equality Act applies to every business operating in the UK. There's no exemption based on size.

However, the standard of compliance is "reasonable adjustment." What's reasonable depends on:
The size and resources of your organisation
The cost of making adjustments
Whether the adjustment would fundamentally alter your service

In practice: Large businesses with resources are held to a higher standard than sole traders. But both must make genuine efforts.

UK Businesses Selling in EU: Yes (EAA)

If you have EU customers, you must comply with the European Accessibility Act.

Key question: Do you have customers in EU countries? If yes, the EAA applies.

Timeline: Full compliance required. No more extensions.

Microenterprise Exemption (Limited)

The EAA has a temporary exemption for microenterprises:
Fewer than 10 employees AND
Annual revenue less than €2M

Duration of exemption:
Websites: Exempt until June 2026
Mobile apps: Exempt until June 2027
Physical products: Different timeline

Important: This exemption expires. Even if you qualify now, you need to plan for compliance.

Our recommendation: Even microenterprises should start moving toward compliance now. The exemption window is closing, and legal action risk is increasing.

What Happens If You Don't Comply?

The consequences are real — and increasingly common.

Legal Litigation

In recent years, the UK and EU have seen a rise in accessibility lawsuits. Here are real examples:

Boots UK: Settled an accessibility lawsuit without disclosing terms (rumoured £100,000+ settlement).

Tesco: Multiple complaints about website inaccessibility. Settled various claims.

Sainsbury's: Faced accessibility claims, made improvements to avoid litigation.

Various SMEs: Hundreds of smaller cases settling for £5,000-20,000+.

How lawsuits happen:

A disabled user tries to use your website
They can't — maybe no alt text on images, poor colour contrast, or non-keyboard-accessible features
They contact you to complain
You don't fix it (or fix it slowly)
They engage a lawyer
Costs: solicitor fees, expert witnesses, court fees, damages
Even losing a case costs £10,000+ in legal fees

Damages Awards

Courts award damages based on:
How severely the inaccessibility affected the user
Whether you made good-faith efforts to fix it
How serious the violation was

Recent UK cases have awarded:
£5,000-10,000 for minor barriers
£15,000-25,000 for serious barriers
£50,000+ in egregious cases

Plus legal costs (often £5,000-15,000).

Government Enforcement

The UK government has enforcement powers under the Equality Act. While enforcement isn't aggressive (compared to EU countries), it's increasing.

Expect:
Increased monitoring and complaints to enforcement bodies
Regulators issuing orders for compliance
Reputational damage from public complaints

SEO Penalty

Google's ranking algorithm now heavily favours accessible websites. Sites with poor accessibility often have poor SEO performance because:
Inaccessible sites often have bloated code (bad Core Web Vitals)
Poor semantic HTML hurts SEO
Alt text helps Google understand images

Better accessibility = better SEO.

Practical Compliance Checklist: Make Your Site Accessible

Here's what you actually need to do to be WCAG 2.1 AA compliant:

1. Images & Graphics

Requirement: Every image needs alt text describing it.

Why: Blind users rely on screen readers to understand images. Alt text is read aloud.

What to do:
Add descriptive alt text to every image (not "image" or "photo")
Keep it concise (under 125 characters)
Decorative images can have empty alt text
Avoid repeating text that's already in the image caption

Example: ❌ Bad: `` ✅ Good: ` MattDarm team of five web developers `

2. Colour Contrast

Requirement: Text must have sufficient contrast against its background.

Standard: 4.5:1 contrast ratio (AA level). This applies to:
Body text
Buttons
Form labels
Links

What to do:
Use a contrast checker tool (WebAIM, Contrast Ratio)
Don't rely on colour alone to convey information
Example: Instead of "Click the red button," say "Click the Delete button (red)"

Example: ❌ Bad: Light gray text (#CCCCCC) on white background (#FFFFFF) = 1.2:1 (fails) ✅ Good: Dark gray text (#333333) on white background (#FFFFFF) = 12.6:1 (passes)

3. Keyboard Navigation

Requirement: Everything on your site must work using keyboard alone (no mouse required).

Why: Users with mobility disabilities, tremors, or those using voice control rely on keyboard navigation.

What to do:
Test by using TAB and SHIFT+TAB to navigate
Ensure all interactive elements (links, buttons, form fields) are keyboard accessible
Show a visible focus indicator (border, highlight) when tabbing
Avoid keyboard traps (elements where you can tab in but not out)

Example:
Can you fill a form using only Tab, Enter, and arrow keys? If no, it fails accessibility.

4. Form Labels & Error Messages

Requirement: Every form field must have a label, and errors must be clearly explained.

Why: Screen readers announce labels, helping users understand what each field is for. Clear error messages help everyone recover from mistakes.

What to do:
Use `` elements for form fields
Associate labels with inputs using `for` and `id` attributes
When validation fails, clearly state: "Password must be at least 8 characters"
Mark required fields clearly

Example: ❌ Bad: ```html ```

✅ Good: ```html Email address ```

5. Video Captions & Transcripts

Requirement: All videos need captions (for deaf users) and transcripts (for screen reader users).

Why: Deaf users can't hear audio, and transcripts help users with different learning styles and those in sound-off environments.

What to do:
Add captions to every video (YouTube captions work, but manually review them)
Provide a transcript below the video
Sync captions with dialogue (not just generic)

6. Semantic HTML

Requirement: Use proper HTML elements (`

Website Accessibility Laws in 2026: What Every UK Business Needs to Know