Title: Public Sector Body Accessibility Regulations (PSBAR) Guide
Introduction
Digital accessibility is no longer optional—it's a fundamental aspect of inclusive online experiences, especially for public sector organizations. Across the UK and other parts of Europe, laws like the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, more commonly referred to as the PSBAR, require public sector websites and mobile applications to meet specific accessibility standards. But what does this really mean? Who does it apply to? And how can organizations take practical steps toward digital inclusivity?
In this comprehensive PSBAR guide, we’ll demystify the regulation, explore its relationship with the WCAG standards and EN 301 549, discuss how it fits into the broader legal framework like the European Accessibility Act (EAA), and show how a smart tool like allyWay can support accessibility efforts—without making unrealistic promises.
Whether you’re responsible for a local council site, an NHS portal, or a university intranet, this article offers practical insights into making your digital platforms more accessible for everyone.
What Is the Public Sector Body Accessibility Regulations (PSBAR)?
The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations were introduced in the UK in September 2018. PSBAR aims to ensure that government and public sector digital services are accessible to all users, especially those with disabilities.
Key Facts About PSBAR
- Applies to most public sector bodies in the UK
- Requires websites and mobile apps to be accessible and published with an accessibility statement
- Aligns with the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level
- Builds upon the Equality Act 2010, adding specific digital responsibilities
Though the UK has left the EU, PSBAR was enacted prior to Brexit and reflects the principles of EU Directive 2016/2102 on web accessibility.
Who Must Comply?
Public sector organizations covered by PSBAR include:
✓ Central and local government bodies
✓ NHS and healthcare providers
✓ Police and emergency services
✓ Education institutions (some exceptions apply)
✓ Public-facing digital platforms funded by government entities
However, some bodies are partially exempt, such as:
→ Non-government funded schools
→ Nursery schools
→ Some charities
A detailed assessment may be necessary to determine exact responsibilities.
Why Accessibility Matters for Public Sector Websites and Apps
Providing accessible websites and mobile applications isn't just a legal obligation—it’s a social responsibility. As nearly one in five people in the UK reports a disability, inaccessible digital experiences can exclude large groups from accessing vital public services.
Top Benefits of Accessibility in the Public Sector
- Legal risk reduction – Reduces the chance of discrimination claims
- Better user experience – Makes digital services usable for everyone
- Improved SEO – Accessibility overlaps with SEO best practices
- Operational efficiency – Reduces costs related to user complaints and service desk support
- Public trust and reputation – Shows commitment to inclusivity and social good
allyWay can be a strategic partner in supporting these benefits. It helps identify and address accessibility barriers with scalable tools suited for public-facing and intranet-delivered web platforms.
Understanding the WCAG Connection
What Are WCAG 2.1 Guidelines?
The Web Content Accessibility Guidelines (WCAG) define how to make digital content more accessible. WCAG 2.1 Level AA is the standard referenced by PSBAR.
It is built upon 4 core principles, known as POUR:
- Perceivable – Information must be presented in ways users can perceive
- Operable – Interface must be navigable by all
- Understandable – Content must be comprehensible
- Robust – Content must be compatible with assistive technologies
Why WCAG 2.1 AA?
- Balances technical feasibility and user benefit
- Used internationally (including in ADA and EN 301 549 contexts)
- Offers a clear benchmark for public sector organizations to aim for
allyWay supports WCAG improvement by combining an AI-powered audit engine and over 30 accessibility enhancements, making it easier for organizations to identify, prioritize, and address accessibility gaps.
How PSBAR Relates to EN 301 549 and the EAA
EN 301 549 and Digital Accessibility
EN 301 549 is the European harmonized standard developed for ICT product accessibility, including websites and apps. It underpins PSBAR and aligns with WCAG, making it a useful reference framework for compliance strategies.
The Broader Reach: European Accessibility Act (EAA)
Finally, the European Accessibility Act (EAA) broadens digital accessibility mandates beyond the public sector. Scheduled to be enforced from July 2025, it applies to a wider range of services (e.g. eCommerce, banking, and eBooks).
If your public sector body also delivers digital services that may be impacted by future EAA requirements, adopting WCAG 2.1 AA practices now is a forward-thinking move.
Seamlessly supporting these evolving frameworks, allyWay presents a sustainable solution to strengthen accessibility initiatives, while preparing for future regulations.
What Are the Core Requirements of PSBAR?
Let’s break the regulation down into actionable components.
You Must:
- Make websites and mobile apps accessible
- Publish an accessibility statement
- Keep accessibility up to date
- Respond to accessibility issues and fix them rapidly
Accessibility Deadlines You Should Know
| Resource Type | Deadline |
|---|---|
| Public websites published before 23 Sep 2018 | 23 Sep 2020 |
| Public websites published after 23 Sep 2018 | 23 Sep 2019 |
| Mobile apps | 23 June 2021 |
Required Accessibility Statement
Public sector sites must publish a statement that:
- Describes accessibility status
- Identifies known issues
- States applicable exceptions (if any)
- Provides a way for users to report accessibility barriers
The accessibility statement must follow GOV.UK’s recommended template or equivalent.
allyWay supports this process by generating audit reports that help content creators draft accurate, transparent accessibility statements based on real observations.
Practical Steps to Improve Your Accessibility
Improving digital accessibility doesn’t have to be overwhelming. Here’s a structured roadmap:
Step-by-Step Action Plan
- Audit your website or application
- Identify barriers and prioritize critical issues
- Fix WCAG 2.1 AA issues
- Use tools and manual testing
- Train your content and development teams
- Promote accessibility awareness
- Create and maintain an accessibility statement
- Monitor changes regularly
- Ensure new content stays accessible
Helpful Tools
| Tool/Service | Description |
|---|---|
| allyWay | AI-powered accessibility audit + 30+ features for continuous improvement |
| WAVE | In-browser accessibility checker |
| Axe DevTools | Chrome/Firefox extension for developers |
| NVDA | Free screen reader for testing |
| Lighthouse | Chrome DevTools audit feature |
How allyWay Supports PSBAR Compliance Efforts
While no tool can guarantee compliance, digital accessibility platforms like allyWay play a key role in enabling organizations to meet accessibility goals faster and more effectively.
Here’s how allyWay can support public sector compliance strategies:
allyWay Features Overview Table
| Feature Category | Description |
|---|---|
| AI-Powered Audit | Scans site to detect WCAG-related issues |
| Accessibility Profiles | 5 user-centric modes (visual, cognitive, ADHD, motor, seizure-safe) |
| 30+ Accessibility Tools | Text contrast, readable fonts, keyboard nav, text-to-speech, and more |
| Multilingual Support | Supports 35+ languages for global audiences |
| Custom Branding | Seamlessly integrates into your organization’s branding |
| Auto-Monitoring | Periodic scans to detect newly introduced issues |
allyWay is designed to scale with your site’s evolution, making it a smart, business-friendly accessibility platform for sustained improvement.
Internal Accessibility vs. External Requirements
Often, teams focus on external-facing websites but forget internal systems and intranets—which PSBAR covers broadly. allyWay supports both websites and web applications, making it ideal even for less-publicly visible platforms like employee portals and training environments.
Frequently Asked Questions (FAQ)
What does PSBAR require from my organization?
The PSBAR mandates that public sector websites and mobile apps must be made accessible, publish an accessibility statement, and ensure continued monitoring and resolution of barriers.
Does using allyWay mean my site is compliant?
No, no one tool can automatically ensure legal compliance. However, allyWay supports your efforts by reducing barriers, scanning for WCAG 2.1 AA issues, and providing accessibility enhancements.
Are we exempt from PSBAR if we’re a small public sector body?
Some smaller public sector bodies may be partially or temporarily exempt, but accessibility should still be regarded as a best practice. It’s recommended to perform at least a basic audit and patch high-priority issues.
Should we focus only on WCAG improvements?
WCAG 2.1 AA is the primary guideline right now, but future legislation like the EAA may bring broader scope. Getting a head start ensures long-term sustainability and user inclusion.
How often should we review accessibility?
Regular reviews—at least quarterly—are recommended. allyWay’s automated audits
