← Back to blog

Does Your Small Business Website Need to Be Accessible? What UK Law Actually Says

Aaron Allen

A client asked us recently whether their website "had to" meet accessibility standards, because a supplier had mentioned WCAG in a contract review and nobody on their team knew what it meant or whether it applied to them. That's a more common conversation than you'd think, and the honest answer is: it depends what you sell and to whom, but there's more here than most business owners realise.

What the Equality Act 2010 actually requires

The Equality Act applies to services, and a website counts as a service. It doesn't hand small businesses a checklist or a specific technical standard to hit. What it requires is "reasonable adjustments" so that disabled customers aren't put at a substantial disadvantage compared to everyone else. There's no fixed WCAG level written into the law for private companies the way there is for the public sector, where the Public Sector Bodies Accessibility Regulations 2018 explicitly require WCAG 2.2 AA.

That gap sometimes gets misread as "so it doesn't really apply to us." It does, it's just less prescriptive. If a disabled customer can't use your site (a screen reader can't navigate your menu, or your checkout form has no visible labels) and you've made no attempt to fix it, that can constitute a failure to make reasonable adjustments, and it's the kind of thing that ends up in a solicitor's letter before it ends up in court. Most cases never get that far, but the exposure is real, and it's grown as more disabled consumers shop online rather than in person.

The European Accessibility Act changed the picture in 2025

If you sell to consumers in the EU, even as a UK-based business, this is worth paying attention to. The European Accessibility Act came into force on 28 June 2025, and it requires digital products and services sold to EU consumers, including e-commerce websites, banking apps, and certain other online services, to meet accessibility standards broadly aligned with WCAG 2.1 AA. It applies based on where your customers are, not where your business is registered, so a UK company selling into France or Germany can fall under it even though the UK itself has no equivalent domestic law for private businesses.

If most of your customers are UK-based and you don't sell into the EU, the EAA doesn't touch you directly. If you run an online shop with EU customers, it's worth a proper look rather than assuming Brexit put it out of scope.

What "accessible" actually means day to day

Full WCAG 2.2 AA compliance is a genuine technical exercise, and for most small business sites it's not where to start. The bulk of real-world accessibility problems come down to a handful of things:

Text that doesn't have enough contrast against its background, especially light grey text on white, which is common in "clean" modern designs and genuinely unreadable for a lot of people, not just those with diagnosed vision impairments. Images with no alt text, so a screen reader either skips them entirely or reads out the filename. Forms where the input boxes aren't properly linked to their labels, so a screen reader user can't tell what a field is asking for. Buttons and links that only make sense visually, like a row of icons with no text equivalent. And sites that can't be operated with a keyboard alone, which matters for people with motor impairments and also for anyone whose mouse or trackpad has just stopped working, which is more people than you'd guess on any given day.

None of these require a rebuild. They're mostly things that get fixed during development if the person building the site knows to check for them, and retrofitted with a few days of focused work if they don't.

The business case holds up even if the legal one feels distant

Roughly 16.1 million people in the UK are disabled, about 1 in 4 of the population, based on the Family Resources Survey and 2021 Census data. Research from We Are Purple puts the collective spending power of disabled people and their households at around £274 billion a year, with an estimated £24.8 billion of that specifically online. Separate research on the "Click-Away Pound" (what disabled shoppers spend elsewhere when a site doesn't work for them) put the annual loss to inaccessible retail sites at over £17 billion, and found that seven in ten disabled customers will simply leave a website they find difficult to use rather than push through it. A meaningful share said they'd pay more to buy from a site that works properly than deal with a cheaper one that doesn't.

That's not a niche audience, and it's not charity. It's customers who are already trying to give you money and hitting a wall before they can.

Where to actually start

You don't need an accessibility consultant and a formal audit to make meaningful progress. A realistic starting point looks like this:

Run your homepage and one or two key pages (your contact form, your main service or product page) through a free automated checker like WAVE or the Lighthouse accessibility audit built into Chrome's dev tools. These won't catch everything, but they'll surface obvious problems like missing alt text and poor colour contrast in minutes. Then try navigating your own site using only the Tab key, no mouse, and see how far you get through your own contact form. If you genuinely can't find where you are on the page at any point, that's exactly what a keyboard-only visitor experiences. Check that every form field has a visible, properly linked label rather than just placeholder text that disappears when you start typing, which is a common issue on sites built with off-the-shelf templates.

Fixing what those three checks turn up usually covers the majority of real accessibility problems on a typical small business site, without needing a full technical audit.

If you're planning a new site or a redesign, the cheapest time to build this in is during development, not after launch. At Digital Hand we build accessibility checks into every website project from the start rather than treating it as an add-on, partly because it's genuinely better for the business case above, and partly because retrofitting it later almost always costs more than doing it properly the first time. If you're not sure where your current site stands, get in touch for a free 15-minute consultation and we'll give you a straight answer.