Accessibility statement for Worcestershire County Council job application system.

This applies to web pages within https://worcestershire.wm-jobs.co.uk/members/index.php

This website is run by Worcestershire County Council using external software produced by Tribepad. This statement applies to all candidate processes used to register and apply for a job.

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 or device settings.
Zoom in up to 300% without the text spilling off the screen.
navigate most of the website using a keyboard or speech recognition software.
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.

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@worcestershire.gov.uk

Call: 01905 846666

Team: Worcestershire County Council Recruitment Team

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@worcestershire.gov.uk

Call: 01905 846666

Team: Worcestershire County Council Recruitment Team

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

Worcestershire County Council is 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

Some content on the application summary page may appear disjointed when zoomed in above 200%. Users with low vision who rely on zoom functionality may experience readability and usability issues, making it harder to review application details. WCAG Reference: 1.4.4 (Resize Text) | Proposed Fix Date: May 2025
The input field in the registration questionnaire has a broken aria-labelledby reference due to missing guidance, although a visible label is present. This can cause confusion for screen reader users who rely on proper ARIA associations to understand form fields. WCAG Reference: 1.3.1 (Info and Relationships) | Proposed Fix Date: May 2025
Action buttons on the questionnaire pages are not positioned consistently with the rest of the application process, which may confuse users who rely on familiar navigation patterns. Inconsistent UI layouts can be especially challenging for users with cognitive disabilities or assistive technology.WCAG Reference: 3.2.3 (Consistent Navigation) | Proposed Fix Date: May 2025
Helper question marks do not have screen reader-accessible text, even though they can be accessed with a keyboard. This means visually impaired users relying on screen readers may not receive any useful information when focusing on these icons, limiting their ability to understand the provided help content. WCAG Reference: 1.3.1 (Info and Relationships) | Proposed Fix Date: May 2025
The job search menu is a mix of role tabs and presentation elements, which makes it unclear and difficult to navigate using assistive technology. Screen readers may not properly interpret the structure, making it harder for users to understand and interact with the menu. WCAG Reference: 1.3.1 (Info and Relationships) | Proposed Fix Date: May 2025
The "delete saved search" confirmation dialog cannot be accessed via keyboard, preventing users who rely on keyboard navigation from completing the deletion process. WCAG Reference: 2.1.1 (Keyboard Accessibility) | Proposed Fix Date: May 2025
When zoomed to 400%, reflow issues cause page content to become unreadable, making it difficult for users with low vision to access critical information. WCAG Reference: 1.4.10 (Reflow) | Proposed Fix Date: May 2025
Reference input fields contain broken or orphaned labels, preventing screen readers from properly associating labels with inputs, which makes form completion challenging. Similarly, the bank details input fields (and possibly other workflows) also have broken labels, creating difficulties for users with screen readers. WCAG Reference: 3.3.2 (Labels or Instructions) Proposed Fix Date: May 2025
The next steps in the onboarding workflow appear as disabled buttons but can still be focused, confusing users who might assume they can be activated. WCAG Reference: 4.1.2 (Name, Role, Value) | Proposed Fix Date: December 2025
On the E-sign contract view, some labels are missing or not properly associated with their fields, so screen readers might not know the right information needed. WCAG Reference: 1.3.1 (Info and Relationships), 4.1.2 (Name, Role, Value) | Proposed Fix Date: 2025
The option to use 'magic links' to log in does not provide enough guidance, leading to a poor user experience. Users, especially those with cognitive disabilities or unfamiliar with the feature, may struggle to understand how the process works or what to expect. WCAG Reference: 3.3.2 (Labels or Instructions) | Proposed Fix Date: May 2025
If the magic link has expired, the default translation states, “The magic link has expired or has already been used. Click here to login again.” The link is only on the word "here," which provides no meaningful context for screen readers, making it difficult for visually impaired users to understand its purpose. WCAG Reference: 2.4.4 (Link Purpose) | Proposed Fix Date: May 2025
The add and edit buttons cannot be accessed using a keyboard, preventing users with motor impairments or those relying on keyboard navigation from interacting with these essential controls. Additionally, missing labels or ARIA labels on input fields prevent screen readers from providing context, making form completion difficult for visually impaired users. WCAG Reference: 2.1.1 (Keyboard Accessibility), 3.3.2 (Labels or Instructions) | Proposed Fix Date: May 2025

Preparation of this accessibility statement

This statement was prepared on January 14, 2025, and last reviewed on the same date following bug fixes.

The website was last tested in January 2025 against WCAG 2.2 AA standards.
The next scheduled testing is in January 2026 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.