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
- navigate most of the website using just a keyboard or speech recognition software (Voice Control, JAWS 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 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, as:
Navigation and orientation
- on some pages, the primary navigation bar menu options disappear or are inconsistent when zoomed in 200% or more
- on some pages the change link will not take the user to intended input fields
- on some pages URLs and page may be inconsistent
- on some pages error message links are shown in an inconsistent position
- when JavaScript is turned off, the menu button in the main navigation disappears at zoom levels above 150%
- the "All accounts" toggle does not function properly when JavaScript is turned off
- when CSS styles are disabled, some logos and icons push content out of view
- in landscape orientation, a navigation arrow overlaps the “Signed in as [user name]” link
- on some pages, checkboxes and change links become misaligned when the page is resized or viewed in different orientations
- when JavaScript is turned off, skip links may not direct users to the main content
- some links open in a new tab without warning
- on some pages containing tables, content extends beyond the right edge of the screen.
- screen reader users may find that some journeys do not include a confirmation page
- some reporting pages automatically refresh and redirect after a delay
Forms, input fields and error handling
- on some pages error messages do not take the user to the correct input fields
- on some pages focus does not move to the error message, making it harder to identify and correct the error
- on some pages input fields do not have visible labels, making them more difficult to identify and complete
- pages containing date input fields may display a popup message when invalid characters are entered
- on some pages validation errors do not use the standard error formatting
- on some pages when JavaScript is turned off and a validation error occurs, it can be difficult to interact with errors
- when entering referee details, and validation error occurs, the links to the inputs may not be in a logical order
- when creating a job advert or job description, some input fields include character counters that are not announced to screen reader users
Keyboard accessibility and focus
- on some pages, keyboard focus is not always visible
- some links do not have enough colour contrast when focused
- the buttons within the rich text editor (Trumbowyg) cannot be accessed using keyboard navigation or speech recognition on the ‘Provide a job overview to create your advert’ and ‘Add the job description’ pages
- on some pages, keyboard navigation does not follow a logical order
- keyboard users cannot move focus to organisation logos and may not be aware that the logos are present on the page
- when using the dropdown menus on the Ready to Offer page, keyboard focus may reset, requiring users to navigate back to the start
- on some pages, non-interactive elements such as headings and sub-tabs receive keyboard focus
Screen reader and assistive technology support
- some links on the "NHS Jobs terms and conditions" page are not descriptive
- on the ‘Ready to Offer’ page, some link text is not announced correctly by screen readers
- users of Voice Control may have difficulty activating email links and some other interactive elements using voice commands
- some toggles cannot be activated using voice commands or the “Show Numbers” feature
- some links are not recognised correctly by Dragon speech recognition software
- some tabs cannot be activated using direct voice commands or the "Show Numbers" feature
- when using the address finder, screen reader users may hear returned addresses announced as "misspelled"
- some values in the Address Finder dropdown lists cannot be activated by voice command
- the Address Finder page contains content, including images without alternative text
- some buttons are not identified correctly by assistive technologies
- on some pages, links are do not have accurate accessible names
- on some pages, radio button options include hidden text that does not match the visible label.
Downloadable documents and PDFs
- some downloadable PDF documents, do not tag headings, lists, tables and reading order correctly, which means screen reader users may not be able to identify or navigate through them
- some documents do not specify the main language, which may stop screen reader users from switching to the correct language
- some PDFs do not tag document titles correctly, which may make it difficult for screen reader users to identify the purpose of the document
- some downloadable PDF documents do not follow a logical tab order, making them difficult to navigate using a keyboard
- PDF documents contain images with no alternate text which makes them difficult for screen reader users to understand
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: [email protected]
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: [email protected]
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 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
Navigation and orientation
On some pages, the primary navigation menu disappears or becomes inconsistent when the page is zoomed to 200% or more. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
On some pages, "Change" links do not take users to the correct form field. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
On some pages, the page title does not match the main page heading. This may make it more difficult for screen reader users to identify the page. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
On some pages, error message links are displayed in the wrong position, making it more difficult to navigate to and correct errors. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
When JavaScript is turned off, the menu button in the main navigation disappears at zoom levels above 150%. This fails WCAG 2.2 success criteria 1.4.10 (Reflow) and 4.1 (Compatible).
The "All accounts" toggle does not work when JavaScript is turned off. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
When CSS styles are disabled, the NHS logo and navigation arrows become oversized and push the main content out of view. This can make pages difficult to understand and navigate. This fails WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence).
In landscape orientation, a navigation arrow overlaps the "Signed in as [user name]" link, making the link difficult to access. This fails WCAG 2.2 success criterion 1.3.4 (Orientation).
On some pages, selection checkboxes and "Change" links become misaligned when the page is resized or viewed in different orientations. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Skip links do not work correctly when JavaScript is turned off. Selecting a skip link does not move focus to the target heading or announce it in VoiceOver, making it difficult to skip to the main content. VoiceOver users may also have difficulty activating skip links using the Space key. This fails WCAG 2.2 success criteria 2.1.1 (Keyboard) and 2.4.1 (Bypass Blocks).
Some links open in a tab without warning the user, which may confuse screen reader users. This fails WCAG 2.2 success criterion 1.3.6 (Identify Purpose) and 2.4.4 (Link Purpose (In Context)).
On some pages containing tables, content extends beyond the right edge of the screen when viewed on a mobile device or at high zoom levels. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some journeys do not include a confirmation page or confirmation message. This may make it unclear whether an action has been completed successfully. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
Some reporting pages automatically refresh and redirect after a delay. This may make it difficult for users, including screen reader users, to understand what has happened and continue their task. This fails WCAG 2.2 success criteria 2.2.1 (Timing Adjustable) and 2.2.2 (Pause, Stop, Hide).
Forms, input fields and error handling
On some pages, error messages do not move focus to the correct input fields, which may make it difficult for users to correct errors. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
On some pages, when users resubmit a form with the same error, focus does not move to the error message. This may make it more difficult to identify and correct the error. This fails WCAG 2.2 success criteria 3.3.1 (Error Identification), 3.3.3 (Error Suggestion) and 3.2.1 (On Focus)
On some pages, input fields do not have visible labels, making them more difficult to identify and complete. This fails WCAG 2.2 success criteria 2.4.6 (Headings and Labels), 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value).
Pages containing date input fields may display a popup message when invalid characters are entered. Screen readers cannot access this message. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
On some pages, validation errors do not use the standard error formatting. This fails WCAG 2.2 success criteria 3.3.1 (Error Identification) and 3.2.4 (Consistent Identification).
On some pages, when JavaScript is turned off and a validation error occurs, focus is not moved to the error summary. This may make it more difficult to identify and correct errors. This fails WCAG 2.2 success criterion 3.2.3 (Consistent Navigation).
When entering referee details, error summaries may not follow the same order as the associated input fields, making errors harder to locate and correct. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification).
When creating a job advert or job description, some input fields include character counters that are not announced to screen reader users. Users may exceed the character limit without being aware of it. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
Keyboard accessibility and focus
On some pages, keyboard focus is not always visible and the page does not automatically scroll to the focused element, making it difficult to identify where focus has moved. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
Some links do not have enough colour contrast when focused, which may make them difficult for users to see. This fails WCAG 2.2 success criteria 2.4.13 (Focus Appearance), 2.4.7 (Focus Visible) and 1.4.3 (Contrast (Minimum).
The buttons within the rich text editor (Trumbowyg) cannot be accessed using keyboard navigation or speech recognition on the ‘Provide a job overview to create your advert’ and ‘Add the job description’ pages. This fails WCAG 2.2 success criteria 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
On some pages, keyboard navigation does not follow a logical order, making it more difficult to move through content and controls. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
Keyboard users cannot move focus to organisation logos and may not be aware that the logos are present on the page. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
When using the dropdown menus on the Ready to Offer page, keyboard focus may reset, requiring users to navigate back to the dropdown menu they were using. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification).
On some pages, non-interactive elements such as headings and sub-tabs receive keyboard focus, which may make navigation more difficult. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification).
Screen reader and assistive technology support
Some links on the "NHS Jobs terms and conditions" page are not descriptive, making it difficult for screen reader users to understand their purpose. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose).
On the ‘Ready to Offer’ page, some link text is not announced correctly by screen readers. This fails WCAG 2.2 success criterion 2.4.9 (Link Purpose (Link Only)).
Users of Voice Control may have difficulty activating email links and some other interactive elements using voice commands. This fails WCAG 2.2 success criteria 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
The Voice Control "Show Numbers" feature does not recognise the ‘All accounts’ toggle, making it difficult to activate using voice commands. This fails WCAG 2.2 success criteria 2.1.1 (Keyboard) and 4.1.2 (Name, Role, Value).
Some links are not recognised correctly by Dragon speech recognition software, making them difficult to identify and activate. This fails WCAG 2.2 success criteria 4.1.2 (Name, Role, Value) and 2.4.7 (Focus Visible).
Users of Voice Control may have difficulty interacting with the tabs on the Manage Offer page because they cannot be activated using direct voice commands or the "Show Numbers" feature. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
When using the address finder, screen reader users may hear returned addresses announced as "misspelled", which may lead them to believe the address has been entered incorrectly. This fails WCAG 2.2 success criterion 3.3.7 (Redundant Entry).
Users of speech recognition software may have difficulty selecting values from the Address Finder dropdown lists and may need to use alternative navigation methods. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
The Address Finder page contains hidden content below the footer, including images without alternative text, which may be confusing for screen reader users. This fails WCAG 2.2 success criteria 3.2.4 (Consistent Identification) and 1.1.1 (Non-text Content).
On some pages, buttons are identified as links instead of buttons. This means screen readers may announce them incorrectly, making it harder for users to understand how the control will behave. Users of speech recognition software may also be unable to activate these controls using the commands they would normally use for buttons. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
On some pages, "Change" links use wording that does not match the associated section description. This may make it difficult for users of speech recognition software to identify and activate the correct link using voice commands. This fails WCAG 2.2 success criteria 2.4.4 (Link Purpose), 3.2.4 (Consistent Identification) and 4.1.2 (Name, Role, Value).
On some pages, radio button options include hidden text that does not match the visible label. This may make it difficult for users of speech recognition software to select options using voice commands. This fails WCAG 2.2 success criteria 2.5.3 (Label in Name) and 4.1.2 (Name, Role, Value).
Downloadable documents and PDFs
Some downloadable PDF documents do not tag headings, lists, tables and reading order are correctly, which makes them difficult for screen reader users to understand and navigate. 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).
Some documents do not specify the main language, which may stop screen reader from switching to the correct language. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page).
Some PDFs, do not tag document titles correctly, which may make it difficult for screen reader users to understand the of the document. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
Some downloadable PDF documents do not follow a logical tab order, which may make keyboard navigation difficult for users using the Tab or Shift-Tab keys. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
Downloadable PDF documents contain images without alternative text, which will make them difficult for screen reader users to understand. 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).
We plan to fix these issues. When we publish new content, we’ll make sure it meets accessibility standards.
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 30 June 2026.
This website was last tested on 18 June 2026 against the WCAG 2.2 AA standard.
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 then manually test with screen readers (NVDA, JAWS and VoiceOver) and standards checklists.
We run representative user journey tests through speech recognition software (Dragon and Voice Control).
These checklists contain standards that have been compiled using WCAG, the NHS service manual and the Government Digital Service (GDS) guidance.