Most UK business owners assume web accessibility is something for government departments and big retailers to worry about. It is not. It is a legal duty that already applies to your website, a standard with a clear name and version number, and, more usefully, a set of fixes that overlap almost entirely with the things that make websites convert better. This guide covers what the law actually says, what WCAG 2.2 asks for, and where to start without commissioning a rebuild.
What does web accessibility actually mean for a UK business?
The scale of the audience is bigger than most owners expect. Scope reports that there are around 16 million disabled people in the UK, drawing on the government's Family Resources Survey, and that the total spending power of families with at least one disabled person is estimated at £274 billion a year. That figure is often called the purple pound, and it is not a niche. Scope also counts nearly half of pension age adults as disabled, a group that skews towards exactly the customers many local businesses depend on.
Accessibility is also not a binary. A site is not accessible or inaccessible; it has a number of barriers, and every barrier you remove lets more people complete the journey you built the site for.
Is web accessibility a legal requirement in the UK?
The core of the duty sits in Section 20 of the Equality Act 2010, which sets out three requirements. Organisations must take reasonable steps to remove disadvantages caused by their provision, criterion or practice, to deal with physical features that create barriers, and to provide auxiliary aids, which explicitly includes making information available in accessible formats. The Act also says the cost of adjustments cannot be passed on to the disabled person.
What the Act does not do is name a technical standard, which is why WCAG matters. Meeting a recognised standard is the clearest way to show you have taken reasonable steps. Enforcement against private firms is complaint driven rather than proactive, so businesses rarely hear anything until a customer, or a claimant firm, raises it. Waiting for that letter is a poor strategy when the fixes are largely one off and overlap with conversion work you should be doing anyway.
What is WCAG 2.2 and which level should you aim for?
The WCAG 2.2 Recommendation, first published in October 2023 and revised since, added nine new success criteria compared with WCAG 2.1. Several of them read like a checklist of small business website sins. Target Size (Minimum) addresses tap targets that are too small to hit on a phone. Consistent Help says your contact route should appear in the same place across pages. Redundant Entry stops forms asking for the same information twice in one process. Accessible Authentication (Minimum) pushes back on logins that rely on memorising or transcribing codes.
Level A alone leaves too many real barriers in place, and AAA is strict enough that the W3C itself does not recommend requiring it across entire sites. AA is where legal defensibility and practical effort meet.
How common are accessibility failures on business websites?
The WebAIM Million figures are worth sitting with, because they describe the sites your customers use every day, including yours and your competitors'. The report has run annually since 2019, and the pattern is stubborn: the overwhelming majority of home pages fail, and pages keep getting heavier year on year, which means more page furniture and more places for barriers to hide.
The competitive angle is the underrated one. If nearly every home page fails, an accessible site is unusual, and unusual in a way that millions of UK customers and their families will notice.
What are the most frequent accessibility errors, and how do you fix them?
Low contrast is usually a brand palette problem, pale grey body text on white being the classic offender, and it is fixed by darkening text colours until they pass the AA contrast ratio in a free checker. Missing alt text is fixed by writing a short description of what each meaningful image shows, and marking purely decorative images so screen readers skip them. Missing form labels are fixed by attaching a real label element to every input rather than relying on placeholder text that vanishes when someone starts typing. Empty links and buttons, often an icon with no text, are fixed by adding a visually hidden label so assistive technology can announce what the control does.
Because most small business sites are template driven, these fixes compound. Correct the contact form component once and every page using it improves.
How do you test your own website for accessibility?
For the automated pass, WebAIM's WAVE browser extension and the Lighthouse audit built into Chrome both flag contrast, alt text and labelling issues page by page. Run them on your home page, a service or product page, and your contact or checkout flow rather than trying to audit everything.
For the keyboard test, put the mouse aside and use Tab, Shift plus Tab, Enter and the arrow keys. You should always be able to see which element has focus, reach every menu item and button, and never get trapped in a widget. WCAG 2.2's new Focus Not Obscured criterion exists precisely because sticky headers and cookie banners so often hide the focused element.
For the screen reader test, VoiceOver ships free with every Mac and iPhone, and NVDA is free on Windows. Listen to your own checkout. If the screen reader announces button, button, button with no names, or reads your form errors as unlabelled text, you have found what a real customer hits.
What does accessibility have to do with sales and SEO?
This overlap is why accessibility belongs in conversion work rather than in a compliance silo. A properly labelled form is easier for everyone to complete on a phone. Text that passes contrast requirements is easier to read in sunlight. Link text that says view pricing for boiler service rather than click here helps a blind user, a search crawler and a distracted skim reader in exactly the same way. The structural clarity that WCAG demands is also what answer engines feed on, which is covered in more depth in this guide to AI search versus traditional SEO for UK businesses.
For online retailers the stakes are direct, because every barrier in a product page or checkout is a barrier in front of revenue. The practical patterns in this piece pair well with the broader advice in AI for UK shops and ecommerce. And if content production is the bottleneck, accessible writing habits, front loaded answers, descriptive headings, plain sentences, are the same habits covered in choosing an AI content writing service for a UK small business.
How much does it cost to make a website accessible?
Rather than quoting figures that vary wildly by site, it is more honest to describe the cost bands qualitatively. Template level fixes, contrast, labels, alt text, focus styles, are typically days of developer time, not weeks, because the six common error types are repetitive. Complex interactive features, bespoke booking systems, custom checkouts, embedded third party widgets, are where costs climb, because those need testing with real assistive technology and sometimes vendor cooperation.
Two traps inflate cost. The first is the overlay widget that promises instant compliance for a monthly fee; it does not fix the underlying code, so the legal exposure remains while the invoices continue. The second is treating accessibility as a one off audit rather than a habit, so the next batch of pages reintroduces every problem the audit removed. Build the checks into your publishing process and the ongoing cost approaches zero.
Where should a small business start this week?
A realistic first fortnight looks like this. Day one, scan home page, top service page and contact page with WAVE, and list every error. Days two to five, fix contrast, alt text, form labels and empty links across templates, which clears the categories WebAIM found on half or more of all home pages. Week two, keyboard test the money journey, fix any focus traps or invisible focus states, and write a short accessibility statement saying what standard you aim for and how customers can report problems. That statement matters, because it turns a potential complaint into a conversation.
If the site sits on a platform nobody in the business can confidently edit, or the audit surfaces structural problems, that is the point to bring in help rather than to stall. A web build that treats accessibility as a default rather than an add on avoids the whole retrofit cycle.
The gap between the average UK business website and an accessible one is not talent or budget. It is a short list of known fixes, applied consistently. With around 95 percent of home pages failing automated checks, according to WebAIM, the bar is low, the legal duty is real, and the customers you gain by clearing it were always trying to buy from you anyway.
Web Accessibility for UK Businesses — FAQ
Is website accessibility a legal requirement for private UK businesses?
Yes, in practice. The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, and Section 20 of the Act sets out three requirements, including a duty to provide auxiliary aids and to give people access to information in accessible formats. A website is a service, so a site that a screen reader user cannot operate can amount to a failure to make reasonable adjustments. The Act also states that organisations cannot pass the cost of adjustments on to the disabled person. There is no British regulator proactively auditing private sector sites the way public sector bodies are monitored, so enforcement usually arrives as a complaint or a claim rather than an inspection. That makes it tempting to ignore, but it also means the sensible route is simply to meet a recognised standard, and WCAG 2.2 level AA is the benchmark most UK advisers point to.
What is the difference between WCAG levels A, AA and AAA?
WCAG 2.2, first published as a W3C Recommendation in October 2023 and revised since, defines three conformance levels: A is the lowest, AA sits in the middle, and AAA is the highest. Level A covers the most basic barriers, such as images with no text alternative at all. Level AA adds requirements that most organisations treat as the practical standard, including minimum colour contrast and visible keyboard focus. Level AAA is stricter again, with tighter contrast ratios and requirements that are genuinely hard to meet across an entire site, which is why even the W3C does not recommend requiring AAA for whole sites. For a UK small business, aiming for AA across your key journeys, such as home page, product or service pages, contact and checkout, is the realistic and defensible target.
How common are accessibility problems on websites?
Very common. The WebAIM Million report, an annual automated test of the home pages of the top one million websites, found detectable WCAG 2 failures on 94.8 percent of them in its 2025 edition, with an average of 51 errors per page. The same report found low contrast text on roughly four in five home pages and missing alternative text for images on more than half. Those are only the problems automated tools can detect, so the true failure rate is higher once you include issues that need human judgement, such as confusing link text or forms that announce errors poorly. The practical takeaway for a UK business is that your competitors almost certainly have accessibility problems too, so fixing yours is both a compliance step and a genuine point of difference.
Can an automated accessibility checker or overlay widget make my site compliant?
No. Automated scanners such as WAVE or Lighthouse are excellent at finding a specific subset of problems, things like missing alt text, missing form labels and low contrast, but they cannot judge whether your alt text is meaningful, whether your page reads in a sensible order, or whether a keyboard user can complete checkout. Overlay widgets that promise one line of JavaScript compliance are more problematic still, because they sit on top of a broken page rather than fixing its underlying code, and many screen reader users report that they interfere with the assistive technology they already have configured. Use automated tools as a first pass to catch the obvious failures, then do manual keyboard and screen reader testing on your most important journeys. The combination is what actually reduces risk.
Does accessibility help with SEO and conversion?
There is a large overlap. Descriptive page titles, a logical heading structure, meaningful link text and alternative text for images are all WCAG requirements, and all of them also help search engines and AI assistants understand your pages. Accessible forms with clear labels and error messages reduce abandonment for every visitor, not only disabled ones, because the same clarity that helps a screen reader helps someone typing on a phone in a hurry. There is a commercial case too. Scope reports that there are around 16 million disabled people in the UK and that families with at least one disabled person have an estimated total spending power of £274 billion a year, so a site that quietly turns those customers away is leaving revenue on the table.
