16 million UK adults live with a disability. The Equality Act already applies to your website, whether you have thought about it or not.
There is no UK law that explicitly says "your website must meet WCAG standard X by date Y" — and that absence of a clear, prescriptive deadline is precisely why most small business websites have never properly considered accessibility at all. But the Equality Act 2010, which has applied to every UK service provider since long before most current websites existed, already requires businesses to make "reasonable adjustments" so disabled customers can access their services — and in 2026, the legal consensus has shifted decisively toward treating an inaccessible website as exactly the kind of barrier this duty was written to address.
16 million+ — people in the UK live with a disability — roughly one in four of the population
£2 billion — estimated monthly loss to UK businesses from failing to meet disabled customers' needs online
£274 billion — estimated annual spending power of disabled people in the UK — the "purple pound"
1. What the Law Actually Says — And What It Does Not
The Equality Act 2010 does not name a specific technical standard. What it requires is that service providers — which includes almost every UK business with a customer-facing website — make reasonable adjustments to remove barriers that prevent disabled people accessing their services on an equal footing. A website that a screen reader cannot navigate, that requires precise mouse control a motor-impaired visitor cannot manage, or that uses colour contrast a visually impaired visitor cannot read, is, in the current legal consensus, a barrier of exactly this kind.
📄 PRIMARY SOURCE — How the courts and regulators actually assess "reasonable"
While the Equality Act itself does not name WCAG, courts, the Equality and Human Rights Commission (EHRC), and the Equality Advisory and Support Service consistently use WCAG 2.2 Level AA as the practical benchmark for whether a business has made reasonable adjustments. Meeting WCAG 2.2 AA is strong evidence of compliance — though not an absolute legal guarantee — and is the standard explicitly mandated for the public sector under the separate Public Sector Bodies Accessibility Regulations 2018. A disabled visitor who experiences a genuine access barrier can bring a claim in the County Court, and courts can award damages including compensation for distress.
1.1 Are Small Businesses Exempt?
There is no blanket exemption for small UK private businesses under the Equality Act — the reasonable adjustments duty applies broadly, though what counts as "reasonable" does account for a business's size and resources, meaning the bar for a five-person trade business is not identical to the bar for a large retailer. The separate European Accessibility Act, which came into force in June 2025, does include a specific microenterprise exemption (fewer than 10 employees, under €2 million annual turnover) — but this is EU legislation that applies to businesses serving EU customers, not a UK Equality Act exemption, and most UK small businesses serving only UK customers should not rely on it.
2. WCAG 2.2 AA, Explained Without the Jargon
WCAG (Web Content Accessibility Guidelines) is the international standard underlying nearly every accessibility law worldwide, organised around four principles, commonly remembered by the acronym POUR: content must be Perceivable (visible or audible to every user, including those using screen readers), Operable (every function reachable without a precise mouse — keyboard navigation is the most common test), Understandable (clear language and predictable navigation), and Robust (works correctly with assistive technology, both today's and tomorrow's).
Requirement | What it means in practice | How to check it yourself |
Alt text on images | Every meaningful image needs a text description a screen reader can read aloud | View your page source, or use a free tool like WAVE (wave.webaim.org) |
Keyboard navigation | Every link, button, and form field must be reachable using only the Tab key — no mouse | Put your mouse away and try to use your own site with just the keyboard |
Colour contrast | Text must have sufficient contrast against its background to be readable by low-vision users | WebAIM's free Contrast Checker tool tests any colour combination instantly |
Descriptive links | Link text should describe the destination ("Read our pricing guide") not generic phrases ("click here") | Scan your own pages for "click here" or "read more" links and rename them |
Form labels | Every form field needs a properly associated, visible label a screen reader can announce | Check that every input field has a clear, programmatically linked label, not just placeholder text |
Visible focus indicators | When tabbing through a page, it should be visually obvious which element is currently selected | Tab through your site and check whether you can always see where you are |
3. The Popular "Fix" That Does Not Actually Work
⚠️ WARNING — Accessibility overlays are not a substitute for real accessibility work
A category of tools — sold as a single line of code that "instantly makes your site accessible" via a floating widget offering font-size and contrast controls — has become widely marketed to small businesses. The accessibility community, and the W3C (the body that develops WCAG itself), has been consistent and clear: these overlays layer cosmetic controls on top of underlying code problems that remain completely unfixed. They do not make a site WCAG compliant, and several major overlay products have faced legal action in the US specifically for making false compliance claims. A site that genuinely cannot be navigated by keyboard, or that genuinely lacks alt text, has not had either problem solved by adding a widget that lets a sighted visitor enlarge the font.
✅ THE FIX — What actually works instead
Genuine accessibility is built into the underlying code — semantic HTML, properly labelled forms, real alt text, keyboard-navigable interactive elements — not bolted on afterwards with a script tag. This is one of the structural advantages of a hand-coded site over a heavily plugin-dependent page-builder site, as covered in our build process guide: accessibility decisions are made deliberately, page by page, during construction, rather than retrofitted with a third-party widget after the fact.
4. Why This Is Not a One-Time Project
A site that passes an accessibility audit on launch day can fail it within weeks if nobody maintains the discipline. A content editor uploads a new image without alt text. A new contact form is added without properly labelled fields. A colour scheme update accidentally drops contrast below the readable threshold. None of these are dramatic events — they are the ordinary life of an actively maintained website — but each one reintroduces a genuine barrier. This is precisely the kind of ongoing technical discipline covered by the care retainer service for WebWise clients, alongside the security and performance monitoring covered in our broader build process guide — accessibility, once achieved, needs to be actively protected against every subsequent change to the site.
5. Accessibility Also Improves Your Google Rankings
This is not a coincidence — accessibility and SEO share substantial underlying technical overlap. Alt text that describes an image properly for a screen reader is the same alt text Google uses to understand image content, as covered in our schema markup guide. Descriptive link text helps both a screen reader user and Google's crawler understand what a page is about. Clean, semantic HTML structure — proper heading hierarchy, properly labelled forms — is exactly the same structure covered throughout our Core Web Vitals and E-E-A-T guides as a ranking factor. A genuinely accessible site and a genuinely well-optimised site are, to a significant degree, the same underlying technical work viewed from two different angles.
6. The Commercial Case, Beyond the Legal One
Beyond legal exposure, the commercial case stands on its own. Research from Accenture, cited consistently across current accessibility guidance, indicates that customers with disabilities tend to be more brand-loyal and spend more once they find a business that genuinely works for them — a meaningful detail given that an inaccessible website does not just create legal risk, it actively turns away a customer base with an estimated £274 billion in annual UK spending power, as covered in the statistics above. For a UK trade business specifically, this connects directly to the conversion principles covered throughout our CRO guide and mobile conversion guide: a visitor who cannot navigate your form because it lacks proper labels, or cannot read your phone number because of poor contrast, is lost for exactly the same underlying reason a visitor with a slow-loading page is lost — the website created friction that an able-bodied, fully-sighted visitor on a fast connection never encountered, and therefore never noticed needed fixing.
Conclusion: Build It In, Not On
The Equality Act already applies to your website. WCAG 2.2 AA is the practical standard courts and regulators use to judge whether you have met that duty. The single most important thing to take from this article is the distinction in Section 3: genuine accessibility is built into a site's code, deliberately, during construction and maintained afterwards — it is not a widget added retroactively. This is, not coincidentally, exactly the discipline a properly hand-coded site, built and maintained with the process covered in our build process guide, already applies by default.
If you want your current site audited against the checklist in Section 2 — most of which takes minutes to check yourself using the free tools named there — the starting point is a 15-minute call at webwise.digital/contact.
