Accessibility Requirements for Public Sector Websites

Building an accessible website isn’t just about ticking off a few checkboxes. It’s a legal obligation for public sector bodies across the UK, but more importantly, it’s a commitment to treating every user with fairness and respect. If you’re responsible for a public sector website and feeling a bit lost, Priority Pixels offers website accessibility services to help you meet your obligations and build a site that truly works for everyone.

Accessibility might sound like a dry topic on paper, but in practice, it’s about creating websites that don’t leave anyone behind, whether someone’s using a screen reader, navigating with a keyboard, struggling with low vision or simply trying to book an appointment while juggling a toddler and a cup of tea.

Why accessibility matters

Imagine trying to renew a passport or pay council tax but the website only works if you have perfect eyesight and a steady hand with a mouse. For millions of people living with disabilities, badly designed websites aren’t just annoying, they’re a barrier to independence and participation in daily life.

Public sector organisations have a clear duty to make sure their websites and mobile apps are accessible to everyone. It’s not about bells and whistles, it’s about basic usability. The law sets the bar at WCAG 2.2 Level AA, a set of internationally recognised standards that ensure websites are:

• Perceivable: Information must be presented in ways users can see or hear, not just visually
• Operable: Navigation must be possible by keyboard, mouse, voice command or other methods
• Understandable: Content must be clear, consistent and easy to follow
• Robust: Websites must work reliably across different devices, browsers and assistive technologies

Put simply, your website needs to be usable by someone browsing with a keyboard on an old laptop just as much as someone on the latest iPhone.

What public sector websites must do

The accessibility requirements for public sector websites aren’t suggestions or nice-to-haves. They are obligations set out in the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you’re building or managing a public sector website, you need to:

• Meet WCAG 2.2 Level AA standards across your entire website or app
• Publish an accessibility statement that’s easy to find, easy to understand and kept up to date
• Monitor accessibility on an ongoing basis, not just when the website is launched
• Apply these standards to intranets and extranets published on or after 23 September 2019

The accessibility statement deserves a bit more attention. It should explain:

• How accessible your website or app is
• Where users might encounter barriers
• What alternative access routes are available
• How to contact you if users have problems
• What improvements you plan to make

And no, saying “we’re doing our best” isn’t enough. The statement needs to be factual, honest and actionable.

Exemptions and disproportionate burden

There are a few exemptions to the rules. You’re not expected to retrofit every scrap of ancient content or provide subtitles for live council meetings streamed at 3am. Content types usually exempt include:

• Pre-recorded audio and video published before 23 September 2020
• Live audio and video
• Scanned heritage collections, like old manuscripts
• PDFs or other documents published before 23 September 2018 unless essential for active services
• Maps, although important information shown on maps must be provided in another format
• Third-party content you did not create and do not control

Public sector bodies can also claim “disproportionate burden” if making certain content accessible would be so costly or difficult that it would severely impact operations. For example, updating hundreds of old scanned documents might count if the resource drain would outweigh the benefit. However, this claim must be properly assessed, documented and published in your accessibility statement.

You can’t just wave the phrase around like a get-out-of-jail-free card. If challenged, you’ll need to show you seriously considered the costs and benefits.

How accessibility is monitored and enforced

The Government Digital Service (GDS) monitors public sector websites and mobile apps by carrying out accessibility audits. They do not need to warn you before checking your site. If your website is found to be non-compliant, you could be named publicly on the government website.

Even worse, failure to meet accessibility standards can also breach the Equality Act 2010, which prohibits discrimination against people with disabilities. That could open the door to legal action, reputational damage and a lot of unwanted attention.

Priority Pixels builds bespoke WordPress websites that meet accessibility requirements from the very start, helping public sector organisations avoid costly mistakes and create better experiences for users.

Practical ways to stay accessible

Building an accessible website is just the beginning. Accessibility is a moving target, not a one-time project. To stay compliant and genuinely user-friendly:

• Test your site manually as well as automatically. Screen readers, keyboard-only navigation and mobile testing should all be part of the process
• Fix issues promptly when found. Don’t just stick them on a to-do list for “some time next quarter”
• Update your accessibility statement whenever changes are made to the site that affect accessibility
• Train your content editors to follow accessibility best practices for headings, alt text, links and documents
• Factor accessibility into every website update, big or small

Priority Pixels supports public sector clients with managed hosting, maintenance and continuous improvements, ensuring their WordPress websites stay accessible long after launch.

Accessibility benefits everyone

Designing for accessibility doesn’t just help disabled users. It makes websites easier to use for everyone. Clearer layouts help people in a hurry. Good contrast helps those on cracked screens. Keyboard navigation helps people with repetitive strain injuries. Even someone holding a baby in one arm and scrolling with the other benefits from simple, usable design.

In the end, accessibility isn’t a burden. It’s just good design. It’s a way of respecting your users, meeting your legal duties and building websites that work better for everybody.

Priority Pixels believes the web should be for everyone. Every bespoke WordPress website we create is built with accessibility in mind from the very first line of code. If you’re ready to build a site that’s inclusive, future-proof and legally compliant, get in touch with the team today.