No UK law tells a private business that its website must meet a named technical standard. But the Equality Act 2010 requires businesses that provide services to the public to make reasonable adjustments for disabled people, the duty applies to services provided on a website, and it is anticipatory: you are expected to think about barriers before a disabled customer meets them. Public sector bodies have a stricter rule, which names WCAG 2.2 AA. For a business, that same standard is, in our view, the most practical way to show you have taken reasonable steps. This guide explains what the law says, where B2B firms are affected, and a plan you can follow.
This guide is general information, not legal advice. If you’re unsure what applies to your business, check with an adviser.
Key takeaways
- The Equality Act 2010 (in Great Britain) and the Disability Discrimination Act 1995 (in Northern Ireland) require service providers to make reasonable adjustments, and the EHRC’s 2026 code says this covers services on a website.
- The duty is anticipatory: you consider disabled people generally, not only those who have already asked.
- For B2B firms, the duty can also reach your recruitment pages, and public sector clients have their own WCAG 2.2 AA duty.
- If you sell online to consumers in the EU, the European Accessibility Act may also apply to you.
- WCAG 2.2 AA is the benchmark: test against it, fix the problems, offer other ways to reach you, and keep checking.
What the law says
Service providers must not discriminate
Section 29 of the Equality Act 2010 applies to “A person (a “service-provider”) concerned with the provision of a service to the public or a section of the public (for payment or not)”. It says a service provider must not discriminate against a person who needs the service, and that “A duty to make reasonable adjustments applies to” a service provider.
The duty to make reasonable adjustments
Section 20 sets out the duty as three requirements. In short, where a practice, a physical feature or the lack of an auxiliary aid puts a disabled person at “a substantial disadvantage” compared with people who are not disabled, the service provider must “take such steps as it is reasonable to have to take” to avoid that disadvantage. Two details matter for websites:
- Where the requirement relates to information, the reasonable steps “include steps for ensuring that in the circumstances concerned the information is provided in an accessible format” (section 20(6)).
- You can’t pass the cost on: the Act says the service provider is not entitled to require a disabled person “to pay to any extent A’s costs of complying with the duty” (section 20(7)).
It covers your website
The Equality and Human Rights Commission’s Code of Practice for services, public functions and associations explains how the Commission reads the Act. GOV.UK says the code “came into force on 5th August 2026” and that the 2011 code was revoked on the same date. The code says Part 3 of the Act applies to service providers “whether in the private, public or voluntary sectors” and adds: “The obligation also applies to the provision of services on a website (section 29).”
The code gives an example of a legal services firm whose website “has all its text embedded within graphics”, so people with a visual impairment “cannot change the font size or apply text-to-speech recognition software”. The code says this gives rise to an obligation to make a reasonable adjustment and will also be indirect disability discrimination unless the provider can justify it.
Northern Ireland
GOV.UK says “All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010 or the Disability Discrimination Act 1995 (in Northern Ireland).” The Equality Commission for Northern Ireland is the body to check with there.
What happens if someone complains
In Great Britain, a claim about services is heard in the county court or, in Scotland, by the sheriff (section 114). It must normally be brought within “the period of 6 months starting with the date of the act to which the claim relates”, or such other period as the court thinks “just and equitable” (section 118). Damages “may include compensation for injured feelings” (section 119(4)). A customer who can’t use your site may also simply go elsewhere, which is the commercial reason to get this right.
The duty is anticipatory
This is the point many businesses miss. For services, Schedule 2 to the Act says the reference to a disabled person in the duty “is to disabled persons generally”. The EHRC code explains what that means: service providers “must proactively consider the barriers that disabled people could face and take action to address those barriers”, and this “should happen before an individual disabled person seeks to use a service”.
The code also says the duty “applies regardless of whether the service provider … knows that a particular person is disabled or whether it currently has, for example, disabled customers”. So “nobody has complained” is not an answer. Neither is a one-off fix: the code calls it “a continuing duty” that should be kept “under regular review”.
The code also says service providers “are not expected to anticipate the needs of every individual”. They are required “to think about and take reasonable steps to overcome barriers that may impede people with different kinds of disability”. The code’s examples include people with dementia, mental health conditions or mobility impairments. For a website, think also about people who are blind or have low vision, people who are deaf, and people who use a keyboard, switch or voice control instead of a mouse.
What “reasonable” means
The Act doesn’t list factors. The EHRC code says what is reasonable “depends on all the circumstances of the case” and gives examples of factors that might be considered, including:
- “whether taking any particular steps would be effective in overcoming the substantial disadvantage”
- “the extent to which it is practicable” to take the steps
- “the financial and other costs of making the adjustment”
- “the extent of the financial and other resources” of the service provider
- “the amount of any resources already spent on making adjustments”
It adds that it is “more likely to be reasonable” for a provider with substantial resources to make an adjustment with a significant cost, and that in the end reasonableness is “an objective one for the courts to determine”. What that means for your firm is a judgement on your own facts. Our suggestion, which is not a legal test: fix first the barriers that stop people using your key pages, such as forms, navigation, contrast and documents, and keep a dated plan for the rest.
Where B2B firms are affected
Services to the public or a section of the public
Part 3 of the Act is about services “to the public or a section of the public”. If any of your services are offered to the public, such as homeowners, tenants or members of the public booking a consultation, the duty plainly applies to the parts of your website they use. Whether a particular business-to-business arrangement counts as a service to “a section of the public” depends on the facts, and that is a question for legal advice. If you serve both kinds of client through one site, the same pages need to work for everyone.
Recruitment
Your careers pages and application forms are covered by a different part of the Act. Section 39 says an employer must not discriminate against a person “in the arrangements A makes for deciding to whom to offer employment”, and a duty to make reasonable adjustments applies to employers. That duty is not anticipatory in the same way: Schedule 8 says it doesn’t arise if the employer doesn’t know, and couldn’t reasonably be expected to know, that a disabled person is or may be an applicant. Even so, an online application form that some disabled people can’t complete is a barrier you can remove in advance, and offering another way to apply is simple.
Public sector clients
If you design, build or supply websites, apps or documents for a public body, that body is the one bound by the public sector accessibility rules below, and its duty is to meet WCAG 2.2 AA. Check what the contract asks of you.
Selling into the EU
The European Accessibility Act (Directive (EU) 2019/882) is EU law, not UK law, but it can reach UK firms that trade with EU consumers. It covers “e-commerce services”, which it defines as services provided at a distance “at the individual request of a consumer with a view to concluding a consumer contract”, and EU countries were required to apply their national rules “from 28 June 2025”. It exempts “Microenterprises providing services”, defined as an enterprise “which employs fewer than 10 persons” and has an annual turnover or balance sheet total not exceeding EUR 2 million. The rules that bite are each EU country’s own national law, so if you sell online to EU consumers, take advice for the countries you sell into.
The public sector rules
The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 apply to public sector bodies, which GOV.UK’s guidance describes as “central government and local government organisations” and “some charities and other non-government organisations”. GOV.UK says a public sector website or app meets the legal requirements if it meets “the Web Content Accessibility Guidelines (WCAG) 2.2 AA accessibility standard” and publishes an accessibility statement. The regulations allow a body to claim a “disproportionate burden” for some content, but only after an assessment, and it has to say so in its statement.
Even organisations that are exempt from those regulations, GOV.UK says, are “still legally required to make reasonable adjustments for disabled people when they’re needed”. In Great Britain the EHRC enforces the requirement, and in Northern Ireland the Equality Commission for Northern Ireland does.
WCAG 2.2 AA in plain English
The Web Content Accessibility Guidelines are published by the W3C, the body that develops web standards. The W3C says “WCAG 2.2 was published as a “W3C Recommendation” web standard on 5 October 2023″, and in October 2025 it announced that WCAG 2.2 “is now an approved International Organization for Standardization (ISO) standard: ISO/IEC 40500:2025”.
WCAG has three levels: A, AA and AAA. The W3C says that for level AA conformance a page “satisfies all the Level A and Level AA success criteria”, and AA is the level GOV.UK names for public bodies. GOV.UK sums up its principles as making a site “perceivable, operable, understandable and robust”.
What changed in 2.2
The W3C’s page on what’s new in WCAG 2.2 says “WCAG 2.2 provides 9 additional success criteria since WCAG 2.1”. Six of them are at level A or AA, so they are part of a WCAG 2.2 AA target:
- Focus Not Obscured (Minimum), AA. When someone moves through the page with a keyboard, the item they are on mustn’t be completely hidden, for example by a sticky header or a cookie banner.
- Dragging Movements, AA. Anything that needs dragging, such as a slider or a map, must also work with a single tap or click.
- Target Size (Minimum), AA. The W3C says “The size of the target for pointer inputs is at least 24 by 24 CSS pixels”, with some exceptions, such as enough space around a smaller target.
- Consistent Help, A. If help, such as contact details or a chat link, appears on several pages, it should be in the same place on each.
- Redundant Entry, A. Don’t make people type the same information twice in one process, unless there’s a good reason.
- Accessible Authentication (Minimum), AA. In the W3C’s words: “Don’t make people solve, recall, or transcribe something to log in.” This matters for client portals and any other sign-in. The criterion has exceptions, such as recognising objects, so read the W3C’s detail before you choose a sign-in method.
The W3C also says one older criterion, “4.1.1 Parsing is obsolete and removed from WCAG 2.2.”
Where business websites usually fall down
GOV.UK’s guidance for public bodies lists common problems as “websites that are not easy to use on a mobile or cannot be navigated using a keyboard, inaccessible PDF forms that cannot be read out on screen readers, and poor colour contrast”. B2B websites tend to add a few of their own:
- PDF documents. Capability statements, policies, method statements and brochures are often scanned images or untagged PDFs that a screen reader can’t read. Publish key information as web pages, and make PDFs properly tagged.
- Case studies as pictures. Project facts set into an image are invisible to screen readers and search engines. Put the facts in text, and give each photo true alt text.
- Enquiry forms. Missing labels, error messages that only show in red, time limits and puzzle CAPTCHAs can stop people sending the enquiry you want.
- Pale text and thin fonts. Grey on white can look refined and be hard to read. The W3C’s Easy Checks give the minimum as “a contrast ratio of at least 4.5:1 for normal-size text”.
- Carousels and auto-playing video. Moving content that can’t be paused, and video without captions.
- Third-party tools. Embedded booking, chat, maps and job boards bring their own barriers. Ask the supplier about accessibility before you add them.
A plan you can follow
- Pick the journeys that matter. For most firms: finding a service, reading a case study, contacting you, downloading a document, and applying for a job.
- Test against WCAG 2.2 AA. Use automated tools to find the obvious issues, then test by hand. The W3C is clear on the limits: tools “can not determine accessibility, they can only assist in doing so”. Keyboard-only use, 200% zoom and a screen reader check catch problems no scanner will.
- Fix in order of harm. Anything that stops someone completing a journey comes first: forms, navigation, sign-in. Then contrast, headings, alt text and documents.
- Offer other ways in. Show a phone number and email address on every page, and say you can provide documents in other formats on request. Section 20(6) of the Act is about information in an accessible format, so answer those requests promptly.
- Consider an accessibility statement. Only public sector bodies must publish one, but a short page saying what standard you aim for, what you know isn’t right yet and how to get help is useful for everyone. GOV.UK’s sample statement for public bodies is a good model.
- Put it in your supplier contracts. Ask your web designer or agency to build to WCAG 2.2 AA and to show test results, and include the same requirement when you add third-party tools.
- Keep checking. Every new page, PDF and photo can undo good work. Re-test the key journeys after changes, and at least once a year.
If you want to start today, our eight quick accessibility checks take an afternoon and need no tools.
What to ask your web designer
- Will the site be built and tested to WCAG 2.2 AA, and will you show us the results?
- Which tests are automated, and which are done by hand with a keyboard and a screen reader?
- Do the theme’s colours pass contrast, including buttons, links and text on photos?
- Will forms have visible labels, clear error messages and no puzzle CAPTCHA?
- How will our team keep it accessible when we add pages, documents and images?
- Which third-party tools on the site have their own accessibility issues?
Be wary of anything sold as a one-click fix. In our view, the W3C’s point about testing tools applies to plugins and overlays too: they can help, but they can’t make a site accessible on their own.
Common questions
Is WCAG 2.2 AA a legal requirement for our company?
For a private business, no law names it. The legal duty is to make reasonable adjustments under the Equality Act 2010. WCAG 2.2 AA is the standard public bodies must meet and, in our view, the clearest way to show you have taken reasonable steps.
Do we have to publish an accessibility statement?
GOV.UK says “Public sector bodies must publish an accessibility statement and review it regularly.” Private businesses don’t have to, but a short, honest one helps visitors and shows your intent.
Our clients are all businesses. Does the Act still apply?
It may. It depends whether your services are offered to the public or a section of the public, and your recruitment pages are covered by the employment part of the Act either way. Take advice on your own arrangements.
Do PDFs count?
They can. If a document is part of how you provide a service, a disabled person who can’t read it may be at a substantial disadvantage. Publish the key information as web pages too, and offer other formats on request.
Our site is old. Do we need a new one?
Not necessarily. Many barriers can be fixed in an existing site. If the theme or builder makes fixes impractical, plan the rebuild with WCAG 2.2 AA in the brief.
Free help
- What your business website must show by law (UK)
- How to choose a web designer (UK)
- Website redesign: when to do it and what it costs (UK)
Where Hintling Studio fits
We’re Hintling Studio, an independent web design studio registered in London. Every package is built with WCAG 2.2 AA as the target, and the dashboard Site guide, with 8 short how-to videos, shows you how to edit your own pages. See what’s in each package, or tell us about your business.
Sources checked on 17 November 2026: legislation.gov.uk, GOV.UK, the EHRC code of practice published on GOV.UK, and the W3C. Hintling Studio is not connected with the Equality and Human Rights Commission, the Equality Commission for Northern Ireland, GOV.UK, the W3C or the European Commission.
