Expect BestWebsite accessibility is usually met with one of two reactions: it is a legal minefield we cannot afford to think about, or it is something that only applies to councils and the NHS. Neither is right, and both lead to the same outcome, which is doing nothing.
The practical position for a UK business is more manageable than either.
Where the law actually sits
The Equality Act 2010 requires service providers to make reasonable adjustments so disabled people are not put at a substantial disadvantage. That duty is generally understood to extend to websites, because a website is how most businesses now deliver their service.
Public sector bodies sit under separate, more specific regulations with a required standard and a published statement. Most private businesses do not. What they have instead is the reasonable adjustments duty, which is less prescriptive and therefore easier to satisfy sensibly rather than exhaustively.
The honest summary: you are unlikely to be prosecuted, and you are quite likely to be losing customers.
The commercial case, which is stronger
Around one in five people in the UK has a disability. Not all of those affect how someone uses a website, but many do, and the population skews older than most businesses assume. Poor contrast is a problem for a large share of people over sixty, not a minority concern.
Then there is the overlap nobody plans for. A video that works without sound helps deaf users and the far larger group watching on a phone in public. Clear labelling helps screen reader users and everyone filling in a form in a hurry. Good website accessibility work tends to improve the site for people who were never the target of it.
Website accessibility changes worth making first
You do not need a full audit to start. A short list accounts for most real barriers:
- Text contrast that is genuinely readable, not just technically passing on a good monitor
- Alt text on images that carry meaning, and empty alt on ones that are purely decorative
- Form fields with real labels, not placeholder text standing in for one
- Headings in order, describing the page structure rather than chosen for size
- Link text that makes sense alone, so not a page of "click here"
- Everything reachable and usable with a keyboard, no mouse
That list is a few days of work on most sites and removes more barriers than a long compliance document nobody reads.
What to avoid
The accessibility overlay industry sells a script you drop onto the site that promises compliance in a line of code. Accessibility advocates and disabled users broadly regard these as unhelpful, and in some cases actively obstructive, because they layer a second interface over an inaccessible one rather than fixing it. Several have been the subject of legal complaints in their own right.
There is no plugin that makes a site accessible. The work belongs in the markup.
How it connects to everything else
The technical foundations of accessibility are the same foundations that make a site fast, readable by search engines and easy to maintain. Semantic headings, descriptive links, real labels and sensible structure are what a screen reader needs and what a crawler needs. That is why accessibility work rarely feels wasted even when the motivation was compliance.
If you are rebuilding anyway, it costs almost nothing to build it in from the start, and considerably more to retrofit later. If you are not rebuilding, the short list above is the sensible place to spend a couple of days.
Our web design service builds this in as standard rather than selling it separately, and we are happy to look at an existing site and tell you where the real barriers are.