The Leeds City Council Source to Contract platform website is run by Leeds City Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- resize text without assistive technology up to 200 percent without loss of content or functionality
- navigate most of the website using a keyboard
- use this website on most modern browsers and devices
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:
- there are some sections with accessible names that do not include the text of their visual labels
- some interactive controls lack a visible focus indicator
- in some areas search term results appear but are not announced to screen reader users
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 CPU@leeds.gov.uk.
Feedback and contact information
If you need information on this website in a different format email CPU@leeds.gov.uk 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
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).
Technical information about this website’s accessibility
Leeds City 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons:
Non-compliance with the accessibility regulations
There is visually hidden content meant to be hidden from all users, but it can still be accessed by keyboard or screen reader users. Location: Header and Side Navigation This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
The login screen has a main landmark defined inside another main landmark. There are some headings with levels that do not match their visual level on the page and there are some empty table headers. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
There are interactive controls that cannot be navigated to and/or operated with the keyboard alone. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).
The registration and profile accessibility page titles insufficiently describe the page’s purpose. This fails WCAG 2.2 success criterion 2.4.2 (page titled).
When the user enters invalid data in an edit field and submits the form the alter changes the alert focus order. There are dialogs that do not receive focus when they appear. This fails WCAG 2.2 success criterion 2.4.3 (focus order).
The category selection and create RFQ form have insufficiently descriptive names. This fails WCAG 2.2 success criterion 2.4.4 (link purpose).
There are controls with accessible names that do not include the text of their visual labels. This fails WCAG 2.2 success criterion 2.5.3 (label in name).
The create RFQ form lacks text explaining that asterisks indicate required fields. This fails WCAG 2.2 success criterion 3.3.2 (labels or instructions).
Some areas of the website user interface components cannot be programmatically determined, including the tree view navigation in Main Organisation Data and category selection buttons. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
The login screen text does not meet the required minimum colour contract ration with its background. This fails WCAG 2.2 success criterion 1.4.3 (contrast minimum).
Some areas have content that overlaps or is cut off when viewing the page at 200% browser zoom. This fails WCAG 2.2 success criterion 1.4.4 (resize text).
Some areas have content that is cut off when the page has a viewport width of 320 CSS pixels. This fails WCAG 2.2 success criterion 1.4.10 (reflow).
User interface components on the login screen and buyer profile have a contrast ration below 3.00:1. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).
There are some interactive controls without a visible keyboard focus indicator. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).
There are search results that appear but are not announced to screen reader users. This fails WCAG 2.2 success criterion 4.1.3 (status message).
Disproportionate burden
Not applicable.
Content that’s not within the scope of the accessibility regulations
Not applicable.
What we’re doing to improve accessibility
Leeds City Council is working with its partner Jaggaer to ensure future releases address outstanding accessibility issues, with the next scheduled for January 2026.
Preparation of this accessibility statement
This statement was prepared on 17 November 2025.
This website was last tested in January 2025 against the WCAG 2.2 AA standard.
The test was carried out by Jaggaer t/a Bravo Solutions. Evaluation of the product involved a combination of automated, manual, and functional testing against the applicable success criteria within the Web Content Accessibility Guidelines WCAG) 2.2 Conformance Levels A and AA.
Level Access (Level) tested a selection of the product using a representative sample to cover the components and functionality of use flows. Below is a list of the assistive technologies (ATs) used:
- Chrome/NVDA
- VoiceOver/iOS
- VoiceOver/Mac
- ZoomText
- Accessible Color Picker
