This accessibility statement applies to the website ‘Data Hub Portal Page.
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:
- zoom in up to 400% without the text spilling off the screen
- navigate most of the website using just a keyboard or speech recognition software, such as Dragon
- listen to most of the website using a screen reader (including the most recent version of NVDA)
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:
- this page doesn’t contain a heading structure making it difficult to navigate
- this page uses a layout that can make it difficult to navigate the page when using a screen reader
- this page contains missing or inappropriate form labels
- this page contains redundant title text for users with a screen reader
- this page has images which are difficult to identify with a screen reader
- a logo does not have the correct alternative text
- this page is difficult to navigate using just a keyboard
- the layout of tables can cause difficulty when using a screen reader
- list items are not contained within typical unordered list structures which can cause difficulty when using a screen reader
- JavaScript is disabled which can cause difficulty for users of screen readers and other assistive technologies
- this page contains an event handler that may not be accessible
- error messages are complex and difficult to understand
- this page contains an Accessible Rich Internet Application (ARIA) attribute that has not been applied correctly which makes using assistive technology difficult
- users may not be able to navigate this website using speech recognition software
- users may face difficulty using VoiceOver, Voice Control and Mac software
- menu options at the top of the webpage and interactions using grid commands may not be accessible when using a speech recognition tool such as Dragon
How to request content in an accessible format
If you need information on this website in a different format such as an accessible PDF, large print, easy read, audio recording or braille, you can contact us by:
Email: accessibility@nhsbsa.nhs.uk
We’ll consider your request and get back to you in 5 working days.
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, go to the ‘Contact us’ section of this page.
Reporting accessibility problems with this website
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 by:
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, go to the ‘Contact us’ section of this page.
Contact us
For all queries not accessibility related, you can contact us by:
Email: DataServicesSupport@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
The NHSBSA 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 non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
This page doesn’t contain a heading structure making it difficult to navigate. This fails WCAG 2.2 criterion 2.4.6 (Headings and Labels).
This page uses a layout that can make navigating the page difficult when using a screen reader. This fails WCAG 2.2 criterion 2.4.6 (Headings and Labels).
This page contains missing or inappropriate form labels. This fails WCAG 2.2 criterion 2.4.6 (Headings and Labels).
This page contains redundant title text for users with a screen reader. This fails WCAG 2.2 criterion 1.1.1 (Non-Text Content).
This page has images which are difficult to identify with a screen reader. This fails WCAG 2.2 criterion 1.4.9 (Images of Text).
A logo does not have the correct alternative text. This fails WCAG 2.2 criterion 1.4.9 (Images of Text).
This page is difficult to navigate using just a keyboard. This fails WCAG 2.2 criterion 2.1 (Keyboard Accessible).
The layout of tables can cause difficulty when using a screen reader. This fails WCAG 2.2 criterion 3.2.3 (Consistent Navigation).
List items are not contained within typical unordered list structures which can cause difficulty when using a screen reader. This fails WCAG 2.2 criterion 3.2.3 (Consistent Navigation).
Javascript is disabled which can cause difficulty for users of screen readers and other assistive technologies. This fails WCAG 2.2 criterion 3.2.3 (Consistent Navigation) and 4.1 (Compatible).
This page contains an event handler that may not be accessible. This fails WCAG 2.2 criterion 2.1 (Keyboard Accessible).
Error messages are complex and difficult to understand. This fails WCAG 2.2 criterion 3.3.1 (Error Identification).
This page contains an accessible rich internet applications (aria) attribute that has not been applied correctly which makes using assistive technology difficult. This fails WCAG 2.2 criterion 1.3 (Adaptable).
Users may not be able to navigate this webpage using speech recognition software. This fails WCAG 2.2 criterion 4.1 (Compatible).
Users may face difficulty using VoiceOver, Voice Control and Mac software. This fails WCAG 2.2 criterion 4.1 (Compatible).
Menu options at the top of the webpage and interactions using grid commands may not be accessible when using speech recognition tool such as Dragon. This fails WCAG 2.2 criterion 2.4 (Navigable).
Menu options at the top of the webpage and interactions using grid commands may not be accessible when using speech recognition tool such as Dragon. This fails WCAG 2.2 criterion 2.4.11 (Focus Not Obscured) and 2.5 (Guideline Input Modalities).
Navigation and accessing information
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option).
It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
Interactive tools and transactions
Some of our interactive forms are difficult to navigate using a keyboard, for example, some form controls are missing a ‘label’ tag.
Our forms are built and hosted through third party software and ‘skinned’ to look like our website.
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.
What we’re doing to improve accessibility
We’re committed to making sure this website is compliant to WCAG 2.2 ‘AA’ standard.
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 26/06/2024. It was last reviewed on 26/06/2024.
This website was last tested on 19/06/2024 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 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.