UK Equality Act & Website Accessibility: The Complete 2026 Guide

Last updated: November 11, 2026. This article covers UK law at a factual level only and is general information, not legal advice.

Yes — the Equality Act 2010 requires most UK businesses serving the public online to run an accessible website. The Act names no technical standard, but its anticipatory reasonable-adjustments duty covers disabled customers as a group, not just those who complain, which is what UK equality act website accessibility compliance turns on in practice. This guide covers the law, how UK enforcement differs from the US, and the standard courts and the EHRC treat as evidence of compliance.

Key numbers: The Equality Act 2010's Schedule 2 duty to make reasonable adjustments is anticipatory — service providers must act in advance for disabled people generally, not wait for an individual request (legislation.gov.uk). GOV.UK's guidance for public sector bodies was updated in September 2024 to require WCAG 2.2 AA, up from WCAG 2.1 AA. WCAG 2.2 defines 55 success criteria at Levels A and AA — the practical yardstick UK regulators and the courts default to (W3C). In 2026, 95.9% of the world's top one million home pages carried a detectable WCAG failure, averaging 56.1 errors per page (WebAIM Million, 2026). As of 2026, TestParty has remediated 35 million+ accessibility issues across 100+ brands, including UK-facing Shopify and Shopify Plus stores.

Does the Equality Act Require an Accessible Website?

In effect, yes: the Equality Act 2010 doesn't mention websites by name, but its services provisions and its anticipatory reasonable-adjustments duty apply to any UK business offering a service to the public, and a website is squarely a service.

Part 3 of the Act (s.29) prohibits a service provider from discriminating against a disabled person in the way it provides a service, and Schedule 2 sets out the reasonable-adjustments duty that makes s.29 bite in practice. Crucially, that duty is anticipatory: a service provider must think ahead about the barriers disabled customers as a group are likely to face and take reasonable steps to remove them — a provision, criterion or practice that puts a disabled person at a substantial disadvantage, a physical or digital feature, and the absence of an auxiliary aid are all covered — rather than waiting for one customer to ask for a fix (legislation.gov.uk). The Act names no technical standard, so "reasonable" is judged case by case. The EHRC's own code of practice for services and public functions treats bookings and services delivered through "websites or apps" as squarely within scope, using the example of a service refusing bookings from disabled customers online exactly as it would at a physical counter. In practice, WCAG 2.2 AA is what that guidance, public-sector regulation, and settled industry practice treat as the evidence of what "reasonable" looks like, so building to it is the closest thing to a safe harbor the Act itself doesn't spell out.

How Is UK Enforcement Different From the US?

UK enforcement runs through individual County Court claims and public-sector monitoring, not the demand-letter, serial-filer economics that drive US ADA litigation — smaller in volume, but the underlying legal duty is just as real.

A disabled person alleging discrimination under the Act's services provisions brings a claim in the County Court, generally within six months minus one day of the alleged act, after first raising it with the business directly. There is no UK equivalent of the plaintiff-firm volume that produced 3,117 federal website lawsuits in the US in 2025 alone (Seyfarth Shaw, 2025) — claims are brought individually, often with charity or Equality Advisory Support Service backing, and a fully litigated UK website judgment remains rare. The most-cited example is still RNIB's 2011–2012 legal action against bmibaby over a mouse-only flight-booking flow blind customers couldn't use; it settled after the airline rebuilt the booking journey, without a full trial establishing binding case law. That rarity cuts both ways: don't inflate the odds of a lawsuit, but don't read low case volume as low duty — the reasonable-adjustments obligation exists whether or not anyone has sued over it yet, and reputational exposure through press and disability charities is its own real cost.

What Standard Should a UK Business Build To?

Build to WCAG 2.2 AA: it's what GOV.UK guidance names outright for the public sector, what the EHRC treats as evidence of "reasonable" under the Act, and what EN 301 549 converges on for anything also sold into the EU.

A private ecommerce site isn't legally bound by PSBAR, but the regulation still signals the bar regulators and courts expect a "reasonable" business to clear. Our WCAG 2.2 AA breakdown walks through all 55 criteria in plain language if you want the checklist itself rather than the legal framing.

Are UK Ecommerce Sites Exposed to the EAA Too?

Yes, once a UK store targets EU consumers: the European Accessibility Act attaches to the market a service reaches, not where the business is incorporated, so Brexit didn't remove this exposure for cross-border sellers.

