This accessibility statement applies to Jobvite.
Jobvite is an online platform built, hosted and controlled by a third party supplier, Jobvite, and used by the Department for Business and Trade (DBT). It allows people to apply for a job in the Digital, Data and Technology (DDaT) Directorate within DBT. DBT wants the third party online services that it uses to comply with Web Content Accessibility Guidelines (WCAG) 2.2 AA as a minimum so all users can use this platform. This means you should be able to:
- change colours, contrast levels and fonts using browser or device settings
- zoom in up to 400% 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.
How accessible this website is
We know some parts of this website are not fully accessible:
- Users can't skip repeated content sections.
- Links, interactive elements, and custom ARIA roles lack clear or accessible names.
- Fields, buttons, dialogs, and asterisks for required fields are improperly labelled or grouped.
- Formatting isn't preserved when the format changes; some text and elements have low contrast.
- Decorative images are not hidden from screen readers.
- Page titles are repetitive and non-descriptive.
- Links in dialogs are not keyboard accessible; focus is lost when the menu button is expanded.
- Error handling is insufficient; screen reader users aren't alerted to errors
- A reCAPTCHA component does not meet accessibility standards.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [email protected].
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email [email protected].
We’ll consider your request and get back to you in 5 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
The Department for Business and Trade 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
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
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Users are unable to skip repeated blocks of content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
The purpose of every link cannot be understood from the link text alone so users can decide whether to follow the link. Some links do not have an accessible name which results in them being non-descriptive for users of assistive technologies. This fails WCAG 2.2 success criterion 2.4.4. (Link Purpose In Context) and 4.1.2 (Name, Role, Value).
Some fields and button elements are unlabelled and don’t have an accessible name. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships), 2.5.3. (Label in Name), 3.3.2. (Labels or Instructions) and 4.1.2. (Name, Role, Value).
Information and relationships that are implied by visual or auditory formatting are not preserved when the presentation format changes. This fails WCAG 2.2 success criterion 1.3.1. (Info and Relationships).
Some custom elements are inaccessible to multiple user groups. This fails WCAG 2.2 success criterion 1.3.1. (Info and Relationships) and 4.1.2. (Name, Role, Value).
Incorrect use of ARIA - WAI-ARIA roles were used, but did not follow the design pattern to ensure that all behaviour, information and functionality were correctly exposed to assistive technologies. This fails WCAG 2.2 success criterion 4.1.2. (Name, Role, Value).
Some images have been inserted using the CSS ‘content’ attribute but have not been hidden from screen reader users. This fails WCAG 2.2 success criterion 1.1.1. (Non-text Content).
Some page titles are non-descriptive and repeated over multiple pages. This fails WCAG 2.2 success criterion 2.4.2. (Page Titled).
A reCAPTCHA component did not meet accessibility requirements. This fails WCAG 2.2 success criterion 1.1.1. (Non-text Content), 1.3.1. (Info and Relationships), 1.4.1. (Use of Colour), 2.2.1. (Timing Adjustable) and 4.1.3. (Status Messages).
Some interactive elements have not been implemented in a way that is accessible to all users. This fails WCAG 2.2 success criterion 1.3.1. (Info and Relationships), 2.1.1. (Keyboard) and 4.1.2. (Name, Role, Value).
Colour alone has been used to display information which is important to users. Colour blind and low vision users may find this difficult to read. This fails WCAG 2.2 success criterion 1.4.1. (Use of Colour).
Some multiple input fields have not been grouped together correctly. This might affect the understanding of the purpose without additional context. This fails WCAG 2.2 success criterion 1.3.1. (Info and Relationships).
Some dialog has no role or accessible name and focus is not placed within for all users. This fails WCAG 2.2 success criterion 2.4.3. (Focus Order) and 4.1.2. (Name, Role, Value).
Some links inside dialog have been assigned a tab index of -1 which removes them from the keyboard tab index. This means that keyboard only users are unable to access the links using the keyboard tab key. This fails WCAG 2.2 success criterion 2.1.1. (Keyboard).
Some asterisks which convey required fields are not provided with instructions. This fails WCAG 2.2 success criterion 3.3.2. (Labels or Instructions).
Some in page links do not work as expected. This fails WCAG 2.2 success criterion 2.4.3. (Focus Order).
When users commit errors, the error handling is not sufficient to enable users to identify and rectify errors effectively. This fails WCAG 2.2 success criterion 3.3.3. (Error Suggestion).
Some text elements fail to meet the required threshold for contrast minimum. This issue might affect low-vision users. This fails WCAG 2.2 success criterion 1.4.3. (Contrast Minimum).
Some non-text elements fail to meet the required threshold for non-text contrast and this might affect low vision users. This fails WCAG 2.2 success criterion 1.4.11. (Non-text Contrast).
Some labels are not descriptive for screen reader users navigating out of the context of the page. This fails WCAG 2.2 success criterion WCAG 2.4.6. (Headings and Labels).
When screen reader users make an error, there is no alert to inform them that an error has been triggered. This fails WCAG 2.2 success criterion 4.1.3. (Status Messages).
Some content is not presented without the loss of information or functionality and without requiring scrolling in two dimensions. This fails WCAG 2.2 success criterion 1.4.10. (Reflow).
When the page is set to 200% magnification the page content is obscured from users. This fails WCAG 2.2 success criterion 1.4.4. (Resize text).
Focus was obscured when the menu button was expanded. This fails WCAG 2.2 success criterion 2.4.12. (Focus Not Obscured).
What we’re doing to improve accessibility
We are currently working to resolve all of the identified issues listed in this statement to make them fully compliant with the WCAG (Web Content Accessibility Guidelines) version 2.2 AA standard.
Preparation of this accessibility statement
This statement was prepared on 26 May 2020. It was last reviewed on 1 May 2025.
This website was last tested on 14th April 2025 against the WCAG 2.2 AA standard.
The test was carried out by the Digital Accessibility Centre (DAC).
