Accessibility

This accessibility statement applies to the Sussex Police and Crime Commissioner website.

This website is run by the office of the Sussex Police and Crime Commissioner. 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 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)

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.

We know some parts of this website are not fully accessible:

  • you cannot modify the line height or spacing of text
  • most older PDF documents are not fully accessible to screen reader software
  • the map in the ‘Your Area’ section of the Police and Crime Commissioner website is not scrollable with a keyboard
  • some of our online forms are difficult to navigate using just a keyboard

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: pcc@sussex-pcc.gov.uk
  • call: 01273 481561
  • post: OSPCC, Sackville House, Brooks Close, Lewes, BN7 2FZ

We’ll consider your request and get back to you in 20 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: pcc@sussex-pcc.gov.uk or isabel.fitzgibbon@sussex-pcc.gov.uk or call: 01273 481561.

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

The office of the Sussex Police and Crime Commissioner is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

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

Non-accessible Content:

This area will be updated if internal audits flag up non-accessible content. 

 

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

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and 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 do not plan to fix older Performance and Accountability Meeting minutes.

Guidance will be followed for any new PDF and Word documents published on the website to meet accessibility standards published after 01/02/23. PDFs before this date may not be accessible, but you can request an accessible document by request to: isabel.fitzgibbon@sussex-pcc.gov.uk. 

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Preparation of this website's accessibility statement 

This statement was prepared on 21st December 2022. It was last reviewed on 9th March 2023.

This website was last tested on 31st October 2022. The test was carried out by Thco.

The whole website was run through WAVE software to ensure compliance with accessibility standards.

You can read the full accessibility test report here. 

You can also read how we addressed these issues here.