Skip to main content

Accessibility

Accessibility Statement for Islington Directory

This statement applies to content published on https://directory.islington.gov.uk/kb5/islington/directory/home.page.

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:  

·       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 

·       listen to most of the website using a screen reader [NVDA] 

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. 

How accessible this website is

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 

·       some of our online forms are difficult to navigate using just a keyboard 

·       you cannot skip to the main content when using a screen reader  

How to request content in a different format

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: 

·       report it online using our contact form

·       call 020 7527 2000 or minicom 020 7527 1900 

·       if you use British Sign Language you can contact Islington Council using our Sign Language Interpreting Services. 

We’ll consider your request and get back to you in 10 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 us

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)

Contacting us by phone or visiting us in person

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

Technical information about this website’s accessibility 

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. 

Compliance status 

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances and exemptions are listed below. 

Non-accessible content 

The content listed below is non-accessible for the following reasons. 

Non-compliance with the accessibility regulations 

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.

Not all of our tables have headings or scope for headings. This fails WCAG 2.0 success criterion 1.3.1. We plan to address with by 14th February 2021.

Some of our Radio buttons or check boxes with the same name attribute are not contained within a fieldset element. This fails WCAG 2.0 success criterion 1.3.1. We plan to address with by 14th February 2021. 

Not all form fields have labels associated with them. This fails WCAG 2.0 success criterion 1.3.1. We plan to address with by 14th February 2021. 

Not all of our naviagation items are coded as lists. This fails WCAG 2.0 success criterion 1.3.1. We plan to address with by 14th February 2021. 

Not all form fields are correctly structured, which may make it more difficult for screenreaders 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 with by 14th February 2021. 

Some of our links are only distinguished by colour. This fails WCAG 2.0 A success criterion 1.4.1. We plan to address this by 14th February 2021.

Some of our text doesn’t sufficiently contrast with its background color, so that people with moderate visual impairments can read it. This fails WCAG 2.0 AA success criterion 1.4.3. We plan to address this by 14th February 2021. 

Some pages require zooming and 2D scrolling on small screens. This fails the WCAG 2.1 AA success criterion 1.4.10. We plan to address with by 14th February 2021. 

Some pages link to anchors that don’t exist WCAG 2.0 success criterion 2.4.1. We plan to address this by 14th February 2021. 

Some of our pages that contain an iframe don’t have a title. This fails WCAG 2.0 success criterion 2.4.1. We plan to address this by 14th February 2021. 

Not all controls change appearance when selected, this fails WCAG 2.0 AA success criterion 2.4.7  We plan to address this by 14th February 2021. 

Some of our links go the to the same destination with different link text, this text also isn’t always descriptive enough. This fail WCAG 2.1 AA this fails success criterion 1.4.10. We plan to address this by 14th February 2021. 

We don’t specify the language of every page. This fails WCAG A success criterion 3.1.1. We plan to address by 14th February 2021. 

Not all of our forms have a submit button. This fails WCAG 2.0 A success criterion 3.2.2. We plan to address this by 14th February 2021.  

Not all our links can we used by screen readers. This fails WCAG 2.0 success criterion 4.1.2. We plan to address with by end of January 2021.  

Some of our pages have duplicate ID’s. This fails WCAG 2.0 A success criterion 4.1.1. We plan to address this by 14th February 2021. 

We plan to add text alternatives for all images by February 2021. When we publish new content we’ll make sure our use of images meets accessibility standards. 

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. By February 2021, 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. 

Preparation of this accessibility statement 

This statement was prepared on 14 December 2020. It was last reviewed on 14 December 202.0 

This website was last tested on 10 December 2020. 

Themes

On this page you can adapt this website to meet your needs. The settings you create on this page will be saved for future visits. If you wish to return to the standard settings, click the "Reset settings" button.
Choose a theme:

Access Keys

We haven't used access keys as they can often interfere with the default keyboard shortcuts of modern browsers. The content is easily tab-navigable and screen-reader friendly. We have tried to make our site as accessible as possible.

Get help