Accessibility Statement



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

We want everyone to be able to use our website but are aware that some people with disabilities may experience difficulties. We are very sorry about this and will do everything we can to help you as we work to resolve the issues.

If you find that you are unable to access any information on this website, please contact us using any of the following methods:
   
 

How accessible this website is


We know some parts of this website are not fully accessible: 
 
  • There is no inclusion of a site map
  • There is no facility to change the contrast of each web page
  • There is no facility to change the text size of each web page
  • There are no skip links
  • There are overlays used on this website, which are not fully accessible
  • The main navigation style could be confusing for some visitors
  • There are forms on this website that are not possible to use with some types of assistive technology
  • There is a time limit for filling in forms of 60 minutes, which may prove challenging
  • Some pages do not respond accurately to navigation with assistive technology such as dictation
  • Links within pages may be difficult to notice
 


Reporting accessibility problems with this website


If you find any other problems or issues with using this website or if you can make further suggestions to improve its accessibility, please contact us using one of the following methods:
   
 

Compliance status


This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 A standard, AA standard and AAA standard. 

Non-accessible content

A detailed audit of this website has been carried out and each page has been tested for the following areas. Each of these either directly or indirectly affect the accessibility of the website. 
 
  • Website Accessibility Errors Priority A
  • Website Accessibility Errors Priority AA
  • Website Accessibility Errors Priority AAA
  • Website Accessibility Errors for Screen Readers
  • Website Coding Errors that affect Search Engines
  • Website Coding Errors (W3C Standards)
  • Usability and Navigation Issues
In addition, a thorough manual evaluation by people with disabilities of different aspects of this website has been undertaken.

The content listed below is non-accessible on one or more website pages for the following reasons. 
 
Non-compliance with the accessibility regulations (WCAG 2.1)

Priority A

Word document contains a graphic without Alt Text.
(fails under WCAG 2.1 A 1.1.1 Section 508 (2017) A 1.1.1 )
 
The aria-labelled by attribute must point to IDs of elements in the same document.
(fails under WCAG 2.1 A 1.3.1 Section 508 (2017) A 1.3.1 ARIA 1.1  )
 
PDFs must be tagged to be accessible by screen readers.
(fails under WCAG 2.1 A 1.3.1 Section 508 (2017) A 1.3.1 Matterhorn 1.02 01-005 )
 
Word document contains a non-inline graphic or object.
(fails under WCAG 2.1 A 1.3.2 Section 508 (2017) A 1.3.2 )
 
Use the lang attribute to identify the language of the page.
(fails under WCAG 2.1 A 3.1.1 Section 508 (2017) A 3.1.1 Matterhorn 1.02 11-001 )
 
The element form must not appear as a descendant of the form element.
(fails under WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 )

CSS positioning can make pages unreadable when style sheets are turned off.
(fails under WCAG 2.1 A F1 Section 508 (2017) A F1 )
 
Document title must not be blank.
(fails under WCAG 2.1 A F25 Section 508 (2017) A F25 Matterhorn 1.02 06-004 )
 
alt text should not contain placeholders like 'picture' or 'spacer'.
(fails under WCAG 2.1 A F30 Section 508 (2017) A F30 )
 
alt text should not be an image file name.
(fails under WCAG 2.1 A F30 Section 508 (2017) A F30 Matterhorn 1.02 13-004 )
 
An image with a null alt attribute should not have title, aria-label or aria-labelled by attributes.
(fails under WCAG 2.1 A F39 Section 508 (2017) A F39 )
 
Several links on a page share the same link text and surrounding context, but go to different destinations.
(fails under WCAG 2.1 A F63 Section 508 (2017) A F63 )
 
Figures and images in PDF documents should have non blank ALT text, except for decorative images which should be marked as artefacts.
(fails under WCAG 2.1 A F65 Section 508 (2017) A F65 Matterhorn 1.02 13-004 )
 
HTML form control has no accessible name.
(fails under WCAG 2.1 A F68 Section 508 (2017) A F68 )
 
Removing the underline from links makes it hard for colour-blind users to see them.
(fails under WCAG 2.1 A F73 Section 508 (2017) A F73 )
 
Each a element must contain text or an img with an alt attribute.
(fails under WCAG 2.1 A F89 Section 508 (2017) A F89 )
 
Identify row and column headers in data tables using th elements, and mark layout tables with role=presentation.
(fails under WCAG 2.1 A F91 Section 508 (2017) A F91 )
 
We aim to resolve these issues as soon as possible.
 
 
Priority AA

Radio buttons with very generic labels need to be enclosed in a fieldset with a legend explaining the label.
(fails under WCAG 2.1 AA 2.4.6 Section 508 (2017) AA 2.4.6 )

The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline.
(fails under WCAG 2.1 AA F78 Section 508 (2017) AA F78 )

Headings should not be empty.
(fails under WCAG 2.1 AA G130 Section 508 (2017) AA G130 )

We aim to resolve these issues as soon as possible.
 
 

General website content



PDFs and other documents

The PDFs and other documents on this website may not be accessible. For example, they may be missing clear and simple document structure and missing text alternatives.
 
AAA Standard

Some pages have the following issues that fail the 'AAA' standard of the WCAG Guidelines. This is not currently a requirement but we include as it would be good practice to eliminate these in the future:
Several links on a page share the same link text, but go to different destinations.
(fails under WCAG 2.1 AAA 2.4.9 )

This page is hard to read for users with learning disabilities or reading disorders like dyslexia.
(fails under WCAG 2.1 AAA 3.1.5 )

Avoid specifying a new window as the target of a link with target=_blank.
(fails under WCAG 2.1 AAA F22 )

Link uses general text like 'Click Here' which doesn't explain link purpose.
(fails under WCAG 2.1 AAA F84 )

Many people with cognitive disabilities (including dyslexia) find text styled with text-align:justify hard to read.
(fails under WCAG 2.1 AAA F88 )
 
Although these issues are not a requirement, we aim to resolve as many of these issues as possible.

The following issues may occur with screen readers:
An element placeholder link with no event handler or href attribute does not work in some screen readers.
 

How this website was tested


This website was tested for compliance with the Web Content Accessibility Guidelines V2.1 level A, level AA and AAA using a variety of software and extensive manual checking.
 
 

What we’re doing to improve accessibility


We are working to fix issues which fail the Web Content Accessibility Guidelines version 2.1 A and AA as soon as possible.

We will update the accessibility statement when issues are fixed or when we expect them to be fixed. 
 


Preparation of this accessibility statement


This statement was originally prepared on 19th June 2022.
The website was last tested on 19th June 2022.

The test was carried out by Clive Loseby and the Website Accessibility Audit Team from Access by Design. Each member of the team has significant and different disabilities and uses assistive technology.

The full Audit, along with this Accessibility Statement, was prepared and produced by Clive Loseby, Access by Design. If you would like a copy of the audit, please contact us.

Last updated 19th June 2022.