This accessibility statement applies to content published on the Child Friendly Leeds domain.
This website is run by the Web Team. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels, and fonts using browser extensions
- use this website on most modern browsers and devices
- navigate most of the website using only a keyboard
- navigate most of the website using a screen reader
- navigate most of the website using speech recognition software
- zoom in up to 200 percent without the text spilling off the screen
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:
· our website has many instances of insufficient colour contrast which can make it difficult to read the content.
Feedback and contact information
If you need information on this website in a different format email
firstname.lastname@example.org and tell us:
- the web address (URL) of the content
- your name and email address
- the format you need, for example, audio CD, braille, BSL or large print, accessible PDF
Reporting accessibility problems with this website
If you find any problems that are not listed on this page or you think we're not meeting the accessibility requirements, email
If you contact us with a complaint and you're not happy with our response contact the Equality Advisory and Support Service (EASS)[CK5] .
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')
Technical information about this website's accessibility
The Digital Access Team 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Invalid HTML mark-up
Some pages on our website have multiple instances of the same ID. The ID attributes is used to identify a component on the page and although you can have as many IDs on a page as you like each ID should be unique. IDs can be used to link to a certain point in the page and multiple use of this could cause confusion. One of the IDs being specified multiple times is "DataProvider". This fails WCAG 2.1 success criteria 4.1.1 Parsing (A).
Some text on our website doesn't have enough colour contrast against the background colour behind it. This can make the text hard to read for users with low vision or colour blindness. Some areas affected are:
- the white text sitting on an orange background in the navigation
- the orange text sitting on an orange background when we show global alerts
- the white text on orange and yellow buttons across our site
- the back to top button across our site
- the text above hero banners across our site
This fails WCAG 2.1 success criteria 1.4.3 Contrast (minimum) (A).
Images with no alternative text or not marked as decorative
Some images on our website are missing alternative text, haven't being marked as decorative or haven't included relevant information in the alternative text. Alternative text is used to describe the purpose of the image to visitors who are unable to see them. This can include screen readers and browsers that block images.
If an image is purely decorative then an alt tag should be included but left empty. This allows assistive technology to understand the image is there for decorative purposes. If an image serves a purpose (such as explaining what an entrance of a building looks like) then we must include descriptive alternative text.
Some of the images affected are:
- SharePoint sprite which is not visible on the front-end of the website but is present in the code
- on the
CFL is 5 page is an image full of text as the information is already described on the page the image alt tag should be left empty
- on the CFL is 5 page is an image of a map and the alternative text is the URL of the image
This fails WCAG 2.1 success criteria 1.1.1 Non-text content (A).
Some areas of our website don't have headings nested in a hierarchical order.
Headings are used to communicate the structure of the page content and should never skip a level, e.g. you shouldn't go from an h2 to an h4 when reading the content.
This fails WCAG 2.1 success criteria 2.4.6 Headings and labels (AA).
homepage hero banner is contained with a HTML list but doesn't have the appropriate list item HTML mark-up inside it. This issue also occurs on the
Find out more page. List items can be used to tell screen reader users how many items are in the list.
This fails WCAG 2.1 success criteria 1.3.1 Info and relationships (A).
The text "We're working to bring everyone together to make Leeds a child friendly city" in the header is included via CSS and not HTML mark-up. This text cannot be read by screen reader users due to the way it has been included.
This fails WCAG 2.1 success criteria 1.1.1 Non-text content (A) and 1.3.1 Info and relationships (A).
In the ambassadors section of the homepage is links with no text inside them. A screen reader may still announce a link is present but not describe the purpose of the link.
This fails WCAG 2.1 success criteria 2.4.4 Link purpose (in context) (A) and 4.1.2 Name, Role, Value (A).
Content that's not within the scope of the accessibility regulations
Preparation of this accessibility statement
This statement was prepared on 20 August 2020. It was last reviewed on 25 April 2022.
This website was last tested on the 28 July 2020. The test was carried out by the Web Design Team at Leeds City Council.
We tested a selection of pages, ensuring those tested reflected the variety of different page layouts used on our website.
The pages we tested were: