Loading, please wait...

Accessibility statement for admin.trac.jobs

This accessibility statement applies to trac.jobs admin system.

This website is run by Civica UK Ltd.

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change font size
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of: JAWS, NVDA, 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.

How accessible this website is

We know some parts of this website are not fully accessible:

  • Logos do not have alt names
  • Auto-complete options are not voiced by screen-readers
  • Some fields do not have valid labels
  • Focus position is lost after updates to pages
  • TinyMCE fields are not keyboard accessible
  • Vacancy conversion report calendar arrows not read out by screen reader
  • Application search employment checks table
  • Dashboard page has several accessibility issues
  • "Unactioned communications" page has several accessibility failings
  • Login fields and some drop down select fields do not have visible labels
  • Calendar widgets are not fully keyboard accessible
  • Validation is not auto-focused on screenreaders
  • Home/To top menu button not keyboard accessible
  • User guide has several accessibility issues
  • Colour contrast ratio failures on site button borders
  • Tooltips are not hoverable or dismissible
  • Dragging element in Data download missing pointer alternatives
  • Colour contrast ratio failures on tables in hover/focus
  • Site map loses formatting on smaller screen widths

Feedback and contact information

If you have feedback you'd like to share with us relating to accessibility, please contact your recruitment support team or use the email address below.

Accessibility contact email
[email protected]

We will consider your request and get back to you within 10 working days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. Please contact us if you find any problems not listed on this page or think we’re not meeting accessibility requirements.

Please include details of the problem, for example:

  • the web address (URL) of the page you encountered the problem on
  • the web browser you are using (e.g. Internet Explorer, Chrome, Firefox, Safari)
  • any assistive technology you are using (e.g. screen-reader software)

We will investigate your report and get back to you within 10 working days.

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

Civica UK Ltd 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 not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances and exemptions are listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

  • Logos do not have alt names

    The Trac and Civica logos displayed on the site are missing alternative names.

    We plan to fix this issue by April 2025.

    WCAG 2.2 success criterion
    1.1.1 Non-text Content
    Level
    A
  • Auto-complete options are not voiced by screen-readers

    The auto-complete software package we use does not mark-up options properly, which prevents screen-readers from voicing them.

    In some cases, the auto-completes are for a text-value that can be fully entered without using the auto-complete functionality, however in others an option needs to be selected, so those will be inoperable until this issue is fixed.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    1.1.1 Non-text Content
    Level
    A
  • Some fields do not have valid labels

    Some forms have groups of checkboxes that are not marked up with valid labels, and so are not voiced by screen-readers. For example the industry checkboxes on the Employer edit form.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    1.1.1 Non-text Content
    Level
    A
  • Focus position is lost after updates to pages

    When changing the sort order on many of our search pages (e.g. "Vacancy advanced search") the focus position is lost and focus is returned to the top of the page. Similarly when an action triggers a modal such as a confirmation pop up, the focus position is lost and returns to the top of the page.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    1.3.2 Meaningful sequence
    Level
    A
  • TinyMCE fields are not keyboard accessible

    There are several places across the system that TinyMCE fields are used, such as template sets. These fields are not keyboard accessible.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    2.1.1 Keyboard
    Level
    A
  • Vacancy conversion report calendar arrows not read out by screen reader

    On the Vacancy conversion report page, the calendar arrows are not correctly read out by a screenreader.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    2.5.3 Label in name
    Level
    A
  • Application search employment checks table

    There are a few accessibility issues with the way we display employment checks in the results table of the application advanced search. These have an incorrect tab order, and some do not have correct focus/hover styles.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    2.4.3 Focus Order
    Level
    A
  • Dashboard page has several accessibility issues

    There are several level A, AA and AAA failures on this page, the most severe level A failure is in regard to how the tables and links are marked-up which can make it confusing to navigate the page with lots of repetitive content that is not properly distinguished, and the details modal dialogue can not be opened with the keyboard.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    1.1.1 Non-text Content
    Level
    A
  • "Unactioned communications" page has several accessibility failings

    This page has a number of accessibility failures, including a keyboard trap on the message list and some visual-only notifications.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    2.1.2 No Keyboard Trap
    Level
    A
  • Login fields and some drop down select fields do not have visible labels

    The Email address and password fields to login do not have visible labels. This is the same for some drop down select fields are used on forms in a group.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    3.3.2 Labels or instructions
    Level
    A
  • Calendar widgets are not fully keyboard accessible

    There are several places across the system that Calendar widgets are used. Individual dates cannot be selected by keyboard navigation and do not have active focus.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    2.1.1 Keyboard
    Level
    A
  • Validation is not auto-focused on screenreaders

    When validation is triggered, such as entering the incorrect email address or password when logging in, the error message is not fetched by the screenreader as it happens.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    3.3.1 Error Identification
    Level
    A
  • Home/To top menu button not keyboard accessible

    The button used to reload to Home or return to the top of the page is not accessible through keyboard navigation.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    2.1.1 Keyboard
    Level
    A
  • User guide has several accessibility issues

    These pages have a number of accessibility failures including images without alt names missing labels.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    3.3.2 Labels or instructions
    Level
    A
  • Colour contrast ratio failures on site button borders

    The borders across the site's buttons have Level AA failures in terms of contrast ratio.

    We plan to fix this issue by July 2025.

    WCAG 2.2 success criterion
    1.1.1 Non-text Contrast
    Level
    AA
  • Tooltips are not hoverable or dismissible

    The software package we use to generate our tooltips (popup messages on hover/focus) does not allow for dismissing the tooltip (other than by moving the pointer or keyboard focus) and does not allow hovering over or selecting the content of the tooltip.

    These tooltips are primarily used to provide explanation or text-alternatives for user-interface elements and should rarely be used for actual content which would need selecting or copying.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    1.4.13 Content on Hover or Focus
    Level
    AA
  • Dragging element in Data download missing pointer alternatives

    The Data Download report allows you to drag selectors to create different orders. The dragging element is missing a pointer to move these fields.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    2.5.7 Dragging Movements
    Level
    AA
  • Colour contrast ratio failures on tables in hover/focus

    Tables such as the applicant search result lists have contrast ratio failures when in hover/focus.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    1.4.3 Contrast (Minimum)
    Level
    AA
  • Site map loses formatting on smaller screen widths

    When viewing the site map page on a smaller screen width, the table loses its formatting.

    We plan to fix this issue by September 2025.

    WCAG 2.2 success criterion
    1.4.10 Reflow
    Level
    AA

Content that’s not within the scope of the accessibility regulations

  • Older PDFs and other documents may not be accessible.

    There may be some older PDFs and documents attached to vacancies or applications that may not be accessible. We consider these to be historic and not in active use. The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. Any new PDFs or Word documents we publish should meet accessibility standards.

Preparation of this accessibility statement

This statement was prepared on 15-Sep-2020. It was last reviewed on 13-Dec-2024.

This website was last tested on 24-Sep-2024 against the WCAG 2.2 AA standard. The test was carried out by Civica UK Ltd.