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

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:

1. Perceivable: Information must be perceivable by the user (not invisible to screen readers, not dependent on colour alone, etc.)
2. Operable: Users must be able to use the website with keyboard, voice, or assistive devices (not just mouse)
3. Understandable: Text must be clear, instructions must be obvious, errors must be explained
4. 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:

1. A disabled user tries to use your website
2. They can't — maybe no alt text on images, poor colour contrast, or non-keyboard-accessible features
3. They contact you to complain
4. You don't fix it (or fix it slowly)
5. They engage a lawyer
6. Costs: solicitor fees, expert witnesses, court fees, damages
7. 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: <img src="team.jpg" alt="image"> ✅ Good: <img src="team.jpg" alt="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 <label> 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:

<input type="email">

✅ Good:

<label for="email">Email address</label>
<input type="email" id="email" required>

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 (<h1>, <button>, <nav>) instead of generic <div> elements.

Why: Screen readers rely on semantic HTML to understand page structure.

What to do: - Use <h1> for main page title, <h2> for sections (not <div class="title">) - Use <button> for buttons (not <div class="button">) - Use <nav> for navigation - Use <main> for main content - Never skip heading levels (h1 → h3, skipping h2)

7. Focus Indicators

Requirement: When tabbing through the site, there must be a visible indicator of which element is focused.

Why: Keyboard users need to know where they are.

What to do: - Don't remove the default focus outline (:focus-visible) - If you customise focus styling, make it clearly visible (not 1px thin outline) - Ensure focus order follows logical page reading order

8. Skip Links

Requirement: Users should be able to skip repetitive content (like navigation menus).

Why: Screen reader users don't want to hear "Home, About, Services, Contact, Blog" on every page.

What to do: - Add a "Skip to main content" link (visible on tab, can be visually hidden) - Place it at the very top of the page

9. Readable Typography

Requirement: Text must be readable (font size, line height, line length).

Standard: - Minimum 14-16px font size for body text - Line height: 1.5 or greater - Line length: max 80 characters

What to do: - Don't use tiny fonts to save space - Add breathing room between lines - Don't stretch text across full width (hard to read)

10. Clear Link Text

Requirement: Links must make sense out of context.

Why: Screen reader users often navigate by jumping between links. "Click here" doesn't tell them where it goes.

What to do: - Use descriptive link text - Avoid: "Click here," "Learn more," "Read more" - Use: "View our web development services," "Download the 2026 pricing guide"

Example: ❌ Bad: <a href="/services">Click here</a> ✅ Good: <a href="/services">View our web development services</a>

How to Test Accessibility: Tools & Methods

Automated Tools (Start Here)

WAVE (Web Accessibility Evaluation Tool) - Browser extension - Free - Identifies common errors - Website: wave.webaim.org

Axe DevTools - Browser extension - Free and paid versions - More thorough than WAVE - Website: deque.com/axe/devtools

Lighthouse (Chrome DevTools) - Built into Chrome browser - Includes accessibility audit - Free

Colour Contrast Analyzer - Checks text/background contrast - Free - Website: webaim.org/articles/contrast

Manual Testing

1. Keyboard-only navigation: Try using your site with only Tab, Shift+Tab, Enter, and arrow keys. Can you do everything?

1. Screen reader testing: Download NVDA (free) or JAWS and test with it. Hear what screen reader users hear.

1. Mobile device testing: Use VoiceOver (iPhone) or TalkBack (Android) to test.

1. Colour blindness simulation: Use Chrome extension "Colour Oracle" to see your site as colour-blind users do.

Professional Audit

For full compliance, hire an accessibility specialist to conduct a formal WCAG 2.1 AA audit. This includes: - Automated testing - Manual testing with assistive technologies - Expert review - Detailed remediation recommendations

Cost: £1,000-3,000 depending on site complexity.

MattDarm offers accessibility audits as part of our web development process.

The Business Case: Beyond Legal Compliance

You might be thinking, "This seems complicated. Is it really necessary?"

Yes. Here's why:

Market Opportunity

15-20% of UK population has some form of disability. This includes: - Colour blindness (8% of men) - Hearing loss (11 million people) - Visual impairment (2 million people) - Mobility disabilities - Cognitive disabilities - Temporary disabilities (broken arm, recovery from surgery)

By making your site accessible, you're not just being compliant — you're reaching a larger market.

