This accessibility statement applies to www.met.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 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.
The data visualisation tools used in our Crime Statistics and Data dashboards are not accessible by screen readers, screen recognition software and other assistive technology. They do not display well on smaller screens including mobiles and tablets however we have provided access to alternative formats.
Some parts of the forms (such as checkboxes, radio controls, list boxes and combination boxes) for reporting crimes, traffic incidents and anti-social behaviour may be difficult to use with keyboard navigation, screen readers such as JAWS and voice command software such as Dragon.
Most older PDF documents aren’t fully accessible to screen readers, however users can request accessible versions.
The Live Chat function may be difficult to use with keyboard navigation and for users of mobile devices and assistive technologies.
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
what the problem is
what computer and software you use
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.
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).
If you are in Northern Ireland and are not happy with how we respond to your complaint you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland.
Technical information about this website’s accessibility
The Metropolitan 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
There are a number of WCAG 2.1 AA non compliances within the data visualisations used in the Stats and Data dashboards including:
Missing alternative text on graphics. This doesn’t meet success criterion 1.1.1 Non-text Content (Level A).
Information and structure is not always conveyed with native, appropriate or semantic HTML elements. This doesn’t meet success criterion 1.3.1 Info and Relationships (Level A).
Some content doesn’t have enough contrast with foreground and background colours. This doesn’t meet success criterion 1.4.3 Contrast (Minimum) (Level AA).
Text is not always used to convey information rather than images of text. This doesn’t meet success criterion 1.4.5 Images of Text (Level AA).
Content doesn’t reflow or respond well on smaller screens or with zoomed displays. This doesn’t meet success criterion 1.4.10 Reflow (Level AA).
Tooltip content isn't dismissible, hoverable or persistent. This doesn’t meet success criterion 1.4.13 Content on Hover or Focus (Level AA)
Not all data visualisation content is keyboard accessible. This doesn’t meet success criterion 2.1.1 Keyboard (Level A).
Filter options can cause keyboard traps. This doesn’t meet Success Criterion 2.1.2 No Keyboard Trap (Level A)
The focus order doesn’t always reflect the logical relationships in the content. This doesn’t meet success criterion 2.4.3 Focus Order (Level A).
Not all focusable components have focus visible styles. This doesn’t meet success criterion 2.4.7 Focus Visible (Level AA).
Some form elements don’t have associated labels. This doesn’t meet success criterion 3.3.2 Labels or Instructions (Level A).
We are aiming to have all our stats and data on the London datastore by the end of December 2021 so you can download accessible versions.
Live chat (third party supplier)
Some content does not appear in a logical order. This doesn't meet success criterion 1.3.2 Meaningful Sequence (Level A).
Some links do not have clearly visible keyboard focus states. This doesn't meet success criterion 2.4.7 Focus Visible (Level AA).
Some input fields do not have meaningful labels. This doesn't meet success criterion 2.4.6 Headings and Labels (Level AA).
We aim to fix the issues on this list by the end of November 2021.
We are also aware that the live chat widget is not currently optimised for mobile use. We are investigating this with the third party supplier and will confirm a date for this to be fixed as soon as possible.
Dropdown menus and checkboxes in our forms are difficult to operate with a keyboard. This doesn’t meet success criterion 2.1.1 Keyboard (Level A).
When using the enter key to operate dropdown menus in our forms, required field validation messages will display before you submit your data. This doesn’t meet success criterion 2.1.1 Keyboard (Level A).
Form validation and error messages are not read out by some screen readers. This doesn't meet success criterion 3.3.1 Error Identification (Level A).
Some parts of our forms (such as checkboxes, radio controls, list boxes and combination boxes) are difficult or impossible to use with screen readers such as JAWS and voice command software such as Dragon. This doesn’t meet success criterion 4.1.2 Name, Role, Value (Level A).
We aim to fix the issues on this list by the end of December 2021.
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.
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 1 October 2021.
An external audit was carried out on this website in May 2019, and an automated test was run in September 2021.
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.