EU shipping zones, euro pricing, localized EU storefronts, and EU-directed marketing are the evidence regulators use to decide a UK-based store is "offering a service" to EU consumers under Directive (EU) 2019/882. That brings EN 301 549's web requirements, an Annex V accessibility statement, and enforcement through whichever member-state regulator or court has jurisdiction where the customer sits — a materially different exposure than a County Court claim at home. Our EAA-for-ecommerce scoping guide walks through exactly which stores must comply, and our broader EAA compliance guide covers the full requirement set for any brand selling on both sides of the Channel.

What Does a Defensible UK Compliance Program Look Like?

A defensible program is audit, fix in source code, publish a dated accessibility statement, then keep monitoring — documentation of that sequence is the practical evidence a "reasonable" adjustment was in fact made.

Start with an automated and manual audit against WCAG 2.2 AA across every template a customer touches, not just the homepage. In TestParty's audits of UK-facing Shopify and Shopify Plus stores, the most common Schedule 2 barrier isn't exotic: checkout buttons under a 3:1 contrast ratio and delivery-address fields that break keyboard focus order, the kind of issue our website accessibility remediation guide treats as fix-in-code-first rather than paper over with a script. Then publish a dated accessibility statement describing current conformance and known gaps — our accessibility statement generator produces one — because a dated record of ongoing remediation is exactly the evidence a court or the EHRC looks for when judging whether "reasonable" steps were taken. Be honest about overlays here: a toolbar that adjusts the rendered page without touching the underlying HTML, CSS, or JavaScript doesn't discharge the Schedule 2 duty, a point the widely endorsed Overlay Fact Sheet makes about this entire product category, and one our Recite Me alternatives comparison works through in UK-specific detail. Finally, monitor — a site drifts back toward violations with every theme or app update, so treat the first fix as a baseline, not an ending.

What Should UK Teams Do This Quarter?

Sequence the work rather than starting everywhere at once: confirm exposure, audit against WCAG 2.2 AA, remediate checkout first, publish the statement, then put monitoring in place before the next theme release ships new gaps.

First, confirm exposure on both fronts — Equality Act duties at home, and whether EU-directed sales pull in the EAA too. Second, run a full audit rather than a homepage scan; automated tooling catches roughly 60–70% of issues, and the rest needs manual keyboard and screen-reader testing. Third, remediate checkout and account creation before anything cosmetic, since a shopper who can browse but can't complete a purchase is the clearest case of substantial disadvantage. Fourth, publish or refresh the accessibility statement with a real date on it. Fifth, put recurring scans on the calendar so this quarter's fix is still true next quarter.

Frequently Asked Questions

Does the Equality Act name WCAG as the legal standard? No. The Act imposes a duty to make reasonable adjustments without naming any technical standard. WCAG 2.2 AA is what the EHRC's guidance, UK public-sector regulation, and settled industry practice treat as evidence that a business met that duty — a de facto standard, not a statutory one.

What is the anticipatory duty, and why does it matter for a website? It means a service provider must plan for likely barriers facing disabled people generally, in advance, rather than waiting for a specific customer to ask for help. For a website, that means the checkout, search, and product pages should already work with a keyboard and screen reader before anyone complains, not after.

How long does someone have to bring a website accessibility claim in the UK? Generally six months minus one day from the date of the alleged discriminatory act, and the claim is brought in the County Court rather than an employment tribunal, which only hears workplace discrimination matters.

Does PSBAR apply to a private ecommerce store? No. The Public Sector Bodies Accessibility Regulations 2018 bind public sector websites and apps specifically. A private retailer isn't legally bound by them, but the regulation's WCAG 2.2 AA standard is the same benchmark regulators and courts reference when assessing what's "reasonable" under the Equality Act.

Does installing an accessibility overlay satisfy the reasonable-adjustments duty? Not on its own. An overlay adjusts what a visitor sees in the browser without changing the underlying HTML, CSS, or JavaScript an assistive technology reads, so the barrier a screen reader or keyboard user hits remains in the source code either way.

Do UK sellers shipping into the EU need to worry about the EAA as well as the Equality Act? Yes, if EU consumers are genuinely being targeted — EU shipping, euro pricing, or EU-localized storefronts are the evidence used to decide that. The Equality Act covers UK-facing sales; the EAA is assessed separately against the EU market a store reaches.

Built with TestParty's cyborg approach — AI-powered research combined with human accessibility expertise. This article contains TestParty's editorial analysis based on publicly available information. We're an accessibility vendor with opinions informed by working with 100+ brands, and we encourage readers to do their own due diligence when evaluating any solution.