Accessibility Statements - what are they?

Posted:
Tagged with:

An accessibility statement is a specific legal document that organisations must publish under the Public Sector Bodies Accessibility Regulations (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.

Who needs an accessibility statement

Any website, mobile app or other digital system owned, built, or purchased by an organisation in scope of PSBAR must have an accessibility statement.

This includes for third party products that an organisation makes it staff or customers use in some cases. For example, if you are paying for off the shelf 3rd party products you may need to work with the supplier to provide a statement for your users that interact with that system.

We would also say that really, everyone needs an accessibility statement. These are useful pieces of information for users with access needs that are valuable for any website or system. We would encourage everyone to have some form of accessibility related guidance available. It is good practice to test for accessibility issues and let users know if there any problems and who they can get help from or how they can request alternate formats.

What a statement should cover

The content of a statement should cover information about known issues, enforcement processes, contact methods, exemptions and a few other legal requirements, but this section is about the scope of how many systems a statement should cover.

Ideally you will have one statement for each distinct website or system. Sometimes you might have a statement for only part of a larger system or an specific user journey. For example if you are using a 3rd party form product that is integrated with your website, you may have a statement for the website as a whole and a statement for the forms if they have different contacts, or significantly different issues between the website and the forms journeys.

You should avoid writing a statement that covers multiple websites under different domains even if the multiple websites are designed on the same template. Ideally you will have one statement per domain. Multiple websites even if duplicates eventually diverge on content and will introduce unique issues, so having a single statement may list issues of one website that does not apply to the others, which can confuse users.

Subdomains such as library.westminster.ac.uk, which is a separate website but still part of the westminster.ac.uk domain would have its own statement separate to the main westminster.ac.uk statement.

Who checks accessibility statements

The Government Digital Service (GDS) as the monitoring body for the regulations will be assessing whether an accessibility statement meets requirements provided guidance on creating an accessibility statement in the form of a sample statement for a fictional website.

Regional differences

If you are in England, Scotland or Wales, the regulations that you need to mention in your statement are the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, and the Equality Act 2010. These are the relevant pieces of legislation for Accessibility Statement requirements and information on the enforcement procedure through the Equality and Human Rights Commission.

If you are in Northern Ireland you still need to mention the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations but may want to mention the Disability Discrimination Act 1995 which is still an active piece of legislation in Northern Ireland. (It was repealed and superseded by the Equality Act 2010 in England Scotland and Wales). You will also need to direct enforcement to the Equality Commission of Northern Ireland.

Writing an accessibility statement

If you want to write an accessibility statement for your website you can follow the sample statement provided by GDS, or if you want more step by step guidance, you can find more in our How to write an accessibility statement guide.

Share on:

TwitterLinkedIn

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.

Theming

Theme
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

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.

Links

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