What are the Public Sector Bodies Accessibility Regulations?

Tagged with:


In September 2018, Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations became law.

These require websites and apps created or owned by public sector organisations to meet accessibility standards so that people who use assistive technology or have additional needs can access services and information.

These regulations don’t just cover public facing websites, they also apply to documents that can be downloaded, mobile apps, intranets, and extranets so this can have wide ranging implications for large organisations such as councils, government agencies and universities.

NOTE: We use the term “Systems” to describe the type of platforms that require accessibility action.

The regulations do not include a clear definition of what is meant by “public sector” but if you receive public funding then you may be required to comply with these regulations. This includes Higher and Further Education institutions. Further explanation of organisations that come under the regulations is given in the PSBAR scope section.

The Government Digital Service has a useful guide to get you started understanding accessibility requirements for public sector bodies.

To summarise, the regulations are made up of 3 components:

  1. Websites, apps, and documents hosted on these systems must comply with accessibility standards. There is a timeline for when new and existing websites must comply as well as mobile apps.
  2. Public sector organisations must publish an accessibility statement on their websites and in apps to inform visitors about the accessibility of their websites and apps.
  3. The government is required to monitor that public sector websites are meeting these regulations through checking accessibility statements and checking the accessibility of a sample of sites.


The regulations are monitored and enforced by several different bodies. The Government Digital Service (Part of the UK Cabinet Office) monitors compliance of the regulations and will escalate non-compliances to the two enforcement bodies. In Great Britain the enforcement body is the Equality and Human Rights Commission, and in Northern Ireland the enforcement body is the Equalities Commission for Northern Ireland. The monitoring and enforcement process is supported by the Equality Advisory and Support Service who take complaints from individuals such as members of the public.

The way monitoring and enforcement works has several levels to it, and the Government Digital Service works with organisations to improve compliance. Find out more about the process in our PSBAR monitoring and enforcement process guide.


In the UK the regulations are tied to an international standard of best practice for delivering accessible web content. The Web Content Accessibility Guidelines (WCAG) have been running for several decades and have gone through several versions.

WCAG underpins many pieces of accessibility legislation and standards across the globe, including the American Section 508 regulations, and the European Harmonised Standard EN 301 549.

When the regulations were released in 2018, the most recent standard was WCAG 2.1 and required organisations to meet all A and AA success criteria.

On Friday 9th December 2022, Cabinet Office of the UK Government released updated guidance regarding the PSBAR regulations on the Gov.uk site which detailed an addendum to the regulations which means as WCAG is updated, the regulations will automatically change to require the latest current version of WCAG to achieve compliance.

This means that when WCAG 2.2 releases, all organisations in scope will be required to start aiming for compliance against WCAG 2.2 A and AA success criteria. GDS have explained that there will be a 12 month grace period from the date of WCAG 2.2 release before they will be expecting 2.2 compliance evidence.

Read the guide on changes in WCAG 2.2.

Accessibility Statements

Part of the PSBAR requirements is the production of accessibility statements for websites in scope of the regulations.

An accessibility statement is a specific legal document that organisations must publish under PSBAR. The statement must include information about accessibility issues on a system, contact information, enforcement procedure, as well as several other legally required sections.

There is a specific template in the UK that must be followed for accessibility statements under PSBAR.

Private companies or others not covered by PSBAR may choose to write an accessibility statement. A good statement will still be similar to a PSBAR statement in terms of listing issues, contact information etc. but does not require certain pieces of legal wording.

Make Things Accessible has guides on understanding accessibility statements and how to write an accessibility statement, including a template you can download.

Disproportionate Burden

Disproportionate burden is a clause in PSBAR that allows organisations to avoid full compliance without penalty (not indefinitely) if the organisation proves that to achieve compliance would be a ‘disproportionate burden’.

To make a claim you must thoroughly evidence that compliance would for example:

Making a disproportionate burden claim requires a lot of supporting evidence and can only be used for niche failures to meet compliance. For example, you might be able to claim disproportionate burden for fixing one very specific failure against WCAG success criteria because to do so would require a complete website redesign for a tool which has low usage figures and there are other routes around. You would not be able to claim disproportionate burden generally, such as not having the funds or capacity to take any action towards compliance.

The subject of disproportionate burden is very nuanced and a claim should only be made as a last resort. To help you use disproportionate burden claims correctly, Make Things Accessible has guides to help you understand disproportionate burden, and how to write a disproportionate burden assessment.


PSBAR covers many different types of organisations and types of content. Because of the variety, and sometimes impossible challenges of making some content fully accessible, there are a range of exemptions to the regulations that you should be aware of.

Find out more about the exemptions and how they might apply to your systems and content in our PSBAR exemptions guide.

Share on:


Site preferences

Please feel free to display our site, your way by finding the preferences that work best for you. We do not track any data or preferences at all, should you select any options in the groups below, we store a small non-identifiable token to your browser's Local Storage, this is required for your preferencesto persist across pages accordion be present on repeat visits. You can remove those tokens if you wish, by simply selecting Unset, from each preference group.


Code block theme

Code theme help

Code block themes can be changed independent of the site theme.

  • Default: (Unset) Code blocks will have the same theme as the site theme.
  • Light 1: will be default for users viewing the light theme, this maintains the minimum 7:1 (WCAG Level AAA) contrast ratio we have used throughout the site, it can be quite difficult to identify the differences in colour between various syntax types, due to the similarities in colour at that contrast ratio
  • Light 2: drops the contrast for syntax highlighting down to WCAG Level AA standards (greater than 4.5:1)
  • Dark: Syntax highlighting has a minimum contrast of 7:1 and due to the dark background differences in colour may appear much more perceivable


Motion & animation

Motion & animation help

  • Default (Unset): Obeys device settings, if present. If no preference is set, there are subtle animations on this site which will be shown. If you have opted for reduce motion, smooth scrolling as well as expanding and collapsing animations will no longer be present, fading transtitions and micro animations will still be still present.
  • None: All animations and transitions are completely removed, including fade transitions.


Underline all links

Underline all links help

  • Default (Unset): Most links are underlined, with a few exceptions such as: the top level links in the main navigation (on large screens), cards, tags and icon links.
  • Yes: Will add underlines to the exceptions outlined above, resulting in every link being underlined

Text and paragraphs

Font size (main content)

Font size help

This setting does not apply to the site's header or footer regions

  • Default (Unset): Font sizes are set to site defaults
  • Selecting Large or Largest will increase the font size of the main content, the size of the increase depends on various factors such as your display size and/or zoom level. The easiest way to determine which option suits you best would be to view this text after clicking either size's button
Letter spacing

Letter spacing help

  • Default (Unset): Default letter spacing applies
  • Increased: Multiplies the font size by 0.12 and adds the sum as spacing between each character
Line height

Line height help

  • Default (Unset): all text has a minimum line height of 1.5 times the size of the text
  • Increased: all text has a line height of twice the size of the text
Line width

Line width help

  • Default (Unset): all text has a maximum line width of 80 REM units (this averages around 110 characters per line)
  • Decreased: all text has a maximum line width of 55 CH units (this averages around 80 characters per line)
Paragraph spacing

Paragraph spacing help

  • Default (Unset): The space between paragraphs is equivalent to 1.5 times the height of the paragraph's text
  • Increased: The space between paragraphs is equivalent to 2.25 times the height of the paragraph's text
Word spacing preference

Word spacing help

  • Default (Unset): No modifications to word spacing are present
  • Increased: Spaces between words are equivalent to 0.16 times the font size