If you run a website or app in the UK, at least one accessibility law already applies to you. Which ones, and how strictly, depends on who you are and who you sell to. This is a plain-English overview to help you work out where you stand. It isn’t legal advice; for a specific situation, speak to a solicitor.
The short version
| You are… | What applies | The standard to aim for |
|---|---|---|
| Any UK business or charity providing a service | Equality Act 2010 | WCAG 2.2 AA is the accepted benchmark |
| A UK public sector body | Public sector accessibility regulations (2018), plus the Equality Act | WCAG 2.2 AA, and a published accessibility statement |
| A business selling to consumers in the EU | European Accessibility Act, since 28 June 2025, plus the Equality Act | EN 301 549, which follows WCAG AA |
The Equality Act 2010: everyone
The Equality Act requires anyone providing goods, facilities or services to the public to make reasonable adjustments so disabled people aren’t put at a substantial disadvantage. A website or app is part of your service, so it’s covered.
Three things are worth knowing:
- The duty looks ahead. You’re expected to think about disabled users’ needs in advance, not wait for a complaint.
- “Reasonable” depends on you. What’s expected of a large retailer is more than what’s expected of a sole trader, taking into account cost, practicality and size.
- You can’t charge for it. Adjustments can’t be passed on as a cost to the disabled person.
The Act doesn’t name a technical standard, but if a claim is made, meeting the Web Content Accessibility Guidelines (WCAG) at level AA is the clearest way to show you’ve done what’s reasonable. Taylor Wessing’s overview covers the detail.
Public sector bodies
The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to central and local government, the NHS, schools, universities and many other public bodies. They must meet WCAG 2.2 AA, publish an accessibility statement saying what doesn’t yet meet it, and keep that statement up to date. The Government Digital Service monitors sites and can ask for fixes. Some organisations are exempt or partly exempt, and a “disproportionate burden” argument is possible but must be justified.
If you’re a supplier building for the public sector, these rules become your requirements too.
The European Accessibility Act: if you sell into the EU
The European Accessibility Act (EAA) has applied since 28 June 2025. It covers certain products and services sold to consumers in the EU, wherever the business is based, so UK companies selling into the EU can be caught. Services in scope include:
- e-commerce sites and apps
- online banking and some financial services
- e-books, and passenger transport booking and information
- some communication and audio-visual media services
Microenterprises providing services are exempt: fewer than 10 staff and an annual turnover or balance sheet of no more than €2 million. Each EU country sets its own enforcement and penalties. The technical standard is EN 301 549, which builds on WCAG AA. iubenda’s guide has a fuller list of what’s in scope.
Many businesses meet the EAA for every market rather than running two versions, which also takes care of the Equality Act at home.
What WCAG AA actually asks for
In practice, most of it is good design:
- Text with enough contrast against its background, in every theme.
- Everything usable with a keyboard, with a visible focus indicator.
- Images with meaningful alternative text.
- Forms with proper labels and clear error messages.
- Pages that still work when zoomed to 200% or 400%, or on a narrow screen.
- Video with captions.
- No content that flashes or moves without a way to stop it.
The cheapest time to do all of this is from the first design, not after launch. We wrote about why in accessibility isn’t a checklist, and it’s how we built this site and our design system, Somnia DS.
Where to start
- Check what applies. Public sector? Selling to EU consumers? More than 10 staff?
- Test what you have. Automated tools catch only a minority of issues; checking with a keyboard and a screen reader finds much of the rest.
- Fix the components, not the pages. If the button is accessible, every page that uses it is. A design system makes this stick.
- Publish an accessibility statement. Required for the public sector, and good practice for everyone: say what you meet, what you don’t yet, and how to get help.
- Keep it up. Accessibility slips with every new feature unless it’s part of how you design and test.
Not sure where your site or app stands? Get in touch. We design to WCAG 2.2 AA from the first prototype and can review what you have.
← Back to all insights