Enhance the user experience for your website visitors
Improve the build of your website to WCAG 2.2 Compliance
Instantly find and remediate every inaccessible PDF on your website
Accelerate your compliance journey with manual auditing and remediation
Get a free automated scan of your homepage for WCAG compliance issues and provides recommended fixes
Your hub for accessibility learning, resources, and support
Latest accessibility updates, insights, and industry trends
Practical, step-by-step resources to improve accessibility
Structured training to build accessibility skills and confidence
Get a free automated scan of your homepage for WCAG compliance issues and provides recommended fixes
Most public sector organisations know PSBAR exists. Far fewer have actually met the standard. Whether you are starting from scratch or picking up a stalled compliance effort, this is where to get a clear picture of what is required, and what to do next.
PSBAR applies to almost every public body. Central government, local councils, NHS trusts, universities, housing associations, and more are all in scope.
The standard is WCAG 2.2 AA. WCAG, the Web Content Accessibility Guidelines set out the technical requirements your website and mobile apps must meet. Level AA is the legal minimum. Read our plain English WCAG 2.2 guide.
An Accessibility Statement is mandatory. Every in-scope website must have a published accessibility statement explaining what is and is not accessible, and what you plan to do about it.
PDFs and documents are included. Minutes, reports, policies, and notices published on your website fall under the same rules as the site itself. See our PDF accessibility checklist.
Compliance is being actively monitored. The Cabinet Office and Government Digital Service check public sector websites against the standard and can issue enforcement notices.
PSBAR introduced three core, ongoing duties for public sector bodies.
1
Your website and mobile apps must conform to WCAG 2.2 AA. This is not a target or a best practice, it is a legal requirement.
2
You must publish a clear, up-to-date accessibility statement covering what is accessible, what is not, why any gaps exist, and how users can request accessible alternatives or raise a complaint.
3
New content, new features, and new documents all need to be checked on an ongoing basis. Compliance is not something you achieve once and move on from.
If your organisation is a public sector body in England, Scotland, or Wales, PSBAR almost certainly applies to you. That includes:
Not sure if you’re in scope? The regulations cover any body that is publicly funded or carries out a public function. When in doubt, treat it as applicable.
It is a legal requirement under PSBAR, and one of the most common areas of non-compliance. A valid statement must:
Documented proof of what was assessed, what was found, and what action was taken protects your organisation if a formal complaint or audit arises.
For some people, an inaccessible website is a complete barrier to services they have a right to access. That is not a small thing.
Enforcement notices, fines, and legal challenges are all real possibilities for organisations that ignore their obligations.
Every week your organisation publishes more content. Starting now means fewer problems, and less remediation work, down the line.
Clear policies and regular audits mean staff know what is expected when creating and publishing content.
An accessible digital presence tells the public their organisation is thinking about all of them, not just some of them.
Most public sector organisations publish hundreds of documents a year. Most of those documents are not accessible, and most organisations do not know it.
Exporting to PDF does not make a document accessible. Common problems include:
PSBAR is not a project with an end date. The Cabinet Office expects to see continuous improvement, which means:
Legal risk: If issues are identified, GDS can require your organisation to make improvements, typically within around 12 weeks, before escalating to the Equality and Human Rights Commission.
Financial risk: Fixing accessibility problems reactively costs significantly more than getting it right from the start, and cases that escalate can result in legal costs and financial penalties.
Reputational risk: Public sector organisations are expected to lead on inclusion, and when accessibility falls short it can affect how your organisation is perceived.
Operational risk: When digital services are difficult to use, people find other ways to get things done, more calls, more emails, and more pressure on internal teams.
Service delivery risk: If barriers exist, users may not be able to complete applications, find information, or engage with your organisation at all.
No evidence trail: Nothing to show if a formal complaint is made.
Free Website Accessibility Scan
What are the risks of not complying with UK public sector accessibility regulations?
Documented Accessibility Progress Guide