This accessibility statement applies to the Data Hub website.
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 up to 400% without the text spilling off the screen, except for the issues listed in this statement
- navigate most of the website using just a keyboard or speech recognition software (Dragon)
- listen to most of the website using a screen reader (including the most recent version of NVDA and JAWS)
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:
- the skip to main content link does not always receive keyboard focus on the first press of the Tab key and can overlap with or partially obscure nearby page elements
- a few pages have a colour contrast issue, which may make some text difficult to read
- page functionality such as search does not work when CSS styles are disabled.
- a few pages are missing descriptions, and some content uses inconsistent capitalisation
- certain links open external websites in the same tab, so users may need to rely on browser navigation to return to the previous page
- embedded report elements, including visual header actions, drill-down features and buttons that can sit behind visuals, may not be fully accessible to people who use a keyboard unless they know the relevant keyboard shortcuts
- report content with horizontal scrolling does not always stay focused on the current element when the screen is zoomed
- chart labels, numbers and legends may not have enough spacing, some stacked bar charts and map visuals may unclear, and legend order and orientation may not match the related chart
- data shown in the accessible table option for report visuals may not follow the same formatting as the data shown in the visual
- report elements, links, scrolling areas and map visual legends do not always work efficiently with speech recognition software and may require alternative methods, such as keyboard commands
- parts of report content are not always read correctly, fully, or in a logical order by screen readers, which may make it harder for people who use assistive technology to understand or navigate the content
Feedback and contact information
Contact us if you need information about this website in a different format, such as accessible PDFs, 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 by:
Email: [email protected]
This email address is only for accessibility questions. It is not for technical queries or IT problems. If you have a query that is not about accessibility, you can contact our support team
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 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 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
The skip to main content link does not always receive focus on the first press of the Tab key and can overlap with or partially obscure nearby page elements. This fails WCAG 2.2 success criteria 2.4.1 Bypass Blocks (Level A), 2.4.3 Focus Order (Level A) and 2.4.11 Focus Not Obscured (Minimum) (Level AA).
A few pages have a colour contrast issue, which may make some texts difficult to read. This fails WCAG 2.2 success criterion 1.4.3 Contrast (Minimum) (Level AA).
Page functionality such as search does not work when CSS styles are disabled. This fails WCAG 2.2 success criteria 1.3.2 Meaningful Sequence (Level A) and 2.1.1 Keyboard (Level A).
A few pages are missing descriptions, and inconsistent capitalisation may be used in some content. This may affect WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.1 Readable.
Certain links open other websites in the same tab, so users may need to rely on browser navigation to return to the previous page. This fails WCAG 2.2 success criteria 2.1.1 Keyboard (Level A) and 4.1.2 Name, Role, Value (Level A).
Embedded report elements, including visual header actions, drill-down features and buttons that can sit behind visuals, will not be fully accessible using keyboard navigation unless the user is aware of the relevant keyboard shortcuts. This fails WCAG 2.2 success criteria 2.1.1 Keyboard (Level A), 2.4.3 Focus Order (Level A) and 4.1.2 Name, Role, Value (Level A).
Report content with horizontal scrolling does not always stay focused on the current element when the screen is zoomed. This fails WCAG 2.2 success criteria 1.4.10 Reflow (Level AA), 2.4.3 Focus Order (Level A) and 2.4.11 Focus Not Obscured (Minimum) (Level AA).
Chart labels, numbers and legends may not have enough spacing, some stacked bar charts and map visuals may be unclear, and legend order and orientation may not match the related chart. This fails WCAG 2.2 success criteria 1.1.1 Non-text Content (Level A), 1.3.1 Info and Relationships (Level A) and 3.1 Readable.
Data shown in the accessible table option for report visuals may not follow the same formatting as the data shown in the visual. This may affect WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A) and 3.1 Readable.
Report elements, links, scrolling areas and map visual legends do not always work efficiently with speech recognition software and may require alternative methods such as keyboard commands. This fails WCAG 2.2 success criteria 2.1.1 Keyboard (Level A) and 4.1.2 Name, Role, Value (Level A).
Parts of report content are not always read correctly, fully, or in a logical order by screen readers, which may make it harder for assistive technology users to understand or navigate the content. This may affect WCAG 2.2 success criteria 1.3.1 Info and Relationships (Level A), 2.4.3 Focus Order (Level A) and 4.1.2 Name, Role, Value (Level A).
We plan to fix these issues. When we publish new content, we’ll make sure it meets accessibility standards.
Navigation and accessing information
It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
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 9 July 2026. It was last reviewed on 16 July 2026.
This website was last tested on 9 July 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 test team. A further audit of the website was carried out to the WCAG 2.2 AA standard.
We tested about 90% of 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 and JAWS) and standards checklists.
We run representative user journey tests through speech recognition software (Dragon).
These checklists contain standards that have been compiled using WCAG, the NHS service manual and the Government Digital Service (GDS) guidance.