PortfolioBlogAboutContact
Hero image

The Accessibility Law the UK Never Wrote

Published: June 01, 2026

"We're a UK company, the EAA doesn't apply to us, and there's no ADA over here, so we're fine." I have heard a version of this from more than one business owner, usually said with relief, as if Brexit quietly cancelled their accessibility obligations. It is the most expensive sentence in UK digital compliance, and almost everyone who says it believes it.

Here is the part that catches people out. The UK genuinely does not have a dedicated web accessibility law for the private sector. No EAA. No US-style lawsuit industry. No statute that says "you must pass WCAG 2.1 AA." If you only read the headlines, the UK looks like the relaxed one in the room.

It is not. The law that actually governs you is older, broader and quieter than the EAA, and it has been on the books since 2010. This post covers what UK law really requires, what "reasonable adjustment" looks like once you write the code, what it costs when it goes wrong, and whether a real accessibility law is finally on the way.

I Shipped a Site to a Standard the Law Never Names

When I took CeHDI (cehdi.org) to WCAG 2.1 and 2.2 AA, no statute handed me a checklist. There is no UK law that says "the focus order must be logical" or "text needs a 4.5:1 contrast ratio." I worked to WCAG because WCAG is the only standard that turns "make your site accessible" into something a developer can actually build and test.

The work was concrete, not abstract. Keyboard focus order so a screen reader user moves through the page in a sensible sequence. Colour contrast fixed on text that looked fine to me and failed for someone with low vision. Form fields with real labels tied to their inputs, not placeholder text pretending to be a label. Semantic landmarks so assistive tech can skip to the main content. Alt text that describes the image instead of repeating the file name. None of that is in an Act of Parliament. All of it is exactly what a UK court would later call a "reasonable adjustment."

That is the lesson that frames everything below: "reasonable adjustment" is not vague once you are the one building it. It resolves into a specific, testable set of WCAG success criteria. And if you think only small or careless sites fail these checks, look at the accessibility audit I ran on X.com. A platform with effectively unlimited budget still missed AA criteria a junior dev could catch. "Reasonable" is not "whatever the big companies happen to ship." You can read the full CeHDI remediation breakdown here.

So What Does UK Law Actually Say?

The governing law is the Equality Act 2010. It applies to anyone providing a service to the public, and a website is treated as a means of delivering that service electronically. E-commerce, SaaS, banking, booking, a restaurant's menu page: if the public uses it, it is in scope. In Northern Ireland the equivalent instrument is the Disability Discrimination Act 1995, which works on the same principle.

The duty itself is to make reasonable adjustments so that disabled users are not put at a substantial disadvantage. Two features of that duty matter more than anything else:

  • It never names WCAG. There is no statutory line that says "conform to WCAG 2.1 Level AA." The Act describes an outcome, not a technical specification.
  • It is anticipatory. You are expected to design for accessibility in advance, not to wait for a disabled user to complain and then scramble to fix it. The obligation exists before anyone has been turned away.

Most "the law is too vague to bother with" takes stop at the first point and miss the second. That is the mistake.

Vague Sounds Like a Loophole. It's the Opposite.

Put the two regimes side by side and the trap becomes obvious.

The EU's European Accessibility Act is narrow but specific. It applies to a defined list of product and service categories, and it points at an explicit technical standard (EN 301 549, which lands on WCAG 2.1 AA). If you are not in a named category, you can argue you are out of scope.

The UK Equality Act is the mirror image: broad but unnamed. It covers every public-facing service, with no category list to fall outside of, but it never specifies a standard. People read "no named standard" as "no hard requirement," so they defer. That reasoning is backwards. Because the duty is anticipatory and the scope is unlimited, the practical exposure in the UK is wider than under the EAA, not narrower. There is no "we're not a covered category" escape hatch, because there are no categories.

And here is where the missing standard reappears anyway. When a claim arises, the yardstick a court or a regulator reaches for to decide whether your adjustment was "reasonable" is WCAG 2.1 or 2.2 AA. So "the law doesn't mention WCAG" quietly collapses into "WCAG is the evidence standard you will be measured against." Same destination, fewer signposts on the way.

The Public Sector Plays by a Harder Rulebook

If you build for government, councils, the NHS or universities, the vagueness disappears entirely. The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, usually shortened to PSBAR, name the standard directly: the A and AA success criteria of WCAG, "as amended from time to time." That phrasing is deliberate. The bar rises automatically as WCAG evolves, with no need to pass new legislation.

