Accessibility statement

Last updated on 20 November 2019

Leeds City Council is committed to making our websites accessible. We want as many people as possible to be able to use this website.

This means you should be able to:

  • change line height, spacing between paragraphs 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 (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet external link has advice on making your device easier to use if you have a disability.

Our accessibility issues

We know some parts of this website aren’t fully accessible, for example:

  • many online forms are not currently easy for screen readers to navigate
  • most documents aren’t accessible to screen reader software - our aim is that all documents will meet our website's content standards and the accessibility regulations by September 2020
  • some links on our website aren’t self-explanatory to screen reader users
  • we might link to websites or software we do not own or manage and cannot guarantee their accessibility 

Reporting accessibility problems with this website

We're working to improve the accessibility of our website, but if there's anything which you'd like us to prioritise please email us and let us know:

We’ll consider your request and get back to you in three working days.

The Equality and Human Rights Commission is responsible for enforcing the accessibility regulations for the council and other public sector bodies. If you’re not happy with our response, contact the Equality Advisory and Support Service.

Technical information about this website’s accessibility

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non accessible content

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

HTML validation

Our website fails to validate using W3C Markup Validation Service. This means that some assistive technologies may not be able to interpret the content accurately. This doesn’t meet WCAG 2.1 success criterion 4.1.1 (parsing).               

We are continuously working towards ensuring our website passes W3C validation tool and we will ensure any new content or components we build meet accessibility standards.               


Headings are missing text

There are instances of empty heading tags being used on our website. These are not visible on the front-end of the website but are hidden in the code. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (info and relationships).                


Multiple instances of the same ID

Each page of our website has multiple elements with the same ID value. A singular webpage may contain one ID per element but the value for each ID must be unique. The ID value specified multiple times is called “DataProvider”. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Info and Relationships and 4.1.1 (Parsing).             


Link text

Some of the links on our website do not make sense when taken out of context. For example, the A to Z links in the footer read out as “A link” to screen reader users. We also have a couple of instances where the same link text is used for links that take users to different locations. These issues do not meet WCAG 2.1 success criterion 2.4.4 Link purpose (in context). We are continuously working to improve our link text by adding in screen reader friendly text where necessary and performing content reviews and re-designs.                


Missing button on forms

The mark-up of our pages are built on forms due to the platform we use. As a result of this each page is technically missing a button and although it has no impact on a user it does fail validation. This doesn’t meet WCAG 2.1 success criterion 3.2.2 On Input and 4.1.2 (Name, Role, Value).                


Feedback form

Our feedback form includes a label that is not connected to a form field and has no content inside it until the submit button is pressed. When content does appear it displays an error message, this is using the incorrect mark-up. This fails WCAG 2.1 success criterion 1.3.1 Info and relationships, 2.4.6 Headings and labels and 4.1.2 (Name, Role, Value).                


Google Captcha

We use Google Captcha on our feedback form to prevent us from receiving spam.                

We are aware of a few technical issues with Google Captcha such as a text area having no description, a local link destination not existing, an iframe being used to format content and the iframe having no title. This fails WCAG 2.1 success criterion 1.3.1 Info and relationships, 3.3.2 Labels or instructions and 4.1.2 (Name, Role, Value).                

We have tested Google Captcha on various devices and browsers, using keyboard only and on screen readers where we found it to still function well. Google Captcha has become commonplace across many websites and most of our users are familiar with it. Due to this, we have no plans to replace it.                

Google Captcha is exempt from meeting the accessibility regulations because it is neither funded, developed by, or under the control of Leeds City Council.               


How we tested this website

This website was last tested on 29 August 2019.

We tested a selection of our most popular pages, ensuring those tested reflected the variety of different page layouts used on our website.

The pages we tested were: