Accessibility Statement

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:

• zoom in up to 300% without problems
• navigate most of the website using just a keyboard
• navigate most of the website using speech recognition software
• use 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.

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.

If you contact us with a complaint and you’re not happy with our response contact the Equality Advisory and Support Service (EASS).

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’).

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.

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

Non-compliance with the accessibility regulations

1. Some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
2. Some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.4.2 success criterion (Page Titled).
3. Some features are inconsistently named, for example accordions, tables of contents, search boxes and translation navigation. This fails WCAG 2.1 success criterion 3.2.4 (Consistent Identification).
4. Some pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways).
5. Some buttons look like links. This means it is difficult for some users to complete a transaction or onward journey. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
6. Some pages have inconsistently-placed language navigation. This fails WCAG 2.1 success criterion 3.2.4 success criterion (Consistent Identification).
7. Some content looks like headings but is not. This makes it difficult for screen reader users to navigate the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
8. Many documents are in less accessible formats, for example PDF. Non-HTML documents published on or after 23 September 2018 must have an accessible format.

PDFs and non-HTML documents

Many documents are not accessible in a number of ways including missing text alternatives and missing document structure.

View the accessible document policy of the organisation that published the document to report any problems or request documents in an alternative format. If more than one organisation is listed, view the accessible document policy of the first.

We believe that fixing the accessibility problems with some content would be disproportionate because the relevant platform will be retired soon.

Performance information

Some of the content published at the publication scheme is non-accessible:

• broken ARIA reference, this fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships) and WCAG 2.1 success criterion 4.1.2 (Name, Role, Value)
• some foreground and background colours lack contrast, so users with low vision may find it difficult to, for example, pick out rows in tables - this fails WCAG 2.1 success criterion 1.4.3 (Contrast)
• some pages are missing a heading - this fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships)
• adjacent links go to the same URL, which means additional navigation and repetition for keyboard and screen reader users - this fails WCAG 2.1 success criterion 2.1.1 (Keyboard)

Non-HTML documents published before September 2018 do not need to be accessible - unless users need them to use a service.

We use the Web Content Accessibility Guidelines V2.1 level A and level AA to test how accessible www.staffordshirefire.gov.uk is.

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