Accessibility Statement

This accessibility statement applies to www.policepensioninfo.co.uk

This website is run by the NPCC pensions team. We want as many people as possible to be able to use this website. For example, that means you should be able to:
– zoom in up to 300% without the text spilling off the screen
– navigate most of the website using just a keyboard
– listen to most of the website using a screen reader

We’ve also tried to make 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 some parts of this website are not fully accessible:

– some documents are in PDF format and may not be fully accessible to screen reader software

– some pages and document attachments may not be clearly written due to the technical nature of the subject

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email npccpensions@npcc.police.uk

We’ll consider your request and get back to you in 5 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: npccpensions@npcc.police.uk

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

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

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

Many of 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. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

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.