This accessibility statement applies to the NHS Jobs website for employers.
This website is run by the NHS Business Services Authority (NHSBSA). 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 most of the website up to 400% without the text spilling off the screen
- navigate most of the website using just a keyboard or speech recognition software (Voice Control and Dragon)
- listen to most of the website using a screen reader (including the most recent version of NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advised 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, as:
- on some pages, the primary navigation bar menu options disappear or are inconsistent when zoomed in 200% or more
- there are redundant links on some pages which result in extra navigation and repetition for keyboard and screen reader users
- on most pages, skip links shift user focus to the main content but the focused content is not highlighted - this may cause difficulties in identifying which element the focus has been shifted to
- on some pages, error links do not take the user to the input field that is causing the error
- on some pages, the change link does not take the user to intended input fields
- on some pages, the page title and page heading are not the same which may cause issues for screen reader users
- error messages on reporting screens are not recognised by speech recognition tools like Dragon
- screen reader users may experience difficulties with identifying headings, lists, tables and reading order as they are not tagged properly in the downloadable PDF documents
- screen reader users will have difficulties switching to the appropriate language as the primary text language of the downloadable PDF documents is not specified
- in some PDFs, document titles are not correctly tagged, which can make it difficult for screen reader users to identify the document’s purpose
- downloadable PDF documents do not follow a logical order when using the Tab or Shift-Tab keys to navigate, which will cause issues for users navigating with a keyboard
- downloadable PDF documents contain images with no alternate text which will cause issues for screen reader users
- on some pages, focus does not move to the error message dialog box from the selected input field when a user resubmits the same form - this may cause difficulties with selecting the intended web element
- on some pages, error message links are shown in an incorrect position - this may lead to inconsistent navigation for users
- on some pages, error message links shift the focus to the correct input field but this is outside the screen view area - this may cause difficulties in finding the web element
- on some pages, focus is not visible after tabbing and the page does not scroll to focus on the tabbed fields - this may cause issues with identifying which element the focus has been shifted to
- on some pages, the focus contrast affects the page view and page elements which may cause issues when reading the page content
- on some pages, new text is automatically populated over original text in the field which makes it unclear and difficult for the user to enter the correct value
- on some pages, focus is on non-functional fields - this may cause issuess with navigating between functional areas of the page
- on some pages, input fields do not have visible labels, which may cause issues for screen reader users
- some links on the ‘NHS Jobs terms and conditions’ page are not descriptive which may cause issues for screen reader users
- on some pages, the menu button does not display correctly when JavaScript is disabled and the zoom level is above 150%
- some URLs contain underscores which screen readers may misread
- the "All accounts" toggle does not function properly when JavaScript is disabled
- the buttons within the rich text editor (trumbowyg) are not accessible when using keyboard navigation, on the ‘Provide a job overview to create your advert’ and ‘Add the job description’ pages
- VoiceOver users can face difficulty in navigating through the skip links using the space bar
- on the ‘Ready to offer’ page, VoiceOver does not read the link text correctly
- Voice Control users may face difficulty in interacting with email and other interactive links
- the Voice Control "Show numbers" speech command does not recognise the ‘All accounts’ toggle
- certain links are not recognised as actionable links for Dragon users and are incorrectly highlighted
Feedback and contact information
Contact us if you need information about this website in a different format, such as accessible PDF, large print, easy read, audio recording or braille. We’ll consider your request and get back to you within 5 working days.
We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we’re not meeting accessibility requirements, you can contact us using the same email address:
Email: accessibility@nhsbsa.nhs.uk
This email address is only for accessibility queries. It is not for technical queries or IT problems. If you have a query that is not about accessibility, you can contact us by:
Email: nhsbsa.nhsjobs@nhsbsa.nhs.uk
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
NHS Business Services Authority 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
On some pages, the primary navigation bar menu options disappear or are inconsistent when zoomed in 200% or more. This fails WCAG 2.2 success criterion 1.4.10 (Zoom and reflow).
There are redundant links on some pages which result in extra navigation and repetition for keyboard and screen reader users. This fails WCAG 2.2 Success criterion 2.4.4 (Link Purpose).
On most pages, skip links shift the user focus to the main content but the focused content is not highlighted - this may cause difficulties in identifying which element the focus has been shifted to. This fails WCAG 2.2 success criteria 2.4.1 (Bypass Blocks) and 2.4.7 (Focus Visible).
On some pages, error links do not take the user to the input field that is causing the error. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
On some pages, the change link will not take the user to intended input fields. This fails WCAG 2.2 success criterion 2.4.7 (Tab Indexes).
On some pages, the page title and page heading are not the same which may cause issues for screen reader users. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
Error messages on reporting screens are recognised by speech recognition tools like Dragon. This fails WCAG 2.2 success criteria 3.3.1 (Error identification) and 3.3.3 (Error Suggestion).
Screen reader users may experience difficulties with identifying headings, lists, tables and reading order as it is not tagged properly in the downloadable PDF documents. This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content), 1.3.1 (Info and Relationships) and 1.3.2 (Meaningful Sequence).
Screen reader users will have difficulties switching to the appropriate language as the primary text language of the downloadable PDF documents is not specified. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page).
In some PDFs, document titles are not correctly tagged, which can make it difficult for screen reader users to identify the document’s purpose. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
Downloadable PDF documents do not follow a logical order when using the Tab or Shift-Tab keys to navigate, which will cause difficulties for users navigating with a keyboard. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
Downloadable PDF documents contain images with no alternate text which will cause issues for screen reader users. This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content), 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value).
On some pages, focus does not move to the error message from the selected input field when a user resubmits the same form - this may cause difficulties with selecting the intended web element. This fails WCAG 2.2 success criteria 3.3.1 (Error identification) and 3.3.3 (Error suggestion) and 3.2.1 (On Focus).
On some pages, error message links are shown in an incorrect position – this may lead to inconsistent navigation for users. This fails WCAG 2.2 success criterion 3.3.1 (Error identification).
On some pages, error message links shift the focus to the correct input field but this is outside the screen view area – this may cause difficulties in finding the web element. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
On some pages, focus is not visible after tabbing and the page does not scroll to focus on the tabbed elements - this may cause issues with identifying which element the focus has been shifted to. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
On some pages, the focus contrast affects the page view and page elements which may cause issues when reading the page content. This fails WCAG 2.2 success criterion 2.4.11 (Focus Appearance).
On some pages, new text is automatically populated over original text in the field which makes it unclear and difficult for the user to enter the correct value. This fails WCAG 2.2 success criteria 1.3.5 (Identity (Input Purpose) and 3.3.7 (Redundant Entry).
On some pages, focus is on non-functional fields – this may cause issues with navigating between functional areas of the page. This fails WCAG 2.2 success criterion 2.1.
On some pages, input fields do not have visible labels, which may cause issues for screen reader users. This fails WCAG 2.2 success criterion 2.4.6 Headings & Labels, 1.3.1 Info and Relationships, 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value).
Some links on the “NHS Jobs terms and conditions” page are not descriptive which may cause issues for screen reader users. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose).
On some pages, the menu button does not display correctly when JavaScript is disabled and the zoom level is above 150%. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some URLs contain underscores which screen readers may misread. This fails WCAG 2.2 success criterion 2.4 (Navigable).
The "All accounts" toggle does not function properly when JavaScript is disabled. This fails WCAG 2.2 success criterion 4.1 (Compatible).
The buttons within the rich text editor (trumbowyg) are not accessible when using keyboard navigation on the ‘Provide a job overview to create your advert’ and ‘Add the job description’ pages. This fails WCAG 2.2 success criterion 2.1 (Keyboard Accessible).
VoiceOver users can face difficulty in navigating through the skip links using the space bar.. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
On the ‘Ready to offer’ page, VoiceOver does not read the link text correctly. This fails WCAG 2.2 success criterion 2.1 (Keyboard Accessible).
Voice Control users may face difficulty in interacting with email and other interactive links. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
The Voice Control "Show numbers" speech command does not recognise the ‘All accounts’ toggle. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
Certain links are not recognised as actionable links for Dragon users and are incorrectly highlighted. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value) and 2.4.7 (Focus Visible).
Content that’s not within the scope of the accessibility regulations
Features and structural elements
Many features on the website need to be accessibility-reviewed to make sure they’re implemented correctly for users with accessibility needs.
The structure of the website screens needs to be reviewed to make sure they meet accessibility guidelines.
The use of ARIA labels on the website needs to be reviewed to make sure they meet accessibility guidelines.
Although these do not fail WCAG 2.2 success criteria, we aim to review these areas. This will make sure we meet all accessibility standards on our website.
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. We plan to either fix these or replace them with accessible HTML pages.
Any new PDFs or Word documents we publish will meet accessibility standards.
Document Upload
Due to an issue with Dragon and some older versions of this assistive technology, users will have difficulties interacting with the document upload buttons. We advise Dragon users to use the mouse grid to interact with the file upload feature.
What we’re doing to improve accessibility
We’re committed to making sure this website is compliant to WCAG 2.2 ‘AA’ standard.
Our accessibility compliance statement will be reviewed regularly. Every newly released website will be designed, built, and tested to meet ‘AA’ standards by default.
Preparation of this accessibility statement
This statement was originally prepared on 17 September 2019. It was last reviewed on 14 July 2025.
This website was last tested on 17 April 2025.
The test was carried out by the NHSBSA test and development teams. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.
We tested all the website screens to meet ‘AA’ WCAG 2.2 standards, using manual and automated tests.
We run each webpage through automated Wave, Lighthouse and Axe accessibility tools and then manually test with screen readers (NVDA or VoiceOver) and standards checklists.
We run representative user journey tests through speech recognition software (Dragon or Voice Control).
These checklists contain standards that have been compiled using WCAG, the NHS service manual and the Government Digital Service (GDS) guidance.