WCAG compliance for UK small businesses: what you actually need

WebAIM’s 2026 scan of the top one million homepages found detectable WCAG failures on 95.9% of them. The same report found that 96% of all the errors it detected fell into just six categories (WebAIM Million 2026, retrieved 2026-09-26). Put those together and the picture is less grim than it first looks. Nearly every site has problems, but most of those problems are the same handful of fixable things.

Much of what’s written about WCAG and the law doesn’t help you act on that. Some of it tells you WCAG is a legal requirement for every UK business, which isn’t quite true. Some of it implies accessibility is optional, which isn’t true either. Vendor pages lean towards the scary version because it sells audits and overlay plugins.

This guide covers what the law says for a UK small business, when WCAG becomes an explicit requirement, what level to aim for, and which fixes to do first.

This isn’t legal advice. It’s general information from a web design studio that builds accessibility into client sites. If you need a judgement on your specific situation, speak to a solicitor or an accessibility consultant.

Key Takeaways

• For most private UK businesses, no law names WCAG. The Equality Act 2010 does require you to make reasonable adjustments for disabled customers, and that duty covers services provided through your website.
• The duty is anticipatory. You’re expected to think ahead about disabled customers generally, not wait until someone complains.
• Public sector bodies are different. They must meet WCAG 2.2 AA and publish an accessibility statement. If you build or run sites for them, expect that standard in your contract.
• WCAG 2.2 Level AA is the sensible target. Level A leaves out fixes that matter, and W3C itself doesn’t recommend requiring AAA across a whole site.
• Six issue types, led by low-contrast text and missing alt text, account for 96% of detected errors. Fixing those first gets you most of the practical benefit.

Is WCAG legally required for UK small businesses?

Not by name, for most private businesses. No UK law says “your website must meet WCAG”. What does apply is the Equality Act 2010, which requires anyone providing services to the public to make reasonable adjustments for disabled people. Your website is part of how you provide your service.

The Equality and Human Rights Commission’s updated statutory Code of Practice for services came into force on 5 August 2026. It spells out the website point directly: “The obligation also applies to the provision of services on a website” (EHRC Code of Practice for services, public functions and associations, 2026, para 3.6, retrieved 2026-09-26). Courts must take the Code into account where it’s relevant (Equality Act 2006, section 15(4), retrieved 2026-09-26).

The duty is anticipatory. Schedule 2 of the Act says the duty for service providers is owed to “disabled persons generally” (Equality Act 2010, Schedule 2, para 2, retrieved 2026-09-26). In practice, that means you’re expected to think ahead about the barriers disabled customers are likely to hit. It isn’t enough to wait for a named person to complain and then fix their specific problem.

“Reasonable” is judged on your circumstances. The Code says reasonableness is assessed objectively on all the circumstances, and lists factors such as how effective a step would be, how practical it is, its cost, and the provider’s resources. A sole trader with a five-page brochure site isn’t held to the same standard as a national retailer. Offering the same service another way, such as a phone line with the same prices as the website, can be part of a reasonable response. It’s rarely a substitute for fixing barriers on the site itself.

So where does WCAG come in? The Act doesn’t define what an accessible website looks like, so people reach for the standard that does. WCAG is the international standard and the one the UK government requires of its own sites, so it’s what an expert or a court would most likely compare your site against. The Act never mentions it, but it’s the most widely used yardstick for showing you’ve taken reasonable steps.

This is where a lot of small business guidance goes wrong in one direction or the other. “WCAG is the law” overstates it. “Accessibility is optional” ignores an anticipatory legal duty. The duty is binding and the standard is voluntary, and meeting WCAG is how you show you’ve met the duty.

One geographical footnote: the Equality Act covers England, Scotland and Wales. Northern Ireland has its own disability discrimination law, so check that separately if you trade there.

When WCAG is an explicit legal requirement

If you’re a public sector body, the rules are much stricter. Under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, public sector websites must “meet the Web Content Accessibility Guidelines (WCAG) 2.2 AA accessibility standard” and publish an accessibility statement (GOV.UK, Understanding accessibility requirements for public sector bodies, last updated 30 September 2024, retrieved 2026-09-26). For them, WCAG is the requirement itself.

That covers central and local government, and some charities and non-government organisations. Charities are generally exempt unless they’re mostly publicly funded or provide services that are essential to the public or aimed at disabled people.

