Accessibility rules for council and public sector websites and apps (2026)

What the regulations ask of a public sector website or mobile app, what's exempt, and who checks, taken from the GOV.UK guidance.

The short answer

Public sector bodies in the UK must make their websites and mobile apps meet the WCAG 2.2 AA accessibility standard and publish an accessibility statement, under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. The Government Digital Service checks a sample of public sector websites and apps each year, and the Equality and Human Rights Commission enforces the rules in England, Scotland and Wales (the Equality Commission for Northern Ireland in Northern Ireland).

Who the rules cover

In the GOV.UK guidance's words, public sector bodies.

  • Public sector bodies, for example local authorities, must meet the rules for their websites and mobile apps.
  • Charities and other non-government bodies are exempt unless they're mostly publicly funded, provide services that are essential to the public, or are aimed at disabled people.
  • Primary and secondary schools and nurseries are partly exempt, but content people need to use their services must still be accessible.
  • Public sector broadcasters and their subsidiaries are exempt.

What you have to do

  • Meet WCAG 2.2 AA, unless a legal exemption applies.
  • Publish an accessibility statement that explains how accessible the website or app is.
  • In the statement, list content that isn't accessible and why, including anything exempt or covered by a disproportionate burden assessment.
  • Set out your plans to fix the remaining issues, including with your suppliers.
  • Review and update the statement regularly.

What's exempt

Some content doesn't have to meet the standard.

  • Live audio and video.
  • Heritage collections, such as scanned manuscripts.
  • Maps, as long as essential information is available in an accessible format.
  • Third-party content you didn't pay for or develop, such as social media 'like' buttons.
  • Archived websites that aren't needed for your services and aren't updated.
  • PDFs and other documents published before 23 September 2018, unless people need them to use a service.
  • Pre-recorded audio and video published before 23 September 2020.

Disproportionate burden

If meeting part of the standard would be a disproportionate burden, you can say so, but only after carrying out an assessment. The GOV.UK guidance is clear that lack of time, knowledge or priority isn't a reason.

In practice, it's cheaper to build accessibility in from the start than to fix it later. When we build for councils, we build to WCAG 2.2 AA from the start.

Questions to ask your supplier

Whoever builds or hosts your site or app.

  • Will it meet WCAG 2.2 AA, and how will you test it?
  • Will you give us what we need for our accessibility statement?
  • How do we fix issues found after launch, and how fast?
  • Do the documents and forms we publish need to be accessible too, and who makes them so?

Quick answers

Which accessibility standard do public sector websites need to meet?

WCAG 2.2 AA, according to the GOV.UK guidance on the public sector accessibility regulations.

Do the rules apply to mobile apps?

Yes. The regulations cover public sector bodies' websites and mobile apps.

Do charities have to meet the public sector accessibility regulations?

Not usually. Charities and other non-government bodies are exempt unless they're mostly publicly funded, provide essential public services, or are aimed at disabled people.

What goes in an accessibility statement?

How accessible the website or app is, which content isn't accessible and why, and your plans to fix it. It should be reviewed and updated regularly.

Who enforces the rules?

The Equality and Human Rights Commission in England, Scotland and Wales, and the Equality Commission for Northern Ireland. The Government Digital Service monitors a sample of sites each year.

Free, in 10 seconds

See it working for your organisation

Type your organisation's name and what you run. Your own sample app opens straight away, with your name on it and the automations running live: bookings, payments, reminders and messages.

  • Click around it like the real thing
  • Watch it take bookings and send reminders by itself
  • The fixed price is on the page

Nothing to install and no card. We may email you once to ask what you thought. See our privacy policy.

Need an accessible website or app?

We build to WCAG 2.2 AA at a fixed price, with a working demo about two weeks in.