This statement applies to content published on https://www.nrpfnetwork.org.uk/
This website is run by Islington Council. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:
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:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We’ll consider your request and get back to you in 10 working days.
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 us.
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).
We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.
Islington Council’s Customer Centre and the Town Hall have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out how to contact us
Islington Council 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 and exemptions listed below.
The content listed below is non-accessible for the following reasons.
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add text alternatives for all images December 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
Some of our more complex tables do not have table headings that are linked to the information they relate to. Fixing this will help screen readers describe the information to the user. This fails WCAG A success criterion 1.3.1. We plan to address this by December 2020.
Not all our tables have headings. This fails WCAG A success criterion 1.3.1. We plan to address this by December 2020.
Not all form fields are correctly structured, which may make it more difficult for screen readers to explain their purpose or browsers to help the user complete them. This fails WCAG AA success criterion 1.3.5. We plan to address this by December 2020.
On mobile view for some of our pages you need scroll in two directions to see all content. This fails WCAG AA success criterion 1.4.10. We plan to address this by December 2020.
Some of our link text isn’t described very well or we may use the same word for different destinations. This fails WCAG 2.0 A success criterion 2.4.4. We plan to address this by December 2020.
Some of our controls don’t change in appearance once they are selected. This fails WCAG 2.0 AA success criterion 2.4.7. We plan to address this by December 2020.
We don’t specify the language of our site on every page. This fails WCAG 2.0 success criterion 3.1.1. We plan to address this by December 2020.
A couple of our links can't be accessed by screen readers. This fails WCAG 2.0 success criterion 4.1.2. We plan to address this by December 2020.
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. By December 2020, we plan to either fix these or replace them with accessible HTML pages. 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.
This statement was prepared on 25 September 2020.
This website was last tested on 25 September 2020. The test was carried out by Islington Council using a combination of manual and automated testing.