Small businesses sometimes get caught by this indirectly, as suppliers. Suppose you build or run a website for a council, an NHS trust, a university or a publicly funded charity. (Schools and nurseries are only partially covered.) The regulations bind your client, not you. But GOV.UK is explicit that the public body stays “legally responsible for your website meeting accessibility requirements, even if you’ve outsourced your website to a supplier”. Public bodies therefore have every reason to write the standard into their supplier contracts.

In practice, that often turns WCAG 2.2 AA into a contractual requirement for you. If you supply digital work to public sector clients, check your contracts and tender documents for accessibility clauses. Make sure you can show conformance, ideally with a documented audit.

What about selling to EU customers?

If you sell to consumers in the EU, the European Accessibility Act may apply to you separately from UK law. It has been enforceable since 28 June 2025. It covers a defined list of products and services, e-commerce among them, and it applies to businesses outside the EU, including UK ones, that serve EU consumers (Travers Smith, “A new milestone for accessibility: the European Accessibility Act now applies”, retrieved 2026-09-26; European Commission, European Accessibility Act, retrieved 2026-09-26).

There’s a relevant carve-out for very small businesses. Microenterprises, meaning those with fewer than 10 staff and no more than €2 million in annual turnover or balance sheet, are exempt from the Act’s requirements for services, though not for products.

Whether it applies depends on what you sell and how big you are. A UK café’s website doesn’t need to worry about it. A UK online shop with 15 staff that ships to Ireland and France probably does. Each EU country enforces the Act through its own national law, so this is one to take proper advice on if you’re in scope.

What level should you target?

WCAG 2.2 Level AA. The UK public sector has to meet it, most accessibility audits test against it, and a normal small business website can reach it.

WCAG has three conformance levels, and each includes everything in the level below it:

Level	What it covers	Should you target it?
A	The minimum: text alternatives for images, keyboard access, no content that traps focus	Necessary, but not enough on its own. Leaves out colour contrast, which is the most common failure on the web
AA	Everything in A, plus contrast, resizable text, visible focus, clear labels, consistent navigation, minimum target sizes	Yes. The recognised benchmark
AAA	Everything in AA, plus stricter contrast, sign language for video, reading-level requirements	Not as a whole-site goal. Borrow individual AAA criteria where they’re easy

W3C, which publishes WCAG, is clear on that last row: “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content” (W3C, Understanding Conformance, retrieved 2026-09-26). If someone is selling you a AAA project for a small business site, ask why.

On versions: WCAG 2.2 became a W3C Recommendation on 5 October 2023. It keeps nearly everything from 2.1, removes one obsolete criterion (4.1.1 Parsing) and adds nine new ones, four of them at Level AA (W3C, What’s New in WCAG 2.2, retrieved 2026-09-26). Aim for 2.2. A site that meets 2.2 AA also covers everything that still counts in 2.1 AA.

The handful of fixes that matter most

Six recurring issue types account for 96% of all detected accessibility errors across the top one million homepages. Low-contrast text and missing image alt text lead the list. For most small business sites, fixing these six first gets you most of the practical benefit of a full WCAG project for a fraction of the effort.

Here’s how often each one appeared (WebAIM Million 2026, retrieved 2026-09-26):

Issue	Share of homepages affected	What to do about it
Low-contrast text	83.9%	Check text colours against backgrounds. Body text needs a contrast ratio of at least 4.5:1 at AA. Pale grey text on white is the usual offender
Missing alt text on images	53.1%	Give every meaningful image a short description of what it shows or does. Purely decorative images get empty alt text so screen readers skip them
Missing form input labels	51.0%	Every form field needs a proper label, not just placeholder text that disappears when someone starts typing
Empty links	46.3%	Links that contain only an icon or image, with no text, give a screen reader nothing to announce. Add a text label
Empty buttons	30.6%	Same problem for buttons. The classic example is a hamburger menu or search icon with no accessible name
Missing document language	13.5%	A one-line fix in the page code (lang="en-GB") that tells screen readers which language and pronunciation to use

WCAG is usually explained through its four abstract principles (perceivable, operable, understandable, robust), which is accurate but doesn’t tell a business owner what to do on Monday. The error data does. Automated scanners pick up all six of these issues, so a free tool like WAVE will show you which ones your site has in about a minute.

Two more checks are worth adding, because scanners can’t fully test them:

• Keyboard navigation. Put your mouse aside and press Tab to move through your homepage and contact form. Can you reach every link and button? Can you always see where you are? Can you submit the form? If you get stuck, so does anyone who can’t use a mouse.
• Heading structure. Each page should have one main heading, with sections under it in a logical order. Screen reader users often jump between headings to scan a page, much as sighted visitors skim.

When we ran a basic check on our own homepage while writing the foundational business case for accessibility, it flagged missing alt text and the lack of a single clear main heading. Both are on this list, and both are quick to fix. That’s typical: most small business sites fail on a few common issues that are easy to put right.

None of this counts as a full WCAG 2.2 AA audit, and working through the list doesn’t mean your site “is compliant”. But if you’re deciding where to spend limited time and budget, this is where the evidence says to start. Our Core Web Vitals guide for UK small business websites covers how accessibility fits alongside speed and mobile performance.

What happens if your website isn’t accessible?

For most small businesses, the realistic cost is lost customers, not a court case. But the legal risk is real, so don’t dismiss it.

The commercial cost comes first. The Click-Away Pound Survey found that 69% of disabled internet users have abandoned a website after running into accessibility barriers. Only 8% of them ever contacted the site owner about it. The lost UK retail spend was estimated at £17.1 billion a year (Click-Away Pound Survey, 2019, via AbilityNet, retrieved 2026-09-26). The survey is from 2019 and remains one of the most widely cited UK studies on this. The 8% is the number to notice. Most people who can’t use your site leave without telling you why, so this cost never shows up in a complaint or a review.

The legal route exists. A disabled person who believes a business has failed to make reasonable adjustments can bring a claim in the county court (the sheriff court in Scotland). The normal time limit is six months, less one day, from the act complained of, though the court can extend it if it’s just and equitable (Equality Act 2010, section 118, retrieved 2026-09-26). The best-known example is RNIB’s 2012 legal action against the airline bmibaby over an inaccessible booking site, which RNIB began after repeated attempts to get the problems fixed (The Register, 27 January 2012, retrieved 2026-09-26).

Publicly reported UK website accessibility claims are rare, and the few that are publicly known have generally been resolved without a court judgment. Be wary of scare statistics about lawsuit numbers from other countries: the UK system works differently. But “rare” isn’t “never”. A business that has ignored clear, cheap fixes is in a much weaker position than one that can show it has made reasonable efforts. Working through the fixes above improves your site and gives you evidence that you took the duty seriously.

Do you need an accessibility statement?

If you’re a public sector body, yes. It’s a legal requirement. For most private small businesses, no, but a short statement is good practice and costs very little.

GOV.UK sets out what a public sector statement must cover (GOV.UK, Make your website or app accessible and publish an accessibility statement, last updated 27 September 2024, retrieved 2026-09-26). That structure works well as a template for anyone:

• Whether the site is fully, partially or not compliant with WCAG 2.2 AA.
• What doesn’t work yet, and why, such as older PDFs or an embedded third-party booking widget.
• How someone can get an alternative, for example by phone or email, if they can’t use part of the site.
• How to report a problem, with a named contact route and a commitment to respond.

For a private business, a statement does three useful things. It shows visitors you’ve thought about access. It gives the 8% who do get in touch an easy way to reach you. And it helps show you’re meeting the anticipatory duty, because it records what you’ve checked and what you’re still fixing. Keep it honest: a statement that says “partially compliant, and here’s what we’re working on” is more credible than one claiming full compliance nobody has tested.

The short version

For most UK small businesses, WCAG isn’t a law you’re directly bound by. The Equality Act 2010 is, and its reasonable-adjustments duty covers your website. WCAG 2.2 Level AA is the most practical way to show you’ve met that duty. Public sector bodies face an explicit WCAG 2.2 AA requirement, and their suppliers usually inherit it through contracts. If you sell to EU consumers, check the European Accessibility Act too, unless you’re a microenterprise that only provides services.

You don’t need to tackle all of WCAG at once. Fix contrast, alt text, form labels, empty links and buttons, and page language first. Then test your keyboard navigation and heading structure, and publish a short, honest accessibility statement.

If you’re commissioning a new site, ask whether accessibility is included as standard. Building it in from the start is far cheaper than retrofitting it later. And if you arrived here without the background, start with why accessibility matters for UK small businesses.