This website is run by Police Ombudsman for Northern Ireland. We want as many people as possible to be able to use this website and this is why we have included additional features for accessibility:
- Resizeable text functionality
- Browsealoud, a web accessibility toolbar that provides a host of functionality including:
- A hover to speak function
- A translation tool
- Text to speech tool
- Text magnifier
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website because we want as many people as possible to be able to use it. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:
Information Directorate, Office of the Police Ombudsman.
Tel. 028 9082 8746
Technical information about this website’s accessibility
The Police Ombudsman’s Office is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
1. A small number of images do not yet have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.0 success criterion 1.1.1 Non-text content
We plan to add text alternatives for all images by 31 October 2020. When we publish new content we’ll make sure our use of images meets accessibility standards
2. Some input fields in our online forms do not have labels programmatically associated to them and others are not programmatically grouped.This can make it difficult for a person who uses a screenreader to understand what they should input into a field as the label is not programmatically associated to it. This fails WCAG 2.0 success criterion 1.1.1 Non-text content, 1.3.1 Info and Relationships and 4.1.2
We plan to fix these issues by 31 October 2020. When we publish new content we’ll make sure our forms are designed and coded so they meet accessibility standards
3. Some pages have skipped heading levels. This makes it difficult for people using a screen reader to navigate around a page. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships.
We plan to fix this issue by 31 October 2020. When we publish new content we’ll make sure to structure our web pages so they meet accessibility standards
4. There are tables presented on our website that are for presentation purposes and don’t hold tabular data but are not marked-up appropriately for accessibility. A table located on our “Website Privacy Notice” page needs table headers added to it to ensure screen readers can communicate what is being presented correctly. When tables haven’t been marked up correctly for accessibility it can make it difficult for a person who uses a screen reader to understand what is being presented. This fails WCAG 2.0 success criterion 1.3.1 Info and Relationships.
We plan to fix this issue by 31 October 2020. When we publish new content we’ll make sure our tables are designed and coded so they meet accessibility standards.
5. Some text links on our website are not easy to distinguish amongst surrounding body copy. This fails WCAG 2.0 success criterion 1.4.1 Use of Colour
We plan to adjust the colour of these text links to meet the required contrast and add a differentiator such as an underline on focus and by 31 October 2020.
6. Some text on our website does not have sufficient contrast against the background. Some of our links do not have sufficient contrast against the surrounding text. This can make it difficult to read for people with low vision or visual impairments to read the content presented and to identify links amongst body copy text. This fails WCAG 2.0 success criterion 1.4.3 Contrast (Minimum).
We plan to adjust the colour of our text or backgrounds by 31 October 2020 to ensure there is a sufficient contrast ratio between the two.
7. On our “Statistics Feedback” page there is a dynamic security verification image that contains characters that users need to enter into a field before submitting the form. Because this is an image, screen readers users won’t be able to interpret the characters and as a result, screen reader users won’t be able to submit the form. This fails WCAG 2.0 success criterion 1.4.5 Images of Text.
We plan to fix this issue by 31 October 2020 to ensure screen reader users can provide their feedback via the form.
8. The dropdown navigation cannot be dismissed by keyboard alone. This can be difficult for keyboard only users as some of the dropdown elements obscure other content on the page. This fails WCAG 2.0 success criterion 1.4.13 Content on Hover or Focus.
We plan to fix this issue by 31 October 2020 to ensure keyboard users are able to dismiss the dropdown navigation.
9. Not all page functionality is available using the keyboard. The dropdown items in the Global Navigation, some expandable content (accordion), modals and tooltips cannot be accessed using the keyboard alone. This means that some content on our website will not be accessible to keyboard only users. This fails WCAG 2.0 success criterion 2.1.1 Keyboard.
We plan to fix this issue by 31 October 2020 to ensure keyboard users are able to access and interact with all content on our website.
10. The order of focus on our website for someone who uses a keyboard can be confusing as the focus jumps around unexpectedly and doesn’t always move to the next most logical element on the page. This fails WCAG 2.0 success criterion 2.4.3 Focus Order.
We plan to fix this issue by 31 October 2020 to ensure the order of focus is logical and meets the expectation of keyboard users.
11. A small number of our text links are not easily understood without further context. This can make navigating our website difficult for keyboard users where the purpose of a link is not clear. This fails WCAG 2.0 success criterion 2.4.4 Link Purpose.
We plan to fix this issue by 31 October 2020. When we publish new content we’ll make sure the purpose of text links we include are clear.
12. On our website we have some content published in different languages but no language attributes have been defined for the content. This can make understanding the content for screen reader users difficult as without the language defined the screen reader may not pronunciate the content correctly. This fails WCAG 2.0 success criterion 3.1.2 Language of Parts.
We plan to fix this issue by 31 October 2020. When we publish new content we’ll make sure any language variations presented have the correct language attribute.
13. The error validation on our forms needs improvement as it lacks clarity around what the user is required to do in order to successfully complete the forms. This can make filling in a form for screen reader users. This fails WCAG 2.0 success criterion 3.3.1 Error Identification & 3.3.3 Error Suggestion.
We plan to fix this issue by 31 October 2020 so that users are able to understand the error validation messages presented and successfully submit forms.
14. There is a title missing from an embedded Google map on our website. Without a title, a screen reader user may find it difficult to understand what is being presented to them. This fails WCAG 2.0 success criterion 1.1.1 Non-text content and 4.1.2 Name, Role, Value
We plan to fix this issue by 31 October 2020. When we publish new, embedded content we will make sure it has the required accessibility markup to meet accessibility standards.
Some of our PDFs accessible via our website do not current meet accessibility requirements. We are currently working on these to make sure they meet accessibility requirements and so far we have added alt text to many of the images and graphs contained in PDFs published since September 2018. By 31 October 2020 we plan to fix all other accessibility issues present in any of our PDFs published since September 2018.
Any new PDF documents we publish will meet accessibility standards.