The enforcement machinery is real, and worth knowing even if you only work private sector, because it shows the direction of travel:

  • GDS (the Government Digital Service) monitors public sector sites and apps. It began assessing against the newer WCAG 2.2 criteria in October 2024, having monitored to 2.1 AA before that.
  • A published, accurate accessibility statement is mandatory. The CDDO can publicly name organisations that fail to maintain one.
  • The Equality and Human Rights Commission (England, Scotland and Wales) and the Equality Commission for Northern Ireland enforce, with powers to investigate, issue notices and bring proceedings.

The private sector is on the same trajectory. It is simply a step behind, without the monitoring body breathing down its neck yet.

What It Actually Costs When It Goes Wrong

The risk shape in the UK is different from the EU's. There is no regulator handing private companies five and six figure fines for an inaccessible checkout. The exposure is individual discrimination claims, and they are not hypothetical:

  • RNIB v BMIbaby (2012). The RNIB took the airline to task over a booking site that visually impaired users could not navigate. It settled privately, and the company agreed to overhaul its digital platforms.
  • Holly Scott-Gardner v Student Loans Company (2021). A £5,000 settlement after a blind student could not complete an inaccessible Disabled Students' Allowance form.
  • Stephen Campbell v HSCNI (2023). A £3,000 settlement when a blind man could not use his screen reader on a Health and Social Care Northern Ireland site to apply for a promotion, brought under the DDA.

Look at those numbers and the temptation is to shrug. That is the wrong read. The settlement figure is almost never the real cost. The real cost is remediation under a legal deadline, the legal and management time the claim eats, and the reputational damage of being the company that locked disabled people out. It is consistently cheaper to design for accessibility up front than to be forced into it by a claim.

Two Laws Are Already Pointing at Your UK Business

Here is the twist that makes 2026 different. A UK business can now be in scope of two accessibility regimes at the same time.

At home, the Equality Act applies, with its anticipatory duty and individual claims. Abroad, the European Accessibility Act, live since 28 June 2025, applies to any business selling covered products or services to EU consumers, regardless of where that business is based. Brexit does not exempt you. If you are a UK SaaS company with paying customers in Germany or France, the EAA reaches you directly.

So if you read about the EAA, concluded "we're a UK company, not my problem," and closed the tab, you may have two problems rather than zero. I have written about the EU side in detail: the real-world EAA penalties landscape and why waiting on WCAG in the EU is now the most expensive option. The UK angle does not replace those. It stacks on top of them.

Is a Real UK Accessibility Law Coming?

This is the question I get asked most, so let me give the honest answer and timestamp it. As of mid-2026, there is no confirmed domestic accessibility bill for the UK private sector, and no active government consultation. The legal and trade commentary keeps repeating that "the UK may follow with its own equivalent in time," but there is nothing on the order paper to point at. Anyone telling you a UK EAA is imminent is guessing.

What is genuinely moving matters more than a hypothetical bill:

  • The EAA's reach pulls UK exporters in whether or not Parliament ever acts, simply by binding anyone who sells into the EU.
  • The WCAG bar keeps ratcheting up on its own. PSBAR's "as amended from time to time" wording took public sector monitoring from 2.1 to 2.2 with no new law, and private sector best practice tracks the same climb.
  • Indirect pressure is building through the Procurement Act 2023, which bakes accessibility into public buying and flows downhill to suppliers, and the British Sign Language Act 2022, though neither is a web accessibility statute.

So the regulation "coming to the UK" is mostly the EU's law arriving through the back door, plus a WCAG standard that quietly rises by itself. The honest reframe of "is it coming?" is "it is already here, just not labelled the way you expected."

Conclusion: The Missing Law Is Not a Reprieve

The UK never wrote the accessibility law everyone is waiting for, and people keep mistaking that gap for permission to defer. It is the opposite. The duty already exists, it is anticipatory, it covers every public-facing service you run, and the standard a court will judge you against, WCAG 2.1 and 2.2 AA, is already settled. The only thing missing is the signpost, and the cases are already real.

The good news is that this is a solvable, finite problem. WCAG AA is a defined target. I have taken a live site there, and I have audited sites that thought they were already compliant and were not.

If you run a UK site and you have been treating the absence of a named law as a reason to wait, that is exactly the exposure worth closing now. I offer a paid WCAG audit that turns the Equality Act's vague duty into a concrete, evidenced pass or fail you can actually stand behind. Get in touch to book one.

If you would rather build to this standard by default and never have the conversation, that is what my Skool community, The Agentic Architect Lab is for: senior dev habits, applied with AI speed.

Sources

Building with AI beyond this article?

I run The Agentic Architect Lab, live builds, agent workflows, and a playbook for technical founders shipping solo. No toy demos.

Join the Lab
Next Post →