Accessibility statement for Liverpool City Council job application system

This applies to web pages within AbilityNet has advice on making your device easier to use if you have a disability.

Feedback and contact information

If you find any issues not listed on this page or think we’re not meeting accessibility requirements, please contact:

Email - recruitment@liverpool.gov.uk

Call - 0151 351 0504

Write to - Liverpool City Council, Cunard Building, Water Street, Liverpool, L3 1AH

Help with your application

If you need any information on this website in an alternative format or further assistance with an application, please contact our recruitment team at:

Email - recruitment@liverpool.gov.uk

Call - 0151 351 0504

Write to - Liverpool City Council, Cunard Building, Water Street, Liverpool, L3 1AH.

We’ll consider your request and get back to you as soon as possible.

What we’re doing to improve accessibility

All candidate processes are tested internally on an annual basis, using accessibility tools and assistive technology to help meet standards. Tribepad also tests with real users and requests feedback about the experience of job applicants to improve the user experience.

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

Liverpool City Council are committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

How accessible this website is

We know some parts of this website are not currently fully accessible or could be easier to use:

  • Some older PDF documents are not fully accessible to screen reader software due to missing titles.

  • Some links are not clearly identifiable as tabbed content.

  • Magic links login does not offer enough help or guidance.

  • Some links are missing readable text as icon buttons.

  • Focus order may be interrupted when using some modals.

  • The structure of some page content headings could be presented in a more logical order.

  • Some page titles could provide more context for the content.

  • Some layouts may appear broken when zooming in above 200% on a mobile device.

Compliance status

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

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

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG 2.1 AA standards.

If you find something that does not work that we missed, remember to contact us.

The content listed below is non-accessible for the following reason(s):

Non-compliance with the accessibility regulations

  • Residential History – Date Gap Focus Management (All Devices) After adding or editing residential history, keyboard focus jumps to the end of the page rather than returning to a logical position. This may make navigation difficult if you’re using a keyboard or assistive technology, as you may need to navigate back through the page to continue your task. WCAG Reference: 2.4.3 (Focus Order) | Proposed Fix Date: November 2026

  • Application Questionnaires – Grid questions descriptions (All Devices) Within application questionnaires, grid checkboxes use malformed aria-described by attributes that do not correctly reference their associated row and column headers. This may prevent screen readers from announcing the correct contextual information for each checkbox, making the questionnaire harder to understand and complete. WCAG Reference: 1.3.1 (Info and Relationships) | Proposed Fix Date: November 2026

  • Application Questionnaires – Radio Button Group Structure (All Devices) Within application questionnaires, radio button question groups are not wrapped in fieldset elements. This reduces semantic clarity for screen reader users, as the relationship between the question and available answers may not be clearly communicated. WCAG Reference: 1.3.1 (Info and Relationships) | Proposed Fix Date: November 2026

  • Onboarding – Section Navigation Keyboard Access (All Devices) On the onboarding index, the section navigation arrows cannot be accessed using keyboard input due to the use of a role="presentation" attribute. This may prevent keyboard-only users from navigating between onboarding sections. WCAG Reference: 2.1.1 (Keyboard) | Proposed Fix Date: November 2026

  • Candidate Profile – ‘Currently Employed By’ Focus Management (All Devices) When editing the ‘Currently employed by’ section within the profile area, keyboard focus is not moved to the appropriate starting point. This may create confusion if you’re using a keyboard or screen reader, as it may be unclear where interaction should continue after entering edit mode. WCAG Reference: 2.4.3 (Focus Order) | Proposed Fix Date: November 2026

  • Profile Builder – Date Selection (All Devices) On the profile builder, the date selection fields use placeholder text instead of proper labels, which may be confusing if you’re using a screen reader. The placeholder text is read out even as you start typing, which can cause confusion or make it unclear what information you are entering. WCAG Reference: 3.3.2 (Labels or Instructions) | Proposed Fix Date: November 2026

Preparation of This Accessibility Statement

This statement was prepared on May, 2026, and last reviewed on the same date following bug fixes.

  • The website was last tested in January 2026 against WCAG 2.2 AA standards.

  • The next scheduled testing is in January 2027 or when new functionality is released.

  • Candidate processes are tested annually or when new developments are implemented.

Testing Approach
Accessibility tests are performed manually using tools such as WebAim, WAVE, Lighthouse, and VoiceOver by our website team. Usability tests are also conducted with users who rely on assistive technologies. These tests are carried out by Tribepad.