Yes, UK websites carry legal accessibility obligations: public sector bodies must meet the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 and publish an accessibility statement, while every business has a duty under the Equality Act 2010 to make reasonable adjustments for disabled customers. The practical benchmark for both is WCAG 2.2 AA.
TL;DR:
- Most UK public sector websites must meet WCAG 2.2 AA standards and publish accessibility statements, with compliance deadlines from 2020 onwards.
- Private businesses are not legally bound by WCAG but must make reasonable adjustments under the Equality Act 2010, especially for small or low-cost fixes.
- Sampling specific web pages and combining automated scans with expert testing and user feedback is recommended for effective accessibility audits.
- High-impact, low-cost fixes such as adding alt text, improving keyboard navigation, and ensuring proper color contrast can significantly improve accessibility.
- Enforcement is carried out by the Government Digital Service for public sector sites and the EHRC for private organizations, with complaints escalated through published contact methods.
Table of Contents
- Who the rules apply to: public sector, private businesses and exemptions
- Legal framework: key legislation, regulations and enforcing bodies
- WCAG 2.2 AA: what ‘perceivable, operable, understandable, robust’ actually means
- Accessibility statements: what to publish and how to use the model statement
- How to check and make a plan: sampling, audits, testing and fixing
- Reasonable adjustments, disproportionate burden and practical affordability for SMEs
- Enforcement, complaints and next steps if someone reports a failure
- High-impact checklist for UK website owners this month
- Why accessibility is good business, not just good compliance
- How Fylde Digital can help with accessible, compliant websites
- FAQ
- Sources
Who the rules apply to: public sector, private businesses and exemptions
The 2018 regulations cover public sector bodies: government departments, councils, NHS trusts, schools and other publicly funded organisations. These bodies must meet WCAG 2.2 AA and publish an accessibility statement covering every website and mobile app they run.
Some bodies get exemptions or partial exemptions:
- Charities and non-profits that rely mainly on volunteers for digital services may qualify for exemption from some requirements.
- Broadcasters are generally exempt where the regulations would duplicate existing broadcasting rules.
- Older content, such as archived documents published before the regulations took effect, can often stay unchanged.
- Schools and colleges get a partial exemption covering parts of their websites not essential to administrative functions.
Private businesses sit outside the 2018 regulations but are never free of accessibility duties. The Equality Act 2010 requires every service provider, large or small, to make reasonable adjustments so disabled customers can use their services, and that duty extends to websites and apps.
Legal framework: key legislation, regulations and enforcing bodies
Two pieces of law sit behind every UK accessibility decision. The Equality Act 2010 places a general duty on service providers to make reasonable adjustments for disabled people, and that duty is ongoing: businesses are expected to anticipate likely barriers rather than wait for a complaint before acting, according to EHRC guidance.
Sitting alongside it, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 set specific, measurable duties for public sector digital services: meet WCAG 2.2 AA and publish a conformant accessibility statement. The regulations came into force on 23 September 2018, with existing websites required to comply by 23 September 2020, according to GOV.UK.
Two bodies do the watching. The Government Digital Service monitors public sector compliance by examining a sample of sites each year, while the Equality and Human Rights Commission, alongside the Equality Commission for Northern Ireland, can enforce against public bodies that miss WCAG targets and against any organisation, public or private, that fails its reasonable adjustments duty under the Equality Act, according to the 2018 regulations.
WCAG 2.2 AA: what ‘perceivable, operable, understandable, robust’ actually means
WCAG organises accessibility around four principles. Content must be perceivable, meaning people can take it in regardless of how they browse, through alt text for images or captions for video. It must be operable, so every function works from a keyboard alone, not just a mouse or touchscreen. It must be understandable, with plain language, consistent navigation and clear error messages on forms. Finally, it must be robust, built on clean code that works reliably across browsers and assistive technologies such as screen readers.
In practice, meeting WCAG 2.2 AA means checking things such as: every image carries meaningful alt text, every interactive element is reachable and usable by keyboard, text has enough colour contrast against its background, headings follow a logical order, and form fields carry clear labels rather than placeholder text alone. GOV.UK’s service manual sets the expectation that public services meet both A and AA level requirements from early development through to public release, and that same standard has become the reference point most private sector website owners use too.
Accessibility statements: what to publish and how to use the model statement
A proper accessibility statement does more than declare good intentions. GOV.UK’s model accessibility statement sets out what it needs to include:
- Current conformance status against WCAG 2.2 AA, including any known gaps.
- Details of any exemptions claimed and the reasoning behind them.
- A working contact method for reporting accessibility problems.
- Alternative formats or routes to the same information where parts of the site fall short.
- A link to the relevant enforcement body for unresolved complaints.
Publish the statement as an accessible HTML page rather than a PDF, link to it clearly from the site footer, and review it at least once a year. Where something has been assessed as a disproportionate burden to fix, the statement should document that assessment and explain what remains inaccessible and why.
How to check and make a plan: sampling, audits, testing and fixing
You do not need to test every page to get a clear picture. GOV.UK guidance confirms that sampling a representative set of pages is an accepted approach: pick your homepage, a core transaction or enquiry form, a content-heavy page and anywhere customers are likely to get stuck.
A sound process runs in stages:
- Run automated scans across your sample to catch obvious issues like missing alt text or poor contrast.
- Bring in manual expert testing for anything automated tools cannot judge, such as whether reading order makes sense.
- Test with disabled users where possible, since lived experience surfaces problems that audits alone miss.
- Sort findings into tiers: quick wins you can fix this week, medium tasks for the next sprint, and major remediation that needs budget and planning.
- Brief any external audit clearly, specifying WCAG 2.2 AA as the target and asking for evidence suitable for your accessibility statement.
GOV.UK recommends combining automated tools with expert manual review and genuine user testing for the most reliable evidence of conformance, rather than relying on any single method alone.
Pro Tip: Keep screenshots, ticket records and dated fix logs for every issue you resolve. That evidence becomes the backbone of your accessibility statement and your answer if a complaint ever arrives.
Our audit checklist covers the same ground in more depth if you want a structured starting point.
Reasonable adjustments, disproportionate burden and practical affordability for SMEs
‘Reasonable’ under the Equality Act weighs the size of your organisation, the cost of the adjustment and the practical impact on disabled customers. A one-person shop and a national retailer are not held to the same bar.
Where a fix would genuinely be a disproportionate burden, EHRC guidance supports documenting that assessment rather than ignoring the issue, and signalling it honestly in your accessibility statement if you publish one.
For most SMEs, the highest-value fixes cost little: writing meaningful alt text, fixing colour contrast, labelling form fields properly and making sure every function works by keyboard. None of these need a rebuild.
Enforcement, complaints and next steps if someone reports a failure
Anyone who hits an accessibility barrier can usually report it directly through the contact method listed in your accessibility statement. If that gets no response, public sector users can escalate to the enforcement body named in the statement.
The Government Digital Service monitors public sector sites through annual sampling, while the Equality and Human Rights Commission and the Equality Commission for Northern Ireland can take enforcement action for Equality Act breaches, according to the regulations. When you receive a complaint, acknowledge it promptly, investigate the specific barrier raised, and set a realistic timetable for a fix rather than letting it sit unanswered.
High-impact checklist for UK website owners this month
A handful of fixes account for most of the everyday friction disabled visitors hit on business websites. GOV.UK guidance explicitly recommends prioritising high-impact, low-cost fixes such as these when resources are limited, rather than waiting for a full rebuild.
- Alt text on every image (low effort, high impact): describe what the image shows, not just its filename.
- Keyboard navigation order (medium effort, high impact): tab through your site and fix anywhere the focus jumps illogically.
- Colour contrast (low effort, high impact): check text against its background meets WCAG AA ratios.
- Clear form labels (low effort, high impact): every field needs a visible label, not just placeholder text.
- Logical heading structure (low effort, medium impact): one H1 per page, headings in proper order.
- Accessible PDFs (medium effort, medium impact): tag documents properly or offer an HTML alternative.
- Skip links (low effort, medium impact): let keyboard users jump past repeated navigation.
Log each fix with a date and a short description. That record becomes your evidence trail for your accessibility statement, an audit, or a regulator.
Why accessibility is good business, not just good compliance
Accessible websites tend to reach more customers, load faster for everyone, and read more clearly to search engines, which is why good accessibility work and good SEO often pull in the same direction. We build this thinking into visually distinctive websites and targeted SEO campaigns, alongside social media management and print materials that round out a full marketing presence.
— tibor
How Fylde Digital can help with accessible, compliant websites
We handle accessibility audits, remediation and accessible web builds as part of our wider web design and SEO, PPC and content work for small and medium-sized businesses. If hosting or infrastructure needs attention alongside your accessibility fixes, CTA Systems I.T. Solutions Ltd handles managed hosting and technical support.
Request a website review and we will flag accessibility issues worth fixing first, with a plan that fits your budget. Start with our Web Design Blackpool page to see how we approach accessible, conversion-focused builds.
FAQ
What is WCAG?
WCAG stands for the Web Content Accessibility Guidelines, the technical standard built around four principles: content that is perceivable, operable, understandable and robust. Public sector digital services in the UK are expected to meet WCAG 2.2 at level AA, and most private sector organisations now use the same benchmark.
What conditions automatically qualify you for disability under the Equality Act?
The Equality Act 2010 defines disability broadly rather than through a fixed list of conditions, covering anyone with a physical or mental impairment that has a substantial and long-term adverse effect on their ability to carry out normal daily activities. Businesses are expected to anticipate the needs of this wide range of customers rather than wait for a specific diagnosis to be disclosed, according to EHRC guidance.
Is WCAG a legal requirement in the UK?
WCAG 2.2 AA is a legal requirement for public sector websites and apps under the 2018 accessibility regulations. Private businesses are not bound by WCAG directly, but meeting it is widely treated as the practical way to satisfy the Equality Act’s reasonable adjustments duty.
Is it illegal to not have wheelchair access?
There is no single blanket law demanding wheelchair access everywhere, but the Equality Act 2010 requires service providers to make reasonable adjustments, which can include physical access depending on the size, cost and impact involved for that particular business. For digital services, the equivalent duty points toward meeting WCAG 2.2 AA so disabled customers can use a website on equal terms.
