Website Accessibility for UK Businesses: The Law, the Basics, and Why It Wins You Customers

Quick answer

UK businesses have a legal duty under the Equality Act 2010 to make “reasonable adjustments” so disabled people aren’t excluded from their services, and courts and regulators treat websites as part of the service. Beyond the legal floor, the commercial case is blunt: roughly one in four UK adults has a disability, accessible sites rank better (Google rewards much of the same structure), and every accessibility basic (contrast, readable text, keyboard navigation, clear forms) makes the site easier for every visitor. Most small-business sites get 80% of the way there with a day of fixes costing £300 to £800.

What the law actually requires

The Equality Act doesn’t name websites explicitly, but service providers must not discriminate in how services are offered, and “reasonable adjustments” is an anticipatory duty: you’re expected to think ahead, not wait for a complaint. Public-sector bodies have explicit WCAG-based regulations; private businesses are judged on reasonableness. In practice, UK claims are rare but rising, usually settle, and the reputational cost of “local business sued over website disabled people can’t use” dwarfs the fix cost. The pragmatic standard to aim at is WCAG 2.2 level AA, the same benchmark government uses, and the one any future UK enforcement would almost certainly reference.

The basics that fix most sites

Notice the pattern in the right column: there is no trade-off. Accessibility work is usability work with a legal tailwind, which is why accessible sites measurably convert better: the same clarity that helps a screen-reader user helps the distracted phone user deciding whether to get in touch.

What it costs to fix

• DIY pass (free): run your homepage through the free WAVE or Lighthouse checkers, fix the flagged contrast and alt-text issues, tab through your forms. An afternoon of work catches the worst.
• Professional remediation (£300 to £800): a day or two fixing contrast, headings, forms, focus states and alt text across a typical small-business site, usually bundled sensibly into other work like a redesign.
• Accessible-by-default builds: the cheap route is specifying accessibility in the build brief, where it costs almost nothing extra. Retrofitting is what costs. Any competent professional build should hit WCAG AA basics as standard; ask the question before commissioning, not after.
• Avoid the overlay shortcut: “accessibility widget” overlays that promise one-line-of-code compliance are widely criticised by disabled users and accessibility bodies, and don’t fix the underlying code. Money spent there is better spent on actual fixes.

The five-minute self-audit

1. Tab through your homepage. Can you reach and operate everything? Can you see where focus is?
2. Zoom to 200%. Does the layout survive?
3. Squint test. Does the text hold up? (Proper check: WAVE’s contrast tool.)
4. Read your links aloud out of context. Do they say where they go?
5. Submit a form wrongly. Does the error tell you what to fix, near the field?

Fail two or more and your site is quietly turning away customers, disabled and otherwise. The deeper conversion failures usually travel together with these, which is why the fix list overlaps so heavily with why your website is losing you customers. Accessibility isn’t a compliance chore bolted onto web design; it’s what competent web design looks like from the inside.

Who is actually affected, and how they use your site

Accessibility discussions default to screen readers, which describe a minority of the people your site is failing. The broader picture is more ordinary and more commercially relevant.

Only the last row needs specialist knowledge. Every other row is design and copy discipline you can apply this week, and every one of them also helps a fully-sighted customer reading your quote page on a phone in a van. That overlap is why the low-contrast trend of the last decade, pale grey body text on white because it looks refined, is the single most common failure on small business sites, and the easiest to reverse. It is worth checking your brand palette against real backgrounds before you blame the website, since a mid-tone brand colour used for body text will never pass, which is a constraint worth knowing when choosing shades in the first place; the trade-offs are covered in logo colour psychology.

What good looks like on the pages that matter

The enquiry form. Every field has a visible label that stays visible while typing. Errors appear next to the field, in words, and say what to do rather than what went wrong: “Enter a phone number we can reach you on” beats “Invalid input”. The submit button says what it does. Required fields are marked in text, not only with a red asterisk.

The service page. Headings in real order without skipping levels. Prices and specifications in a proper table with header cells, not a picture of a table. Link text that reads sensibly out of context, so “our kitchen fitting process” rather than “read more”.

The navigation. Reachable by keyboard, with a visible focus outline you have not removed for aesthetic reasons. Dropdowns that open on click work for everyone; hover-only menus exclude touch and keyboard users simultaneously.

The gallery. Alt text that describes the job (“new consumer unit fitted in a Victorian terrace hallway”), not “IMG_4021” and not the same phrase repeated forty times. Decorative images take empty alt text so screen readers skip them.

What to ask a web supplier

• “Which standard do you build to, and at what level?” The expected answer names WCAG 2.2 and AA. Vagueness here predicts the retrofit invoice.
• “How do you test: automated tools, keyboard, or with assistive technology?” Automated checkers catch perhaps a third of issues. A supplier who only cites a Lighthouse score is telling you their ceiling.
• “Will the theme or page builder let me create inaccessible pages later?” Most will. Ask which components are safe and which are traps.
• “Is a keyboard and contrast pass included, or is it an extra?” Get it in the quote in writing.
• “What happens when my staff upload images without alt text?” A good answer involves a short editing guide and a prompt in the CMS, not a shrug.

Specified in a build brief, all of this adds close to nothing to the price. Added a year later it becomes a remediation project, which is the whole argument for buying it inside a fixed-fee web design scope rather than as a corrective purchase.

Mistakes that cost more than the fix

Buying an overlay widget and considering it done. Beyond the criticism from disabled users, the commercial risk is worse than doing nothing: you have documented that you knew about accessibility and chose a shortcut.

Publishing an accessibility statement you cannot support. A statement claiming full conformance on a site that fails basic contrast is a written admission. If you publish one, describe what you have done, what you know is outstanding, and how someone can report a problem.

Removing focus outlines. Designers strip them because they look untidy. It is the fastest way to make a site unusable by keyboard, and it takes one line of CSS to reinstate with a style you actually like.

Locking information in PDFs and images. Price lists as JPEGs, brochures as scanned PDFs, opening hours inside a graphic: all invisible to screen readers and to search engines. Whatever matters belongs in real text on a real page.

Where accessibility and speed meet

Both are ultimately about not making the visitor work. Heavy pages punish older devices and slower connections, which correlates strongly with the users least able to absorb friction elsewhere, and the same restraint fixes both: fewer scripts, smaller images, less motion, real text instead of images of text. Any remediation pass is a sensible moment to run the performance fixes that actually matter alongside it, and both belong on the pre-launch list rather than in a later audit, which is why several of these checks appear in the website launch checklist.

One practical sequencing note: if a redesign is anywhere in the next twelve months, do the free DIY pass now and hold the paid remediation until the rebuild. Paying to fix contrast and heading structure on a site you are about to replace is the one accessibility spend that genuinely is wasted, and it is worth deciding which of those two paths you are on before you commission anything.

Sources & Further Reading

• Accessibility Requirements Guidance, GOV.UK
• WCAG 2.2 Standard, W3C
• UK Disability Facts & Figures, Scope