Accessibility statement for MDP

This accessibility statement applies to www.mod.police.uk.

This website is run by Ministry of Defence Police. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 200% 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)

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.

How accessible this website is

We know that some elements of this website are not fully accessible. For example:

  • Embedded forms do not fully meet accessibility standards
  • Embedded maps are not fully accessible, for example they are missing focus indicator and the controls are missing accessible names

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: MDP-GeneralEnquiries-GMB@mod.gov.uk

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

Write to us at the following address:

General Enquiries
Ministry of Defence Police Headquarters
Palmer Pavilion
RAF Wyton
Huntingdon
PE28 2EA

We’ll consider your request and get back to you in 10 working days from date of receipt.

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

Technical information about this website’s accessibility

Ministry of Defence Police is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Cookiebot

  • At 200% zoom the bottom of the cookie banner available when the ‘Show Details’ link is activated, including some content in the ‘Cookie Declaration’ and ‘About’ tabs, is partly cut off. This fails WCAG 2.2 success criterion 1.4.4 Resize Text.
  • At 400% zoom the cookie banner is partly cut off, with the ‘Show Details’ link and the content below this link when activated no longer being visible. On a small screen (320×256) the ‘Show Details’ link is visible, but the content available when the link is activated is not. This fails WCAG 2.2 success criterion 1.4.10 Reflow.

Cookiebot are aware of these issues, but they have no plans to fix them. Therefore, we are looking for an alternate supplier which meets WCAG 2.2 AA legislation. This will be ongoing until contract renewal in February 2025.

Links

  • Some link text is not informative (e.g Find out more). This fails WCAG 2.2 success criterion 2.4.4 Link Purpose – In Context. 

We will fix any link or text we find that fails this criterion as we review sections of the site. This will be ongoing until contract renewal in February 2025.

Navigation

  • There are not enough options to explore the website for people with visual or cognitive disabilities. This fails WCAG 2.2 success criterion 2.4.5 Multiple Ways.

This is a technical limitation of our website. We will look into fixing this at the next contract renewal in February 2025.

Menu

  • At 400% zoom, some menu text and symbols overlap This fails WCAG 2.2 success criterion 1.4.10 Reflow.

This is a technical limitation of our website. We will look into fixing this at the next contract renewal in February 2025.

Keyboard Focus

  • When the cookies banner is present, the focussable elements in the footer are not visible when receiving focus. This fails WCAG 2.2 success criterion 2.4.11 Focus Not Obscured (Minimum).

We are looking for an alternate supplier for our Cookiebot, and will ensure focussable elements in the footer are visible and meet WCAG 2.2 AA legislation. This will be ongoing until contract renewal in February 2025.

  • On Our People page, when an individual person’s profile is open, the focussable elements on the background are not visible when receiving focus. This fails WCAG 2.2 success criterion 2.4.11 Focus Not Obscured (Minimum).

We are working alongside external software developers to address this issue at the next contract renewal in February 2025.

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

PDFs and other documents

Our older PDFs and Word documents do not meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader.

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.

Any new PDFs or Word documents we publish will meet accessibility standards.

Embedded Google Maps

We use Google Maps on the site. We are aware of some accessibility issues with them: controls missing accessible names, pins missing alternative text, some text being clipped when resized, and controls missing keyboard focus indicator.

These issues lie within Google’s coding, therefore we cannot change them. However, we only use Google Maps to provide a visual enhancement of information, and this information is presented as accessible text descriptions.

Embedded Forms

We sometimes use embedded forms on the site. We are aware of some accessibility issues with them: fields missing keyboard focus indicator, some fields missing autocomplete, screen reader not announcing when the form has been submitted successfully. These are third-party forms and we cannot address the issue within them.

Cookies table

The headings of the cookies table on the Privacy and Cookies page are cut off at 400% zoom. The table is automatically handled by Cookiebot and we are unable to fix this.

Cookies table

The headings of the cookies table on the Privacy and Cookies page are cut off at 400% zoom. The table is automatically handled by Cookiebot and we are unable to fix this.

Disproportionate burden claim

There are issues with our cookie bot as a website cookie provider.

It is highlighted there is an issue when using a small screen (320×256) where the ‘Show Details’ link is visible, but the content available when the link is activated is not.

It is also known that at 200% zoom the bottom of the cookie banner available when the ‘Show Details’ link is activated, including some content in the ‘Cookie Declaration’ and ‘About’ tabs, is partly cut off.

In addition, at 400% zoom the cookie banner is partly cut off, with the ‘Show Details’ link and the content below this link when activated no longer being visible.

The problems noted above cannot currently be resolved with the current cookie provider.

We’ve assessed the cost of fixing the issues with navigation and accessing information. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in 4 months’ time.

Preparation of this accessibility statement

This statement was prepared on 27/08/2024. It was last reviewed on 30/10/2024.

This website was last tested on 27/08/2024 against the WCAG 2.2 AA standard. The test was carried out by Binary Vision. 

The most viewed pages were tested using tools such as WAVE and Lighthouse (to test coding elements), WebAIM contrast checker (to test the contrast levels between colours) and NVDA and JAWS (to test the screenreader experience). Some further manual tests were carried out.