Information checked: 21 July 2026.
UK accessibility duties depend on the organisation and service. The Public Sector Bodies accessibility regulations directly apply to covered public-sector websites and mobile applications, while businesses providing services should also consider duties under the Equality Act 2010. This page is general guidance, not legal advice.
In brief: Determine which duties apply, use WCAG as a practical standard and avoid claiming compliance without evidence.
Do not apply one rule to every organisation
| Framework | Who it primarily concerns | Practical implication |
|---|---|---|
| Public Sector Bodies Accessibility Regulations 2018 | Covered public-sector bodies | Meet the applicable accessibility requirement and publish an accessibility statement |
| Equality Act 2010 | Service providers and others within scope | Avoid disability discrimination and consider reasonable adjustments |
| WCAG 2.2 | Technical and content standard used broadly | Provides testable criteria at A, AA and AAA levels |
| Contracts and procurement | Organisations with specific customer or supplier commitments | May set additional standards, evidence and deadlines |
A responsible approach for a small business
- Identify the applicable legal and contractual context.
- Use WCAG 2.2 AA as a strong practical target where appropriate.
- Prioritise barriers in essential customer journeys.
- Publish an accurate contact route for accessibility problems.
- Record decisions, fixes and alternatives.
- Seek qualified advice where duties or disputes are uncertain.
Avoid unsupported compliance claims
A plugin, theme badge or automated scan cannot prove complete conformance. State what was tested, which standard and version were used, what remains inaccessible and when the information was reviewed.
Acceptance check
The organisation should be able to explain the standard it follows, the scope tested, known barriers, planned fixes and how a disabled user can request help or an alternative.
Record the basis of the claim
If a site states that it meets WCAG 2.2 AA, record the tested scope, exceptions, method and date. Public-sector statements should follow the applicable model and enforcement route; private organisations should avoid copying public-sector wording that does not match their status.
Records to keep
- Applicable legal and contractual framework.
- Conformance target and test scope.
- Known non-conformities and alternatives.
- Legal-advice or governance decision where needed.
Owner test: Compare the published wording with the latest test report and confirm that every compliance claim is supported.
Sources and date checked
This practical guidance was checked against the following primary sources. Legal duties depend on the organisation and service, so obtain qualified advice where the consequences are significant. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.