For years, web accessibility was treated by many businesses as a nice-to-have — something to get to once the important work was done, which usually meant never. That position is no longer tenable. Accessibility has become a legal obligation across much of the market, the enforcement landscape has tightened, and the businesses still treating it as optional are exposing themselves to real risk while quietly excluding a significant share of their potential customers. This is a clear, practical guide to what accessibility actually requires, what the law now expects of UK businesses, and how to build sites and apps that everyone can use without it becoming a burden.
Problem Statement
Roughly one in five people has a disability of some kind, and many more experience temporary or situational limitations — a broken arm, bright sunlight on a screen, a noisy environment. An inaccessible website does not just inconvenience these users; it shuts them out entirely. Someone using a screen reader cannot buy from a shop whose buttons have no labels. Someone who cannot use a mouse cannot complete a form that only works with one. Someone with low vision cannot read text that does not meet contrast standards. Each of these is a customer turned away, and increasingly, a legal exposure.
The deeper problem is that accessibility is usually treated as something to test for at the end rather than design for from the start, which makes it expensive and incomplete. Retrofitting accessibility onto a finished site is far harder and costlier than building it in, and the bolt-on overlay tools that promise an easy fix do not, in practice, deliver compliance or a genuinely usable experience.
Industry Challenges
- Treating it as optional — Many businesses still regard accessibility as a nice-to-have, which is now both a legal and a commercial mistake.
- The retrofit trap — Bolting accessibility onto a finished product is expensive and partial; it belongs in the design from the outset.
- Overlay snake oil — Automated overlay widgets that claim instant compliance do not deliver it and can make the experience worse for the users they target.
- Knowledge gaps — Teams often do not know what the standards require or how to test against them, so problems go unnoticed until a complaint arrives.
What the Standards and Rules Require
WCAG, the standard everything points to
The Web Content Accessibility Guidelines, known as WCAG, are the standard that laws and regulations refer to. They are organised around four principles: content must be perceivable, operable, understandable, and robust. In practice this means things like text alternatives for images, full keyboard operability, sufficient colour contrast, clear and consistent navigation, and markup that assistive technologies can interpret. Most legal requirements point to meeting WCAG at the AA level, which is the practical target businesses should aim for.
The legal landscape for UK businesses
UK businesses sit under several overlapping obligations. The Equality Act requires that services, including digital ones, do not discriminate against disabled people and make reasonable adjustments, which courts and regulators increasingly read as covering websites and apps. Public sector bodies have specific, binding accessibility regulations. And any UK business selling into the European Union is now within reach of the European Accessibility Act, which sets firm accessibility requirements for a broad range of digital products and services and has moved accessibility from guidance to enforceable law across that market. The direction of travel everywhere is towards firmer requirements and more enforcement, not less.
Implementation Considerations
The decisive decision is to build accessibility in from the start. When it is part of the design and development process — considered in the wireframes, built into the components, checked as features are made — it adds little cost and produces a genuinely usable result. When it is left to the end, it becomes an expensive remediation project that catches only some of the problems. The principles overlap heavily with good design generally, which is why we treat them as part of the craft rather than a separate compliance exercise, as we discussed in our writing on UX principles that drive results.
Testing needs both automated and human methods, because each catches what the other misses. Automated tools quickly find a meaningful share of issues — missing labels, contrast failures, structural problems — and should run continuously. But they cannot judge whether navigation makes sense, whether the experience is actually usable with a screen reader, or whether the focus order is logical. That requires testing with assistive technology and, ideally, with disabled users, which is the only way to know the site genuinely works rather than merely passing checks. This pairing of automated and human testing mirrors the wider QA discipline we have written about.
On cost, building accessibility in is inexpensive while retrofitting is not, and both are far cheaper than a legal complaint or the lost custom of excluded users. On the commercial side, accessible sites tend to be better for everyone — clearer, faster, more navigable — and they also align with the search engines' preference for well-structured, semantic markup, so the benefit extends beyond compliance.
Real-World Use Cases
- E-commerce — Where an inaccessible checkout directly loses sales and carries clear legal exposure under equality law.
- Public-facing services — Where binding accessibility regulations apply and non-compliance is a direct breach.
- Businesses selling into the EU — Where the European Accessibility Act now imposes enforceable requirements on digital products and services.
- Any site with forms — Where keyboard operability and proper labelling determine whether a large group of users can complete a basic task.
Common Mistakes to Avoid
- Leaving it to the end — Retrofitting is expensive and partial; accessibility belongs in the design from the start.
- Relying on overlay widgets — They do not deliver compliance or a good experience, and they create a false sense of safety.
- Testing only with automated tools — They catch some issues but cannot judge real usability with assistive technology.
- Forgetting keyboard users — A site that only works with a mouse excludes a significant group and fails the standard.
- Ignoring contrast and labelling — The most common and most easily fixed failures, yet the ones most often left in place.
Future Trends
Accessibility requirements are tightening and enforcement is increasing across both the UK and the EU, so the risk of treating it as optional only grows. Tooling is improving, with better automated testing and accessibility checks built into development workflows, which lowers the effort of doing it well. And there is a growing recognition that accessible design is simply good design — that building for the full range of human ability produces clearer, more robust products for everyone, which is shifting accessibility from a compliance chore towards a quality standard.
Why Businesses Should Act Now
The legal exposure is real and growing, the commercial cost of excluding a fifth of your potential customers is constant, and the cost of building accessibility in is low compared with both. Acting now — making accessibility part of how you design and build — protects you legally, widens your market, and improves your product for everyone. Waiting until a complaint forces the issue means paying for an expensive retrofit under pressure, which is the worst way to do it.
Conclusion
Web accessibility has moved decisively from optional to obligatory, and meeting WCAG at the AA level is now both a legal expectation and a commercial necessity for UK businesses. The key is to build it in from the start, test with both automated tools and real assistive technology, and treat it as part of good design rather than a bolt-on. Done that way it is inexpensive, it widens your market, and it improves your product for everyone. We build accessibility into the work as a matter of course, and we are glad to assess where your site stands and what it would take to meet the standard.
Frequently Asked Questions
Is web accessibility a legal requirement in the UK?
In effect, yes, through several overlapping obligations. The Equality Act requires services, including digital ones, not to discriminate against disabled people, public sector bodies have binding accessibility regulations, and businesses selling into the EU fall under the European Accessibility Act. The standards point to meeting WCAG, usually at the AA level.
What is WCAG?
The Web Content Accessibility Guidelines, the standard that laws and regulations refer to. It is built on four principles — content must be perceivable, operable, understandable, and robust — and AA is the level businesses should aim for in practice.
Do accessibility overlay widgets make us compliant?
No. Automated overlay tools that promise instant compliance do not deliver it and often worsen the experience for the users they claim to help. Genuine accessibility comes from building it into the site, not bolting a widget on top.
Can we just test with automated tools?
Automated tools are valuable and catch a meaningful share of issues, but they cannot judge whether the site is genuinely usable with assistive technology or whether navigation makes sense. Real compliance needs both automated checks and human testing with screen readers and keyboards.
Is it expensive to make a site accessible?
Building accessibility in from the start adds little cost. Retrofitting it onto a finished site is expensive and partial, and a legal complaint or lost custom is costlier still. The economics strongly favour doing it from the outset.
Does accessibility help with anything besides compliance?
Yes. Accessible sites are clearer, more navigable, and more robust for everyone, they widen your potential market by not excluding disabled users, and their well-structured, semantic markup aligns with what search engines prefer, so the benefit extends well beyond meeting the law.