Last updated on 13th May 2020

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 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:

  • we might link to websites or software we do not own or manage and cannot guarantee their accessibility
  • job description documents hosted on this site which are linked from the Cornerstone OnDemand system 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

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.

The below are technical issues relating to the sharepoint platform this site has been built on. Leeds City Council has begun the process of a platform change and this site will be migrated when it has been decided.

The below issues are what the site fails on WCAG2.1

id attribute value must be unique

Duplicate ID's can break the accessibility of labels for forms, table header cells, etc., by the second instance being skipped by screen readers, or by client-side scripts.

Elements must have sufficient colour contrast

Some people with low vision experience low contrast, meaning that there aren't very many bright or dark areas. Everything tends to appear about the same brightness, which makes it hard to distinguish outlines, borders, edges, and details. Text that is too close in luminance (brightness) to the background can be hard to read.

The following are best practice errors

accesskey attribute value must be unique

Specifying a accesskey attribute value for some part of a document allows users to quickly activate or move the focus to a specific element by pressing the specified key (usually in combination with the alt key). Duplicating accesskey values creates unexpected effects that ultimately make the page less accessible.

Text of buttons and links should not be repeated in the image alternative

It is unnecessary and potentially confusing to have alternative text for a link or image to be repeated in text adjacent to the link or image since it would be read twice by a screen reader.

Ensures landmarks are unique

landmark-unique is a new best practice rule ensures that landmarks have a unique role or accessible name (i.e. role, label, title) combination.

All page content must be contained by landmarks

Navigating a web page is far simpler for screen reader users if the content splits between multiple high-level sections. Content outside of sections is difficult to find, and the content's purpose may be unclear.

Cornerstone OnDemand

Cornerstone OnDemand enlists the help of DAC, leaders in compliance, to satisfy WCAG 2.1 and accessibility standards and any VPAT requests.

The ‘Search Candidates’ and ‘Manage Requisition’ pages have multiple barriers to accessibility which may prevent screen reader users and users who cannot use a mouse from interacting with the content.

Screen reader users may encounter issues as there are form elements that do not have a programmatically associated label and there are also links which do not have a descriptive text element.

There are grouped form elements which are not labelled correctly, users who rely on audio feedback may not be aware of the relationships between the input fields.

Aria has been used incorrectly on some elements, which may prevent users who rely on audio feedback from interacting with the elements. There are also elements that have duplicated ID’s which may prevent assistive technology from interacting with the element with the duplicated ID correctly.

Pages are present which do not have a heading structure and some pages have an illogical heading structure.

Users who cannot use a mouse may find that there are elements that are not accessible to users who cannot use a mouse and the tab order of some pages is not logical. There are also elements which have no visible focus highlighting mechanism. There is a modal present that has an internal scroll which users who cannot use a mouse will not be able to interact with.

Some link text has no visible indicator, such as an underline and the colour contrast ratio from the surrounding text is not sufficient. Some users may not be aware that the elements are links.

Cornerstone are aware of the issues and are working towards a resolution.

Please find the audit for the recruitment section.

Contact us

To advertise a job vacancy with us, call 0113 378 5216

If you have any questions about vacancies, contact our recruitment team on 0113 378 5165 or email

If your question is about a vacancy within a school, charity or other non-profit organisation vacancies, please contact them directly.

Search for jobs
Back to top