Short answer: if you provide goods or services to the public in the UK, the Equality Act 2010 (the Disability Discrimination Act 1995 in Northern Ireland) expects you to make reasonable adjustments so disabled people can use your service, and that includes website accessibility. The law doesn’t name a technical standard for private businesses, but the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA are the accepted benchmark. Most of the important fixes are simple and cheap if they are built in from the start.
Around one in four people in the UK is disabled, and many more have temporary or situational difficulties: a broken arm, bright sunlight on a phone screen, a slow connection or simply ageing eyes. An accessible website is easier for all of them to use. It also tends to be faster, clearer and better understood by search engines. This guide explains what the rules say, what to check and how to publish an accessibility statement.
This is general guidance for small businesses, not legal advice.
What the law says
Equality Act 2010
The Equality Act applies to service providers in England, Scotland and Wales, from large companies to sole traders. A website is treated as part of the service you provide. The duty to make reasonable adjustments is “anticipatory”, which means you are expected to think about disabled users in advance, not wait for someone to complain. What is reasonable depends on things like the size of your business and the cost of the change. Northern Ireland has similar duties under the Disability Discrimination Act 1995.
The Act does not say “your website must meet WCAG 2.2 AA”. In practice, though, WCAG is the standard that courts, the Equality and Human Rights Commission and accessibility specialists use to judge whether a site is reasonably accessible.
Public sector rules
Public sector bodies, such as councils, schools and NHS organisations, have stricter rules under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. They must meet WCAG 2.2 AA and publish an accessibility statement. If you supply websites or services to public bodies, expect these requirements to appear in your contract. The government’s guide to accessibility requirements for public sector websites explains them in detail.
The European Accessibility Act
The European Accessibility Act has applied since 28 June 2025. It is EU law, not UK law, so a business that only serves UK customers is not covered. It can apply to UK businesses that sell certain products or services, including online shops, to consumers in the EU. Microenterprises providing services, meaning fewer than 10 staff and an annual turnover or balance sheet of no more than €2 million, are exempt from the service requirements. If you sell online to EU customers and are larger than that, take specific advice.
WCAG in plain English
The Web Content Accessibility Guidelines are published by the W3C. They are built on four principles: content must be perceivable (people can see or hear it), operable (people can use it with a mouse, keyboard, touch or voice), understandable (clear language and predictable behaviour) and robust (works with assistive technology such as screen readers). Level A is the minimum, AA is the usual target and AAA is the highest level, rarely required for whole sites.
The checks that matter most on a small business site
You don’t need to read the full guidelines to fix the most common problems. On the sites we review, these cause most of the trouble:
- Colour contrast. Pale grey text on white, or white text on a light brand colour, is hard to read for many people. Normal-size text needs a contrast ratio of at least 4.5:1 for AA.
- Alt text on images. Every meaningful image needs a short description for screen reader users. Decorative images should have empty alt text so they are skipped.
- Keyboard use. Try using your site with only the Tab and Enter keys. Can you reach the menu, open it, fill in the form and press send? Can you see where you are on the page?
- Headings in order. One H1 per page, then H2s and H3s in a logical order. Screen reader users jump between headings to find what they need.
- Descriptive links and buttons. “Read our pricing guide” works out of context. “Click here” does not.
- Forms with labels. Every field needs a visible label, not just placeholder text that disappears when you type. Error messages should say what went wrong and how to fix it.
- Text that resizes. The page should still work when someone zooms to 200%, and on a phone held either way.
- Video and audio. Add captions to videos and avoid sound or video that plays automatically.
- Touch targets. Buttons and links should be big enough to tap easily. WCAG 2.2 added a minimum size for this.
- Clear language. Short sentences, plain words and no unexplained jargon help people with cognitive and learning disabilities, and everyone else too.
How to test your own website
- Run an automated check. Free tools such as WAVE or Google Lighthouse (built into Chrome) flag missing alt text, low contrast and missing labels. They catch only part of the problems, so treat them as a starting point.
- Do the keyboard test described above on your main pages and your contact form.
- Zoom to 200% and check nothing overlaps or disappears.
- Try a screen reader. VoiceOver is built into iPhones and Macs, and NVDA is free for Windows. Even ten minutes is eye-opening.
- Ask real users. If you have customers who use assistive technology, their feedback is worth more than any tool.
A word on accessibility overlays
You may see plug-ins that promise to make any website accessible with one line of code, usually by adding a toolbar. They can be useful for a few personal preferences, but they don’t fix the underlying problems such as missing labels, poor heading structure or keyboard traps, and many disabled users find them get in the way. Fixing the website itself is the reliable route.
Writing an accessibility statement
An accessibility statement is a page that explains how accessible your website is and how people can get help. It’s required for public sector sites. For private businesses it isn’t a legal requirement, but it’s good practice and a clear signal that you take the subject seriously. A simple statement covers:
- Which website the statement applies to.
- The standard you aim for, for example WCAG 2.2 AA.
- How accessible the site is today, including any known problems and plans to fix them.
- How people can request information in another format or report a problem, with an email address and the time you’ll take to reply.
- The date the statement was prepared and last reviewed.
Keep it honest. Saying “our older PDF price lists are not fully accessible, so please email us and we’ll send the information another way” is better than claiming full compliance you can’t back up. Link to the statement from your footer, next to your privacy and cookie policies.
Accessibility and SEO go together
Many accessibility fixes also help with search. Clear headings help Google understand your page structure. Alt text helps images appear in image search. Descriptive link text tells search engines what the linked page is about. Fast, well-structured pages are easier to crawl. And content written in plain language is easier for AI search tools to quote accurately.
Building it in from the start
Accessibility is far cheaper to get right during a build than to fix afterwards. When we build a website, we choose colours with enough contrast, use one H1 per page with a logical heading structure, label every form field, add alt text to images, make menus and forms work with a keyboard and size buttons for touch. Our web design service and website redesign service both include these basics as standard. If you’d like us to look at your current site, send us a message through our contact page.
For other legal pages your site needs, see our small business website checklist.
Frequently asked questions
Is website accessibility a legal requirement for UK businesses?
Yes, in the sense that the Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, and a website is part of your service. There is no law naming a specific WCAG level for private businesses, but WCAG 2.2 AA is the recognised benchmark.
Do small businesses need an accessibility statement?
Not by law, unless you are a public sector body. It is still good practice, it costs little to write and it gives people a clear way to ask for help.
Does the European Accessibility Act apply to UK businesses?
Only if you sell covered products or services, such as e-commerce, to consumers in the EU. Businesses that only serve UK customers are not covered, and microenterprises providing services are exempt from the service requirements.
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2, published in 2023, keeps almost everything from 2.1 and adds new checks, including clearer focus indicators, minimum target sizes for buttons and easier authentication. Building to 2.2 AA covers 2.1 AA as well.
How much does it cost to make a website accessible?
For a new small business website, built properly, accessibility adds very little to the cost. Fixing an existing site depends on how it was built, ranging from a few hours of changes to a rebuild for very old sites.