SEO Benefits

Accessible sites often rank better because: - Better semantic HTML helps Google understand your content - Alt text helps with image search - Clean, semantic code often loads faster - Keyboard navigation usually means better user experience - WCAG compliance often correlates with good UX

User Experience

Accessibility improvements benefit everyone, not just people with disabilities: - Captions help in noisy environments (coffee shops, offices) - Larger fonts benefit everyone as we age - Clear, simple language benefits non-native speakers - Keyboard navigation is faster than mousing - Good colour contrast is easier on the eyes

Reputation & Brand

Being known as an accessible, inclusive business is good for your brand. It attracts: - Conscious consumers who value inclusivity - Employees who want to work for inclusive companies - Talent (disability advocates are vocal supporters)

Risk Reduction

Every year, more accessibility lawsuits are filed. The risk is real. Why risk it?

Real-World Examples: What Inaccessibility Looks Like

Example 1: E-commerce Site (No Alt Text)

The problem: Product images have no alt text. A blind customer uses a screen reader to shop.

What they experience: Blank product pages. They can see prices but not what the products look like. They can't shop effectively.

Legal issue: Violation of Equality Act (can't access product descriptions).

Business impact: Lost sales. Potential lawsuit.

Fix: Add alt text to every product image.

Example 2: Booking System (Not Keyboard Accessible)

The problem: A date picker requires mouse clicking. A user with tremors uses keyboard navigation.

What they experience: Can't book. Can't interact with the calendar.

Legal issue: Violation of WCAG (no keyboard accessibility).

Business impact: Lost bookings. Customer complaint. Potential legal action.

Fix: Implement keyboard-accessible date picker (or provide alternative text input).

Example 3: Form With Poor Labels

The problem: Form fields aren't properly labelled. A screen reader user fills it in.

What they experience: Don't know what each field is for. Errors aren't explained clearly.

Legal issue: Violation of WCAG (no proper labels or error messages).

Business impact: Incomplete forms. Lost conversions.

Fix: Add proper labels and clear error messages.

Making Your Site Accessible: Where to Start

Step 1: Educate Your Team

Make sure your team (designers, developers, content creators) understands accessibility. It's not extra work — it's built into the design and development process.

Step 2: Audit Your Current Site

Use free tools (WAVE, Axe DevTools) to identify current issues. Document them.

Step 3: Prioritise Fixes

Not all violations are equal. Prioritise: 1. Keyboard accessibility (high impact) 2. Alt text for images (high impact) 3. Colour contrast (high impact) 4. Form labels (high impact) 5. Semantic HTML (medium impact) 6. Other improvements (lower impact)

Step 4: Implement Fixes

For simple fixes (alt text, colour contrast), your team can handle them. For complex issues (keyboard accessibility, semantic HTML restructuring), hire developers.

Step 5: Test & Verify

After fixes, test with real assistive technologies (screen readers, keyboard navigation). Don't just rely on automated tools.

Step 6: Document & Maintain

Create an accessibility statement on your website. Document your commitment and remediation plan.

What to Include in Your Accessibility Statement

Include this on your website (usually footer or accessibility page):

"We are committed to making our website accessible to everyone. Our site meets WCAG 2.1 AA standards. If you encounter accessibility issues, please contact us [contact info]. We welcome feedback and will work to address any barriers."

Key Dates & Deadlines

• June 2025: EAA enforcement begins
• June 2026: Microenterprise website exemption expires
• June 2027: Microenterprise mobile app exemption expires
• Now: Start working on compliance (no time to waste)

Working with MattDarm: Accessibility by Design

At MattDarm, we build every website with accessibility in mind from the start. It's not an afterthought — it's foundational.

Our process includes: - WCAG 2.1 AA compliance as standard - Semantic HTML structure - Performance optimisation (which improves accessibility) - Keyboard navigation testing - Screen reader testing - Regular accessibility audits

Contact us if you need an accessibility audit or want to make your existing site compliant.

Ready to make your website accessible and legally compliant? Contact MattDarm for a free accessibility audit. We'll tell you exactly what needs to change — and how we can help.

You might also find these posts useful:

• How Much Does a Website Cost in the UK? — Website pricing breakdown
• AI Website Builders vs Web Developer — Compare building options
• Why Is My Website So Slow? — Speed and performance