Website Accessibility for UK Small Businesses: The 2026 Compliance Guide

Around 16 million people in the UK live with some form of disability. That's roughly one in four customers, prospects, and visitors to your website.

If your site can't be used by them — and most UK small business sites can't, properly — you're losing customers, exposing yourself to legal risk, and signalling poor quality to everyone else who visits.

The good news: accessibility isn't as scary as it sounds. Most UK small businesses can reach reasonable compliance in 2-4 weeks of focused work. The bad news: very few are doing it, and the legal landscape changed in 2025.

Here's what UK small businesses actually need to know about web accessibility in 2026.

What's actually changed in 2025-2026

Three things shifted the accessibility landscape recently:

The European Accessibility Act (EAA) deadline passed on 28 June 2025. Even though the UK is no longer in the EU, this affects any UK business selling to EU customers. Enforcement is now active.

WCAG 2.2 became the working standard in late 2023, replacing WCAG 2.1. Most accessibility audits now reference 2.2.

Accessibility lawsuits in the UK increased sharply through 2024-2025. While not as litigious as the US, the trend is clear: real businesses are facing real legal claims.

For a UK-only small business with no EU customers, the legal pressure is lower than it sounds. But the Equality Act 2010 still applies and has always required reasonable adjustments for disabled users. That hasn't changed since 2010 — what's changed is awareness and enforcement.

The actual UK legal position (no scaremongering)

There's a lot of conflicting information online about UK accessibility law. Here's the straight version:

The Equality Act 2010 is the foundational UK law. It requires service providers to make "reasonable adjustments" so disabled people aren't disadvantaged. Websites count as services. So websites must be accessible.

The Act doesn't specify technical standards (no "you must meet WCAG 2.2 AA"). It uses the deliberately flexible word "reasonable" — what's reasonable for a one-person sole trader is different from what's reasonable for a 500-person company.

The Public Sector Bodies Accessibility Regulations 2018 require WCAG 2.2 AA compliance for government, schools, councils, NHS organisations, etc. If you run a public sector website, this is mandatory and enforced by the Government Digital Service.

The European Accessibility Act 2025 applies to UK businesses selling products or digital services to EU customers. If you don't sell to the EU, this doesn't apply. Microenterprises (under 10 employees, under €2m turnover) are exempt from some requirements anyway.

For a typical UK small business serving the UK only: the Equality Act is what matters. The standard the courts use to interpret "reasonable" is generally WCAG 2.1 or 2.2 at AA level.

What "WCAG 2.2 AA" actually means

WCAG (Web Content Accessibility Guidelines) are organised around four principles, easily remembered as POUR:

Perceivable — users can perceive your content through sight, sound, or touch Operable — users can interact with your interface (keyboard, mouse, screen reader, voice) Understandable — content and operation are clear Robust — works with current and future assistive technologies

There are three conformance levels:

• Level A — minimum (very basic)
• Level AA — what UK courts and the Equality Act effectively expect (the practical target)
• Level AAA — gold standard (most sites don't need to hit this)

For UK small businesses, WCAG 2.2 AA is the practical target. Hitting it satisfies the Equality Act and protects you legally.

The 2026 WebAIM Million report numbers

Recent global accessibility research found:

• 95.9% of homepages had detected WCAG failures
• Average homepage had 52.8 distinct accessibility errors
• WordPress sites averaged similar error counts

This isn't because accessibility is impossibly hard. It's because almost nobody has prioritised it. The bar to be in the top 5% of accessible sites is lower than you'd think.

The 10 most common accessibility failures (and quick fixes)

We audit a lot of UK small business sites. Here are the failures we see consistently, ranked by frequency:

1. Missing alt text on images

Every meaningful image needs alt text describing it. Decorative images can have empty alt (alt="").

Bad: <img src="our-team.jpg"> Good: <img src="our-team.jpg" alt="The Webgenix team in our Derby office">

Quick fix: Audit every image on your site. Add alt text describing what's in the image and why it matters in context.

2. Poor colour contrast

WCAG 2.2 requires:

• 4.5:1 contrast ratio for normal text against background
• 3:1 for large text (18pt+) and UI components

Common failure: light grey text on white background (looks elegant, fails contrast).

Quick fix: Test your site at WebAIM Contrast Checker. Adjust colours that fail.

3. Form inputs without labels

Every input field needs a <label> connected to it. Many sites use placeholder text instead, which disappears when typing and is invisible to screen readers.

Bad: <input placeholder="Email"> Good:

html

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

Quick fix: Audit every form. Add proper labels to every input.

4. Unclear link text

"Click here" tells screen reader users nothing. Link text should describe the destination.

Bad: "For our pricing guide, click here" Good: "View our complete pricing guide"

Quick fix: Search your site for "click here" and "read more" — rewrite each so the link text describes where it goes.

5. Missing heading structure

Headings (H1, H2, H3) provide structure for screen reader users to navigate. Many sites use heading tags purely for visual styling, creating a broken structure.

Bad practice: Skipping from H1 directly to H4 because H4 looks the right size

Quick fix: Outline your page structure logically. H1 = page title (one per page). H2 = main sections. H3 = subsections within H2s. Don't skip levels.

6. Keyboard inaccessible

Try this right now: open your site, put your mouse aside, and try to navigate using only the Tab key. Can you reach every button? Can you submit forms? Does the focused element have a visible outline?

If you can't navigate without a mouse, neither can users with motor disabilities or screen reader users.

Quick fix: Test with keyboard only. Ensure all interactive elements are reachable. Add visible focus indicators (don't remove them with outline: none unless you replace with something else).

7. Auto-playing media with sound

Videos that auto-play with sound are blocked by most browsers anyway, but still common on UK SME sites. They violate WCAG and annoy users.

Quick fix: Set videos to autoplay muted if you want them to play, or require user interaction to start playback.

8. Missing language attribute

The <html lang="en"> attribute tells screen readers what language to read in. Missing it causes screen readers to mispronounce content.

Quick fix: Check that your <html> tag has lang="en" (or appropriate language code).

9. Inaccessible navigation menus

Dropdown menus that only work on hover, or menus that trap keyboard focus, fail accessibility.

Quick fix: Ensure dropdown menus open on click as well as hover, can be navigated with arrow keys, and can be closed with Escape.

10. Missing skip-to-content link

Sighted users can scroll past navigation easily. Screen reader users have to listen to the entire navigation menu on every page unless there's a "skip to main content" link at the top.

Quick fix: Add a hidden-until-focused link at the top of every page:

html

<a href="#main" class="skip-link">Skip to main content</a>

How to audit your own site (free 30-minute check)

You don't need a paid tool to find most issues. Use these free methods:

Tool 1: WAVE Browser Extension (free)

Install WAVE for Chrome/Firefox. Visit your site, click the extension. It highlights every accessibility error directly on the page.

Tool 2: axe DevTools (free)

axe DevTools is the industry-standard free accessibility checker. Run it on your homepage, contact page, and main service pages.

Tool 3: Lighthouse in Chrome DevTools

Built into Chrome. Right-click any page → Inspect → Lighthouse tab → run an Accessibility audit. Aim for 90+ score.

Tool 4: Manual keyboard test

Disconnect your mouse. Navigate your site using only Tab, Enter, and arrow keys. If you can't complete your contact form or navigate the menu, neither can disabled users.

Tool 5: Screen reader test (advanced)

Built into operating systems:

• macOS: VoiceOver (Cmd+F5)
• Windows: Narrator (Windows+Ctrl+Enter)

Listen to your homepage being read aloud. If it doesn't make sense, your screen reader users are getting that experience daily.

What to fix first if you're starting from scratch

Don't try to fix everything at once. Prioritise:

Week 1: High-impact, low-effort fixes

• Add alt text to all images
• Add proper labels to all forms
• Fix colour contrast issues
• Add lang="en" to your HTML
• Add a "skip to main content" link

Week 2: Structural fixes

• Fix heading hierarchy (H1, H2, H3 in proper order)
• Rewrite vague link text
• Test all forms with keyboard only

Week 3-4: Deeper fixes

• Test with screen reader
• Fix any keyboard navigation issues
• Add ARIA labels where needed for complex UI
• Address any remaining WAVE/axe errors

Ongoing maintenance:

• Test new pages before publishing
• Run quarterly audits
• Monitor for accessibility regressions when plugins update

What about accessibility overlay widgets?

You may have seen those "accessibility widget" popups on some sites — buttons that claim to make your site accessible by adding a widget.

Don't use them. Specifically:

• They don't work. Multiple studies show overlays don't fix underlying accessibility issues. They often make things worse.
• They're often sued. US courts have ruled overlays don't constitute compliance. UK courts are likely to follow.
• They're a marketing scam. "AI-powered accessibility" is largely marketing hype.

Real accessibility comes from fixing the underlying code. There are no shortcuts.

What about accessibility statements?

For private businesses, a published accessibility statement isn't legally required in the UK. But it's strongly recommended because:

• Documents what you've done
• Provides a way for users to report issues
• Shows good faith if disputes arise
• Builds trust with disability advocacy groups

A simple accessibility statement should cover:

• What standard you're targeting (WCAG 2.2 AA)
• Known accessibility limitations
• How users can request alternative formats
• Contact details for accessibility issues
• Date of last review

For public sector sites, a published accessibility statement IS legally required.

How accessibility helps SEO and conversions

The good news: accessibility improvements often improve other things too.

SEO benefits:

• Proper heading structure helps Google understand your content
• Alt text helps image search rankings
• Descriptive link text improves keyword signals
• Better mobile usability (Google ranking factor)
• Faster page loads (often required for accessibility)

Conversion benefits:

• Forms with proper labels convert higher
• Better keyboard navigation helps power users
• Cleaner contrast helps everyone read your content
• Better mobile experience reaches more users

This is why we recommend accessibility as part of any website redesign project — fixing it during a rebuild is much cheaper than retrofitting later.

When to invest in professional accessibility help

DIY accessibility is realistic for:

• Static brochure sites with under 20 pages
• Sites where you can edit HTML directly
• Small e-commerce stores (under 200 products)

Professional help makes sense for:

• Sites with complex interactive elements (calculators, configurators, dashboards)
• Multi-tenant or multi-user platforms
• Sites where you've received a complaint or legal letter
• Public sector sites (where compliance is mandatory)
• Any site where you want a formal accessibility audit document

Professional accessibility audits in the UK typically cost £500-£2,500 depending on site size. Remediation work varies significantly.

What this means for your maintenance plan

Accessibility isn't a one-time fix. It needs ongoing maintenance because:

• WordPress and plugin updates can introduce regressions
• New pages built without accessibility in mind undo previous work
• WCAG standards evolve (3.0 is in draft)
• Browser and assistive technology behaviour changes

For our maintenance plan clients, accessibility monitoring is part of how we look after sites — including checking for regressions after every update.

If you're not on a maintenance plan, the minimum is quarterly accessibility audits, more frequently if you publish new content often.

Common excuses (and why they don't hold up)

"We're too small to need to comply."

The Equality Act applies to every business providing services to the public. Size doesn't exempt you, though it affects what's "reasonable."

"Our customers don't have disabilities."

You don't know that. Many disabilities are invisible. Around 1 in 4 UK adults has some form of disability.

"We've never had a complaint."

Most disabled users don't complain — they just leave and use a competitor. You're losing customers silently.

"It's too expensive."

Most fixes are free or cheap. The expensive part is professional audits and major rebuilds. Basic compliance through DIY work costs zero in money, just time.

"We'll deal with it if we get sued."

UK accessibility lawsuits are increasing. Settling claims costs significantly more than prevention. Plus the reputational damage is real.

A realistic compliance plan

Here's what we recommend for a typical UK small business:

Months 1-2: DIY audit using free tools above. Fix the obvious issues (alt text, contrast, forms, headings).

Month 3: Professional accessibility audit if budget allows. Use this to prioritise remaining work.

Months 4-6: Address audit findings systematically. Document with accessibility statement.

Ongoing: Quarterly self-audit. Annual professional audit. Monitor for regressions.

This gets most UK small businesses to "reasonable" compliance within 6 months at modest cost.

Where to go next

Related guides:

• GDPR compliance for UK websites — the other legal requirement most UK SMEs miss
• Website launch checklist 2026 — accessibility built in from launch
• Signs your website needs a redesign — accessibility is often a redesign trigger
• Core Web Vitals UK guide — performance and accessibility overlap

Or get help directly:

• Free 30-minute consultation — we'll review your site for accessibility and tell you the top 3 fixes
• Custom web development — built accessible from day one
• Maintenance plans from £45/month — includes accessibility monitoring

Accessibility isn't just a legal requirement. It's the difference between a website that serves all your potential customers and one that excludes a quarter of them. For most UK small businesses, the legal threat is real but the moral and commercial case is bigger. Either way, the fix is the same: take accessibility seriously, build it into your processes, and treat it as ongoing rather than a one-off project.