Answer first: If you sell to the public in Great Britain, the Equality Act 2010 already covers your website. Service providers must not discriminate against disabled people. Where the way you provide information puts a disabled person at a substantial disadvantage, you must take reasonable steps to avoid it, and those steps include providing the information in an accessible format (Equality Act 2010, section 20). The law doesn't name a technical standard for private businesses. In practice, the yardstick is the Web Content Accessibility Guidelines (WCAG) 2.2, which UK public sector sites must meet at level AA. Start with W3C's quick checks: page titles, alt text, headings, colour contrast, zoom, keyboard use, forms and video captions. Then fix the pages people use to contact you or buy from you first.

What the law asks of a small business

The Equality Act 2010 applies to anyone providing a service to the public in England, Scotland and Wales, whether or not they charge for it (section 29). Northern Ireland is covered by the Disability Discrimination Act 1995 instead. Three points matter for a website:

  • The duty to make reasonable adjustments. Where a "provision, criterion or practice" puts disabled people at a substantial disadvantage, you must take reasonable steps to avoid it. For information, that includes providing it in an accessible format (section 20).
  • The duty is anticipatory. The Equality and Human Rights Commission's Code of Practice for services, published in August 2026, says service providers should think ahead about the barriers disabled people are likely to face, rather than waiting for a complaint (EHRC Code of Practice, chapter 5).
  • Websites appear in the Code's own examples. One describes a legal services firm whose website text is all embedded in images. Visually impaired users can't resize it or use text-to-speech software, so the firm has to make a reasonable adjustment, and the Code says the practice will be indirect disability discrimination unless the firm can justify it.

GOV.UK's guidance for public sector bodies makes the same point from the other direction. It says all UK service providers have a legal duty to make reasonable adjustments, and that even organisations exempt from the public sector rules must still do so when needed, for example by providing information in a more accessible format (GOV.UK, accessibility requirements for public sector bodies).

The stricter Public Sector Bodies Accessibility Regulations apply only to public sector bodies and some publicly funded organisations. Those bodies must meet WCAG 2.2 AA and publish an accessibility statement. A private small business isn't bound by those rules, but they are the clearest published picture of what an "accessible website" means in the UK.

WCAG 2.2 in plain English

WCAG is published by the World Wide Web Consortium (W3C). Version 2.2 was published in October 2023, and W3C notes it has since been approved as the international standard ISO/IEC 40500:2025 (W3C, WCAG overview). The guidelines are grouped under four principles:

  • Perceivable. People can see or hear the content, or get it another way, for example alt text or captions.
  • Operable. People can use the site with a keyboard, a switch or voice control, not only a mouse.
  • Understandable. Content and forms are clear and behave predictably.
  • Robust. The site works with assistive technology such as screen readers.

Each success criterion is graded A, AA or AAA. Level AA is the usual target. W3C says content that meets WCAG 2.2 also meets 2.1 and 2.0.

If you sell into the EU, W3C notes that the European Accessibility Act is supported through WCAG and the EU standard EN 301 549. That's another reason to aim for 2.2 AA rather than an older version.

Quick checks you can run this afternoon

W3C publishes a set of "Easy Checks" that anyone can run without specialist tools (W3C, Easy Checks). W3C says they cover just a few accessibility issues, and a page can pass them and still have significant barriers, but they are a good first look. Try them on your homepage, your main service page and your contact or checkout page.

  1. Page titles. Each page should have a short, distinct title that says what the page is. "Home" on every tab doesn't help anyone.
  2. Image text alternatives. Informative images need alt text describing what matters. Decorative images should have empty alt text (alt="") so screen readers skip them. Text should never be baked into an image, which is the problem in the EHRC example above.
  3. Headings. Pages should use real headings in a logical order. Text that is simply bold and large isn't a heading to a screen reader.
  4. Colour contrast. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal-size text. Pale grey text on white usually fails.
  5. Zoom to 200 per cent. At 200 per cent zoom, text should still be readable without content disappearing or the page needing horizontal scrolling.
  6. Keyboard only. Put the mouse aside and press Tab. You should be able to reach every link, button and form field, always see where the focus is, and never get stuck. Check cookie banners and chat widgets too, because they sit on top of every page. Our guide to cookie banners and privacy notices covers what the banner must say. Make sure it can also be used with a keyboard.
  7. Forms. Every field needs a visible label. Error messages should say what went wrong and how to fix it, not just turn the box red.
  8. Moving content. Anything that moves for more than five seconds, such as a carousel or auto-playing video, needs a way to pause, stop or hide it. Nothing should flash more than three times a second.
  9. Video and audio. Videos need accurate captions. W3C notes that automatic captions alone are not enough. Audio content needs a transcript.

Write down what fails and where. That list is your starting plan.

Fixing it without a full rebuild

Most fixes on small business sites are content and template changes, not a new website:

  • Start with the money pages. Fix your contact form, quote request, booking or checkout before the blog. If a disabled customer can't get in touch, nothing else on the site matters to them.
  • Fix templates, not pages. Contrast, heading structure, focus styles and form labels usually live in a theme or template. Fix them once and every page improves.
  • Make text real text. Replace image-based banners, price lists and menus with HTML text.
  • Give people another way in. Offer an email address and an accessible alternative to complex forms, and say on your contact page that you will provide information in other formats on request. This is the "reasonable adjustment" route the law describes.
  • Write a short accessibility statement. Private businesses don't have to publish one, but a page explaining what you have checked, what you know still needs work and how to ask for help is good practice. It is the format the public sector uses.
  • Re-check after changes. A new plugin, theme update or page builder block can undo earlier fixes. Run the quick checks again whenever the site changes.

If your site is due for a refresh anyway, include accessibility in the brief from the start. Our guide to small business website redesign covers planning the rest of the project, and our website service is where to start if you'd like help.

FAQ

There is no specific website accessibility regulation for private businesses. However, the Equality Act 2010 applies to services provided to the public in Great Britain, including through a website. It requires reasonable adjustments, including providing information in an accessible format.

Which WCAG level should a small business aim for?

WCAG 2.2 level AA. It is the standard UK public sector websites must meet, and W3C says content that meets 2.2 also meets the earlier 2.1 and 2.0.

Do I need an accessibility statement?

Public sector bodies must publish one. For a private business it isn't required, but a short statement explaining what you've checked and how people can ask for information in another format is good practice.

Are automatic captions good enough for my videos?

W3C's Easy Checks say automatically generated captions are not sufficient on their own. Check and correct them before relying on them.

Can an accessibility overlay or plugin make my site compliant?

No single plugin replaces fixing the underlying pages. In April 2025 the US Federal Trade Commission approved a final order requiring accessiBe to pay $1 million over claims that its AI plug-in could make any website WCAG-compliant. W3C's checks look at the content itself, such as headings, alt text, labels, contrast and keyboard access, and those need fixing in the site's templates and content.

Sources