PSBAR 2018: Accessibility Rules for Public Sector Suppliers

<div className="my-6 rounded-lg border border-slate-200 bg-slate-50 p-5"> <div className="mb-2 flex items-center gap-2 text-slate-700 font-semibold"> <svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true"> <circle cx="10" cy="10" r="9" stroke="currentColor" strokeWidth="2" /> <path d="M10 6v5M10 13.5v.5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" /> </svg> <span>Quick summary</span> </div> <ul className="list-disc space-y-1 pl-5 text-sm text-slate-800"> <li><strong>Who:</strong> UK public sector bodies. Suppliers are bound through contracts and procurement.</li> <li><strong>Standard:</strong> WCAG 2.1 AA is the legal minimum. WCAG 2.2 AA is the working benchmark since October 2023.</li> <li><strong>Deadline:</strong> An accessibility statement must already be in place for every in-scope site and app.</li> <li><strong>Monitored by:</strong> Cabinet Office Government Digital Service. Enforced by EHRC (GB) and ECNI (NI).</li> </ul> </div>

The <a href="https://www.legislation.gov.uk/uksi/2018/952/contents/made">Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018</a> (SI 2018/952), known as PSBAR 2018, implement the EU Web Accessibility Directive in UK law. They require public sector bodies to make their websites and mobile applications meet WCAG accessibility standards. Bodies must also publish accessibility statements that document their compliance position.

PSBAR 2018 directly binds public sector bodies rather than private companies. Understanding the regulations still matters for any supplier that builds, maintains or provides technology to UK public sector clients. Contracts for public sector digital services routinely pass PSBAR obligations down the supply chain. Procurement frameworks such as G-Cloud and the Digital Marketplace require suppliers to show accessibility compliance.

For an overview of accessibility duties on private sector websites under the Equality Act 2010, see website accessibility under the Equality Act 2010.

Scope: which bodies and which content

PSBAR 2018 applies to public sector bodies as defined in Regulation 2. The definition covers central government departments and agencies, local authorities, NHS trusts and bodies, maintained schools and higher education institutions plus most other bodies exercising a function of a public nature. Bodies governed by private law (private companies, charities and social enterprises) are not directly bound. Public funding does not change that.

The regulations apply to websites (defined to include web applications accessible via a browser) and to mobile applications. Certain content is excluded from scope entirely:

• Pre-recorded audio and video content published before 23 September 2020.
• Live audio and video.
• Online maps where essential navigational information is provided by alternative accessible means.
• Third-party content not under the body's control.
• Reproductions of items in heritage collections that cannot reasonably be made accessible.

Content can also be exempted on grounds of disproportionate burden. This exemption requires evidence of a genuine proportionality assessment, not a blanket assertion. GDS has made clear in its monitoring activities that bodies claiming disproportionate burden must show they have assessed the cost and impact of compliance against the benefits to disabled users.

<div className="my-6 overflow-x-auto"> <table className="w-full border-collapse text-sm"> <thead> <tr className="bg-slate-100"> <th className="border border-slate-300 p-2 text-left">Body type</th> <th className="border border-slate-300 p-2 text-left">In PSBAR scope?</th> <th className="border border-slate-300 p-2 text-left">Monitored by</th> </tr> </thead> <tbody> <tr> <td className="border border-slate-300 p-2">Central government departments and agencies</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">Yes</td> <td className="border border-slate-300 p-2">Cabinet Office GDS</td> </tr> <tr> <td className="border border-slate-300 p-2">Local authorities</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">Yes</td> <td className="border border-slate-300 p-2">Cabinet Office GDS</td> </tr> <tr> <td className="border border-slate-300 p-2">NHS trusts and ICBs</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">Yes</td> <td className="border border-slate-300 p-2">Cabinet Office GDS</td> </tr> <tr> <td className="border border-slate-300 p-2">Maintained schools, universities, FE colleges</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">Yes</td> <td className="border border-slate-300 p-2">Cabinet Office GDS</td> </tr> <tr> <td className="border border-slate-300 p-2">Private companies and charities</td> <td className="border border-slate-300 p-2 text-rose-700 font-semibold">No</td> <td className="border border-slate-300 p-2">N/A (Equality Act 2010 still applies)</td> </tr> <tr> <td className="border border-slate-300 p-2">Public sector bodies in Northern Ireland</td> <td className="border border-slate-300 p-2 text-emerald-700 font-semibold">Yes</td> <td className="border border-slate-300 p-2">Cabinet Office GDS, with ECNI enforcement</td> </tr> </tbody> </table> </div>

The WCAG standard

PSBAR 2018 requires compliance with WCAG 2.1 Level AA. The W3C published <a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a> as a Recommendation on 5 October 2023. It supersedes WCAG 2.1. Public sector bodies are now generally expected to work towards WCAG 2.2 AA compliance. GDS accessibility monitoring and the Service Standard treat WCAG 2.2 AA as the current benchmark.

WCAG 2.2 introduced nine new success criteria relative to WCAG 2.1 and removed one (4.1.1 Parsing, now obsolete in light of modern browser behaviour). The new criteria are focused on cognitive accessibility and input methods:

• 2.4.11 Focus Not Obscured (Minimum)
• 2.4.12 Focus Not Obscured (Enhanced)
• 2.4.13 Focus Appearance
• 2.5.7 Dragging Movements
• 2.5.8 Target Size (Minimum)
• 3.2.6 Consistent Help
• 3.3.7 Redundant Entry
• 3.3.8 Accessible Authentication (Minimum)
• 3.3.9 Accessible Authentication (Enhanced)

