Skip to main content

All articles

Website Accessibility in 2026: What UK Small Businesses Actually Need to Know

8 min read

Accessibility tends to get filed away as either a niche legal concern or a box-ticking exercise for big organisations — something with no real bearing on a small local business. Neither is quite true. Most accessibility work overlaps almost perfectly with plain good design, and a surprising amount of it takes an afternoon rather than a rebuild. Here's what it actually means, where UK small businesses stand legally, and where to start.

What accessibility actually means

Website accessibility means building a site that people with a range of disabilities — visual, motor, cognitive, hearing — can actually use. That covers things like someone using a screen reader because they're blind or partially sighted, someone navigating entirely by keyboard because a mouse isn't usable for them, someone with colour blindness who can't distinguish low-contrast text, or someone with a cognitive condition who needs a clear, predictable layout to follow what's happening.

It's a broader group than most business owners assume — accessibility needs touch a significant proportion of any customer base at some point, whether that's a permanent disability, a temporary injury, or simply a hard-to-read screen in bright sunlight.

The UK legal picture, without the scaremongering

The Equality Act 2010 requires service providers to make reasonable adjustments for disabled customers, and that's generally understood to extend to websites, since a website is how many businesses now deliver their service. Public sector bodies face a stricter, explicit set of accessibility regulations with specific technical requirements and audit obligations.

For private small businesses, the position is closer to "act reasonably" than "meet a fixed certification". There isn't a small-business accessibility exam to pass, and no realistic scenario where a local tradesperson's website faces enforcement action for a missed alt tag. That said, legal claims relating to inaccessible websites have increased in some markets in recent years, and the direction of travel is clearly towards higher expectations — which makes this a sensible thing to get ahead of rather than a genuine cause for alarm.

WCAG and POUR, in plain English

WCAG (Web Content Accessibility Guidelines) is the internationally recognised standard for accessible web content, and it's organised into three levels: A (minimum), AA (the level almost everyone aims for in practice, including most legal frameworks), and AAA (a very high bar, rarely required or achieved outside specialist contexts).

The guidelines themselves are built around four principles, often shortened to POUR:

  • Perceivable — content must be presentable in ways people can perceive, such as text alternatives for images and captions for video.
  • Operable — all functionality must work via keyboard alone, not just a mouse, and there's no content that flashes in ways that could trigger seizures.
  • Understandable — text is readable, navigation is predictable, and forms tell people clearly what's expected and what's gone wrong.
  • Robust — content works reliably across different browsers and assistive technologies, now and as they update.

You don't need to memorise the full WCAG spec to get most of the value; aiming at AA and working through the quick wins below covers the large majority of real-world issues.

The quick wins that take an afternoon

A short, practical list that covers most of what actually matters for a typical small business site:

  • Real alt text. Every meaningful image needs a short, accurate description — not "image1.jpg", not stuffed with keywords, just what the image actually shows.
  • Sufficient colour contrast. Light grey text on a white background looks stylish and is unreadable for a lot of people. WCAG AA sets minimum contrast ratios for exactly this reason.
  • Labelled form fields. Every input needs a proper, associated label — not just placeholder text that vanishes the moment someone starts typing.
  • A logical heading structure. One H1 per page, headings used in order (H2 before H3, not skipped), so screen readers can navigate the page's structure the way sighted users scan it visually.
  • Full keyboard access. Every link, button and form should be reachable and usable by pressing Tab and Enter alone, with nothing that only responds to a mouse hover or click.
  • Visible focus states. A clear outline or highlight showing which element is currently selected when navigating by keyboard — often stripped out for looking "untidy", which quietly breaks usability for keyboard users.

Why accessibility overlays don't fix it

A category of plugin has grown up promising instant accessibility compliance via a small floating widget bolted onto an existing site — adjusting font size, contrast or spacing on the fly. They're appealing because they're cheap and quick to install.

They're also widely criticised by disabled users and accessibility professionals, because they attempt to patch problems in the browser rather than fixing the underlying markup, and often interfere with the assistive technology people already use and are comfortable with, making things worse rather than better. A number have featured in legal claims themselves rather than preventing them. There's no substitute for building accessibility into the actual code and content of a site — it's slower, but it's the only version that actually works.

Where accessibility overlaps with SEO and page speed

Most of what improves accessibility also improves the technical fundamentals search engines assess. Proper heading structure helps both a screen reader and Google understand what a page is about. Descriptive alt text serves blind users and also gives search engines context for image search. Clean, semantic HTML tends to perform better in Lighthouse and PageSpeed Insights audits than markup stuffed with unnecessary divs and scripts. This isn't a coincidence — both disciplines reward a site that's built cleanly and communicates clearly, which is also, unsurprisingly, what makes a good website design in the first place.

Building it in from the start

The cheapest time to address accessibility is during design and build, not as a retrofit years later. It's far quicker to choose an accessible colour palette, structure content with proper headings, and write real alt text as you go than to audit and rework an existing site page by page.

It also feeds directly into how a site is perceived generally — a clear, well-structured, easy-to-use site simply feels more professional, which is a large part of what makes a website feel trustworthy to any visitor, disabled or not. If you're planning a new site or a redesign, it's worth raising accessibility explicitly with whoever's building it through our web design service rather than assuming it'll be handled by default.

Common questions

Is website accessibility a legal requirement in the UK?

The Equality Act 2010 requires service providers to make reasonable adjustments, and that's generally understood to include websites. Public sector bodies have stricter, explicit regulations; private small businesses are expected to act reasonably rather than meet a fixed certification.


What is WCAG?

The Web Content Accessibility Guidelines — the international standard for accessible web content, organised into A, AA and AAA levels. AA is the level almost everyone aims for in practice.


What are the quickest accessibility wins?

Real alt text on meaningful images, sufficient colour contrast, labelled form fields, a page structure that uses proper headings, and making sure everything can be operated with a keyboard alone.


Do accessibility overlays fix the problem?

No. Third-party overlay widgets are widely criticised by disabled users and accessibility professionals, and they've featured in legal claims rather than preventing them. Fixing the underlying markup is the only real solution.

Want a website that does this automatically?

Every site we build is hand-coded for performance, SEO and security from day one. Free, no-pressure chat — usually within a day.

Free 30-min strategy callGet a quote