Accessibility Statement

Staffordshire Fire and Rescue Service

This statement applies to content published on the www.staffordshirefire.gov.uk domain. It does not apply to content on staffordshirefire.gov.uk subdomains.

This website is run by Staffordshire Fire and Rescue Service. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:

  • Change colours, contrast levels and fonts using browser or device settings
  • Zoom in up to 400% on most pages without the text spilling off the screen
  • Navigate most of the website using a keyboard or speech recognition software
  • Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.

How accessible this website is

Parts of this website are not fully accessible. For example:

  • The date field on some forms do not have clear HTML element labels making it difficult for screen readers to read.
  • Some video elements do not have captions because they have been published before 23 September 2020.
  • Some documents are in PDF or non-HTML format and are not accessible.
  • On the news listing pages, the left and right arrows on the pagination navigation do not have a visible keyboard focus.
  • Some third party YouTube video content have no captions.

Technical information about this website’s accessibility

Staffordshire Fire and Rescue Service is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Some pages when at 400% zoom and in mobile view (320 x 256 pixels), the cookie banner does not reflow correctly as the content now overflows the visible part of the screen and cannot be scrolled. This fails WCAG 2.2 success criterion 1.4.10 (Reflow). We aim to fix this issue by 5 August 2026.

Some pages when the keyboard tabs or mouse hovers over the navigation bar dropdown menus, there is no mechanism to dismiss the additional content triggered without moving pointer hover or keyboard focus. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus). We aim to fix this issue by 5 August 2026.

Some pages when the keyboard tabs or mouse hovers over the navigation bar dropdown menus, there is no mechanism to dismiss the additional content triggered without moving pointer hover or keyboard focus. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus). We aim to fix this issue by 5 August 2026.

On some pages the links in the footer of the webpage are obscured behind the cookie banner. More focused elements become hidden from view if the site is viewed at 200% and 400% zoom. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured). We aim to fix this issue by 5 August 2026.

On some news pages the keyboard focus is not visible when it tabs onto the number pagination under the articles. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible). We aim to fix this issue by 5 August 2026.

On some PDF documents there are multiple elements across the document that do not have sufficient colour contrast. This fails WCAG 2.2 success criterion 1.4.3 (Contrast). We aim to fix this issue by 5 August 2026.

Content that’s not within the scope of the accessibility regulations

  • There are some instances of third-party interactive material embedded into our web pages that we have no control over in regards to accessibility
  • Adding subtitles to existing media created before 2018
  • The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

How we tested this website

Our website is currently tested for compliance with the Web Content Accessibility Guidelines V2.2 level A and level AA using the SiteImprove automated accessibility service.

What we’re doing to improve accessibility

We are fixing content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard. We will update this page as and when issues are fixed.

As an organisation, we aim to move away from uploading PDFs to the website where feasible in favour of displaying relevant information in a HTML format to improve user experience. This is a key part of our services accessibility strategy written in 2023.

Feedback and contact information

Tell us if you need information in a different format.

In your message, include:

  • the web address (URL) of the content
  • your email address and name
  • the format you need - for example, plain text, accessible PDF, large print, or audio recording

We’ll consider your request and get back to you within 10 working days.

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact us.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).

If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Preparation of this accessibility statement

This statement was prepared on 12 December 2022. It was last reviewed on 11 March 2026.

This website was last tested on 2 March 2026. The test was carried out by Staffordshire Fire and Rescue Service using third-party accessibility tools.

We will review our accessibility statement on a regular basis to ensure accuracy, at least once per year.