This accessibility statement applies to the Lancashire Fire and Rescue Service website: https://www.lancsfirerescue.org.uk/
This website is run by Lancashire Fire and Rescue. We want as many people as possible to be able to use our website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
AbilityNet has advice on making your device easier to use if you have a disability.
We are aware of some issues that may affect the accessibility of some parts of the website:
- forms may be difficult for screen reader users to engage with
- images and videos may not be clearly described
- links and buttons may be difficult for some users to perceive
- some buttons and are not announced in a useful way by the screen reader
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email: firstname.lastname@example.org
- call: 01772 862545
We’ll consider your request and get back to you in [number] working days.
Reporting accessibility problems with this website
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, contact us:
- email: email@example.com
- call: 01772 862545
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).
Technical information about this website’s accessibility
Lancashire Fire and Rescue Service is committed to making its website 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, due to ‘the non-compliances and exemptions’ listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Text links and station types on our Local Stations page are only distinguished by a change in colour, which may be imperceivable to people with visual impairment or colour blindness. This fails WCAG success criterion 1.4.1 (Use of Colour).
We plan to provide an additional visual indication (e.g. an underline) to show that text is a link by March 2023. Any new links with follow this new convention. We are also developing an accessible version of the Local Stations map, which will not rely on colour to distinguish station types.
Colour contrast is insufficient in places making it hard from some people to read content or perceive graphics on our website. This fails WCAG success criteria 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text contrast).
We plan to change all colours that do not pass contrast requirements by March 2023. Any new colours will be tested for compliance before being used on the website.
Image alt text is used unnecessarily on decorative images, which in some places duplicate adjacent link text. This adds unnecessary complexity to the page and fails WCAG success criterion 1.1.1 (Non-text content).
We plan to remove alt text from decorative images by March 2023.
Some videos are missing text alternative or audio description so will be inaccessible to blind users. This fails WCAG success criterion 1.2.3 & 1.2.5 (Audio Description and Media Alternative.)
We plan to add audio description to videos that require them by March 2023.
The carousel on our homepage has hidden controls that still receive focus. This fails WCAG success criterion 1.3.1 (Info and Relationships).
We plan to remove these hidden elements from the focus order by March 2023.
Heading elements are not always used correctly, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and Relationships).
We plan to review and update all heading elements to ensure they are used correctly by March 2023.
The website is missing key ARIA page landmarks, which can make it difficult for some users to discern the structure of the webpage. This fails WCAG success criterion 1.3.1 (Info and relationships).
We plan to review and update page landmarks to ensure they are used correctly across the site by March 2023.
Navigation, links and buttons
Some page elements including accordions and buttons are not keyboard operable or announced clearly by the screen reader. This fails WCAG success criteria 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
As a priority issue, we plan to make all page elements keyboard operable by December 2022.
We plan to resolve these focus order issues by March 2023.
The purpose of links is not always clear from the text alone, which will affect screen reader users when they list links. This fails WCAG success criterion 2.4.4 (Link Purpose (In Context)).
We plan to change all links so they are meaningful without the context of the surrounding text by March 2023. Any new links added will also have clear purpose.
The presentation of text links is not consistent across the website, potentially making it difficult for users to discern what is and isn’t a link. This fails WCAG success criterion 3.2.4 (Consistent Identification).
We plan to adopt a single text link design and use this across the site by March 2023.
A number of our buttons, including social media buttons and the search button in the top navigation, are missing accessible labels so will be announced in an unhelpful way by a screen reader. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to add accessible labels to all buttons by December 2022.
Some form fields are missing programmatic labels, or the labels are not associated with the interactive page element, so the labels are not announced in a useful way by a screen reader. This fails WCAG success criteria 4.1.2 (Name, Role, Value), 1.3.1 (Info and relationships) and 3.3.2 (Labels or Instructions)
We plan to add programmatic labels to our form fields by December 2022. Any new forms will be developed with appropriate labels.
Required fields on our Enquiry Form are not clearly labelled. This may cause potentially avoidable errors and fails WCAG success criterion 3.3.2 (Labels or Instructions).
We plan to add clear required labelling to our form by March 2023.
The error messaging on our Enquiry Form is generic and does not describe how to correct the error. This fails WCAG success criterion 3.3.3 (Error suggestion).
We plan to change our error messaging so it accurately describes the issue and how to fix it by March 2023.
Forms embedded as iframes are missing clear titles so it may not be clear to screen reader users what is contained within the form. This fails WCAG success criterion 4.1.2 (Name, Role, Value).
We plan to add clear and descriptive titles to all iframes used across the site by March 2023.
The error messaging on our Home Fire Safety Form is not announced by the screen reader so blind users will be unaware an error has occurred. This fails WCAG success criterion 4.1.3 (Status Message).
We plan to make the error messaging assertive by December 2022.
What we’re doing to improve accessibility
We have assessed the impact of all accessibility issues listed in this statement and developed a roadmap for addressing them. This will be done in priority order to ensure those issues that have the most impact on users are resolved first. All issues classed as critical will be resolved by December 2022.
Preparation of this accessibility statement
This statement was prepared on 23 September 2020. It was last reviewed on 8 November 2022.
This website was last tested on 27 October 2022. This website was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and the test was carried out by Web Usability Partnership Ltd.
We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.