All articles
WCAGCheck Editorial

Equality Act 2010 and Website Accessibility: What UK Developers Actually Need to Know

The Equality Act 2010 requires accessible websites. Here's what UK developers need to know about legal obligations and practical WCAG compliance.

Equality Act 2010 and Website Accessibility: What UK Developers Actually Need to Know

A recent article from Stephensons Solicitors has brought renewed attention to digital accessibility obligations under the Equality Act 2010. For UK developers and agencies, this is a good reminder that accessibility isn't optional—it's a legal requirement that applies to virtually every website serving UK users.

Let's break down what this actually means for your work.

The Legal Bit: What the Equality Act 2010 Requires

The Equality Act 2010 makes it unlawful to discriminate against people with disabilities. This applies to "service providers"—and yes, that includes websites.

If you're building a website for a business that sells products, offers services, or provides information to the public, that site needs to be accessible to people with disabilities. The Act requires service providers to make "reasonable adjustments" to ensure disabled people aren't placed at a substantial disadvantage.

For websites, "reasonable adjustments" means following established accessibility standards. In practice, that means WCAG (Web Content Accessibility Guidelines).

Which WCAG Level? And Which Version?

The Equality Act doesn't specify WCAG 2.1 AA by name, but this has become the accepted standard in the UK. Here's why:

  • Public sector websites are explicitly required to meet WCAG 2.1 AA under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018
  • Private sector websites don't have a specified standard, but courts and regulators look to WCAG 2.1 AA as the benchmark for what's "reasonable"

WCAG 2.2 was published in October 2023 and adds nine new success criteria. While not yet legally mandated in the UK, it's worth knowing about—particularly if you're building new sites. The additional criteria address issues like focus appearance (2.4.11), dragging movements (2.5.7), and accessible authentication (3.3.8).

What "Reasonable" Actually Looks Like

The "reasonable adjustments" language gives some flexibility, but don't use it as an excuse to do the minimum. Courts consider:

  • The size and resources of the organisation — A multinational retailer will be held to a higher standard than a local sole trader
  • The cost of making adjustments — But most WCAG fixes are cheap or free if you build accessibility in from the start
  • The practicality of the adjustment — Genuine technical limitations may be considered, but "we didn't know" or "it's too hard" won't fly

For most commercial websites, meeting WCAG 2.1 AA is absolutely reasonable. The cost of fixing accessibility issues is almost always lower than the cost of defending a discrimination claim.

Common Issues That Create Legal Risk

Here are the problems we see most often that could expose your clients to legal action:

Missing alt text on images (WCAG 1.1.1) Screen reader users can't understand images without descriptions. Every informative image needs alt text. Decorative images need empty alt attributes (alt="").

Poor colour contrast (WCAG 1.4.3) Text needs a contrast ratio of at least 4.5:1 against its background (3:1 for large text). That light grey text on white background? It's not just hard to read—it's a compliance failure.

Keyboard inaccessibility (WCAG 2.1.1) Every interactive element must work with a keyboard alone. If users can't tab to your navigation, activate your buttons, or submit your forms without a mouse, you've got a problem.

Missing form labels (WCAG 1.3.1, 4.1.2) Form inputs need properly associated labels. Placeholder text doesn't count—it disappears when users start typing.

No skip links (WCAG 2.4.1) Keyboard users shouldn't have to tab through your entire navigation on every page. Provide a "skip to main content" link.

Who's Actually at Risk?

Every organisation that provides goods, services, or information online. That includes:

  • E-commerce sites
  • Booking systems
  • Information websites
  • SaaS platforms
  • Mobile apps

Public sector bodies face additional requirements and must publish accessibility statements. But private companies aren't off the hook—they just don't have the same documentation requirements.

The Business Case Beyond Compliance

Legal compliance matters, but it's not the only reason to care about accessibility:

  • 14.6 million people in the UK have a disability — That's a significant portion of your potential users
  • Accessible sites perform better — Clean HTML, proper headings, and good structure improve SEO
  • Accessibility benefits everyone — Captions help users in noisy environments; good contrast helps users in bright sunlight; keyboard navigation helps power users

What to Do Now

  1. Audit your current sites — You can't fix what you don't know about
  2. Prioritise high-impact fixes — Start with navigation, forms, and core user journeys
  3. Build accessibility into your process — It's cheaper to build it right than to fix it later
  4. Test with real users — Automated tools catch about 30% of issues; manual testing and user testing catch the rest

The Equality Act has been in force since 2010. The accessibility regulations for public sector sites came in 2018. There's no grace period left—the expectation is that websites are accessible now.

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