Public sector suppliers delivering new builds should design to WCAG 2.2 AA from the outset. Existing contracts that specify WCAG 2.1 AA may not automatically require WCAG 2.2 compliance. Procurement bodies usually seek WCAG 2.2 conformance at contract renewal.

The accessibility statement requirement

PSBAR 2018 requires every in-scope public sector body to publish an accessibility statement for each website and mobile application. The statement must be published in an accessible format (typically HTML, not a PDF). It must be easy to find from the site or app and contain a specified set of information.

The required content is set out in the Schedule to the regulations. An accessibility statement must include:

• A statement of the body's general policy on accessibility and its commitment to accessible websites and mobile applications.
• The current level of compliance (fully conformant, partially conformant or non-conformant with WCAG) with known non-accessible content listed and explained.
• The reasons for any non-compliance or exemption claims.
• A description of any alternative access mechanisms where content is not fully accessible.
• Contact details for users to request accessible formats or report accessibility problems.
• A link to the enforcement procedure (the EHRC route in Great Britain or ECNI in Northern Ireland).

GDS provides a generator tool for accessibility statements through its <a href="https://www.gov.uk/government/publications/sample-accessibility-statement">sample accessibility statement</a> on gov.uk. For most public sector bodies, the GDS sample is the starting point. It is then customised with the body's actual audit findings.

<div className="my-6 rounded-lg border border-emerald-200 bg-emerald-50 p-4"> <div className="mb-2 flex items-center gap-2 text-emerald-700 font-semibold"> <svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true"> <rect x="3" y="3" width="14" height="14" rx="2" stroke="currentColor" strokeWidth="2" /> <path d="M6 10.5l2.5 2.5L14 7.5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" /> </svg> <span>Accessibility statement checklist</span> </div> <ol className="list-decimal space-y-1 pl-5 text-sm text-emerald-900"> <li>Audit the site or app against WCAG 2.2 AA.</li> <li>List every known accessibility issue with location and impact.</li> <li>State the conformance level: fully, partially or non-conformant.</li> <li>Justify any disproportionate burden claims with documented evidence.</li> <li>Add alternative access routes for any inaccessible content.</li> <li>Publish contact details for accessibility requests and complaints.</li> <li>Link to the EHRC or ECNI enforcement procedure.</li> <li>Date the statement and review it at least once a year.</li> </ol> </div>

Monitoring and enforcement

The Cabinet Office Government Digital Service runs the monitoring programme. GDS samples a set of public sector websites and mobile applications each year. It publishes its <a href="https://www.gov.uk/government/collections/accessibility-monitoring-of-public-sector-websites-and-mobile-applications">accessibility monitoring of public sector websites and mobile applications</a> on gov.uk. Monitoring usually combines automated testing using tools such as axe-core with manual expert review. GDS reports findings to the relevant body and expects remediation within a reasonable timeframe.

Formal enforcement under PSBAR runs through the Equality and Human Rights Commission in England, Wales and Scotland. In Northern Ireland it runs through the Equality Commission for Northern Ireland. Enforcement notices are rare. GDS typically works with non-compliant bodies to agree a remediation plan before escalation. Users can also bring complaints under the Equality Act 2010 if they have been excluded from a service.

A user who is not satisfied with a body's response can:

1. Raise the issue with the body using the contact details in the accessibility statement.
2. Escalate to the EHRC (or ECNI in Northern Ireland) through the published enforcement procedure.
3. Pursue a county court claim under the Equality Act 2010 where a reasonable adjustment has been refused.

Implications for private sector suppliers

If your organisation builds websites, applications or digital services for public sector clients, PSBAR obligations flow through your contract. Most public sector framework agreements (G-Cloud, the Crown Commercial Service Digital Outcomes framework) require suppliers to warrant that deliverables meet accessibility standards.

In practice this means:

Procurement stage: Tenders and applications often ask for evidence of accessibility compliance. Examples include audit reports, VPAT or ACR documents and WCAG conformance statements. Suppliers who cannot show experience with accessibility testing are at a disadvantage.

Contract terms: Delivery contracts for public sector work usually include acceptance criteria that reference WCAG compliance. Defects that cause non-compliance with the client's PSBAR obligations may be treated as contractual defects that require rectification.

Accessibility auditing: Suppliers who provide components or platforms used on public sector websites may be asked to provide accessibility conformance reports. A current third-party audit reduces procurement friction.

Statement support: The public sector body is responsible for publishing the accessibility statement. Where the body relies on a supplier's platform, the supplier may be expected to provide conformance information for that platform.

Relationship with the Equality Act 2010

PSBAR 2018 and the <a href="https://www.legislation.gov.uk/ukpga/2010/15/contents">Equality Act 2010</a> operate in parallel. PSBAR is sector-specific and prescriptive about standard and documentation. The Equality Act 2010 imposes a broader reasonable adjustments duty on all service providers, public sector bodies included. It does not specify a technical standard.

A public sector body that meets PSBAR but still excludes disabled users from accessing specific content may still be in breach of the Equality Act's reasonable adjustments duty. A body that fails PSBAR monitoring may not face an Equality Act claim if disabled users can access the service by other means. The two regimes are distinct. Both push towards the same outcome of digital services that work for disabled users.

For a practical check of your website's accessibility baseline, run a free scan at /uk/en/scan.