Accessibility statement for www.merseyside.police.uk
This accessibility statement applies to www.merseyside.police.uk
This website is run by the Single Online Home (SOH) platform and uses national templates. The content is a mix of national and local.
National content is managed by the SOH team, local content is managed by the individual forces. Responsibility for the accessibility compliance of the national content sits with the SOH team; individual forces are responsible for the accessibility compliance of their local content.
We want everyone to be able to use this website. You might have a better experience if you change the settings on your computer to suit your needs. The site has been built so that 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 or using 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.
We know some parts of this website aren’t fully accessible.
There are no ‘Skip to main content/navigation’ links on mobile or tablet views for users who rely on keyboard navigation.
When viewed on a mobile, the ‘Back to Top’ button doesn’t focus correctly for those who rely on keyboard navigation.
The pagination in the search results from the ‘Find your nearest police station’ is not announced to screen reader users.
On desktop and tablet views the filters on the search results pages are not available for screen reader users.
On search results pages the left and right arrows on the pagination navigation do not have a visible keyboard focus style.
Most older PDF documents aren’t fully accessible to screen readers. However, users can request accessible versions. The optional downloadable PDFs created after users complete any of our forms also aren't yet fully accessible for screen readers.
For forces who have live chat, the survey that sometimes appears at the end of the chat will be difficult to use with keyboard navigation.
Reporting accessibility problems with this website
If you can't access something you need on this site, please tell us about it and we will get you what you need in another way.
To help us understand the problem as quickly as we can, please tell us:
the web address or title of the page where you found the problem
Please note: this mailbox is only for accessibility enquiries. It you want to report crimes or other incidents, use our online crime reporting services. If a crime is happening now or someone is in immediate danger, call 999.
If you have a hearing or speech impairment, use our textphone service 18000 or text us on 999 if you’ve pre-registered with the emergencySMS service.
Feedback and contact information
If you'd like to contact us about something else, and you need a response, please use our contact page.
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
Merseyside Police is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The content listed below is non-accessible for the following reasons.
Non compliance with the accessibility regulations
The ‘Skip to main content/navigation’ links do not appear on mobile or tablet views. This doesn’t meet success criterion 2.4.1 Bypass blocks (Level A).
The ‘Back to Top’ button that appears on the mobile view accepts focus erratically if navigated using keyboard. This doesn’t meet success criterion 2.4.3 Focus order (Level A).
Some of the visual heading content on the ‘Contact us’ page is not contained in the correct semantic heading mark-up. This doesn’t meet success criterion 1.3.1 Info and relationships (Level A).
Results from the ‘Find your nearest police station’ search are not announced to screen reader users. This doesn’t meet success criterion 4.1.3 Status messages (Level AA).
On search results pages the left and right arrows on the pagination navigation do not have a visible keyboard focus style. This doesn’t meet success criterion 2.4.7 Focus visible (Level AA).
On desktop and tablet views the search filters are hidden from screen reader technologies. This doesn’t meet success criterion 4.1.2 Name, role, value (Level A).
Portions of the search results dynamic pagination content are not announced to screen reader users. This doesn’t meet success criterion 4.1.3 Status messages (Level AA).
The tabbed navigation on the Your Area pages may include some incorrect aria values and interactive elements that contain other nested interactive elements. These don’t meet success criterion 4.1.2 Name, role, value (Level A).
We aim to fix the issues above by end of January 2023.
PDFs and other documents
PDFs may not be suitable for users of assistive technology. We are in the process of replacing or fixing any PDF and Word documents which are essential to our services, however users can request accessible versions.
With a few exceptions, all new PDFs or Word documents we publish will meet accessibility standards. All new documents that aren’t accessible will be clearly identified, and we will provide an accessible version wherever possible.
After users complete some of our forms they are given the option to download a copy of their data in PDF format. We know that these PDFs are not currently fully accessible to screen readers. Building accessible PDFs is part of our future development plans and is being reviewed.
Content that’s not within scope of the accessibility regulations
Many of our older PDFs and Word documents are not fully accessible, for example, they may not be easy to read using a screen reader.
We aim to have replaced or fixed any PDF and Word documents which are essential to our services, like forms published as Word documents.
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. For example, we don’t plan to fix every older non-essential document like old campaign PDFs.
How we tested this website
This website was last tested using:
automated testing – the quickest way to catch 20% to 50% of potential issues
manual testing – using assistive technology tools to test the website with a social focus on areas with known problems
user testing – asking users with accessibility needs to test the website, and learning from their feedback
We continually monitor and test the accessibility of our site and have made fixing and improving the accessibility of the site part of our daily work.
Preparation of this accessibility statement
This statement was prepared on 20 September 2019. It was last reviewed on 26 October 2022.
A full external audit was carried out on this website in May 2019, and a more limited Government Digital Service audit was run in October 2022.
We tested the service based on a user's ability to complete key journeys. All parts of the chosen journeys were tested, including documents. Journeys were chosen on a number of factors including usage statistics, risk assessments and subject matter.