We have detected that you are using Internet Explorer to visit this website. Internet Explorer is now being phased out by Microsoft. As a result, NHS Digital no longer supports any version of Internet Explorer for our web-based products, as it involves considerable extra effort and expense, which cannot be justified from public funds. Some features on this site will not work. You should use a modern browser such as Edge, Chrome, Firefox, or Safari. If you have difficulty installing or accessing a different browser, contact your IT support team.
This website is run by the Health and Social Care Information Centre, operating as NHS Digital.
We want as many people as possible to be able to use our website, and we have designed it to be accessible.
How you can use this website
This accessibility statement is for the NHS Digital website (digital.nhs.uk) only. It does not cover any subsites (which would look like: examplesite.digital.nhs.uk), or any websites linked from this one. Those sites will have their own accessibility statements.
On this website, you should be able to:
change colours, contrast levels, and fonts
zoom in up to 300% with text staying visible on the screen, and most images scaling without resolution loss
navigate most of the website using a keyboard
navigate most of the website using speech recognition software
read most of the website using a screen reader, including the latest versions of JAWS, NVDA, and VoiceOver
read most of the website on devices without a screen, like a braille computer
We've made the website text as simple as possible to understand, aiming for a reading age of a 12 year old.
Some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means.
We'll consider your request, and aim to get back to you within 3 days.
Reporting accessibility problems
We're always looking to improve the accessibility of the website.
If you find any problems which aren't listed on this page, or think that we're not meeting the requirements of the accessibility regulations then please email email@example.com to let us know.
We scan the site weekly for broken links, and look to fix them as soon as they are identified.
The content team are working through the links which don't make sense on their own, and we aim to have fixed these by August 2019.
Issues with PDFs and other documents
PDFs are not able to comply with the requirements of the web accessibility standard, and we do not generally upload new PDFs. Where we do create new PDFs, we use the PDF/A standard which is more accessible.
Our site contains a large number of PDFs created in previous years, especially in our data and information publications.
We strive to make all of our content accessible. We are aware of the following issues with images and video on our site:
Video content uses automated closed captioning and transcripting, and this is often inaccurate. By September 2019 we will review these captions and ensure their accuracy manually.
Some of the images on our site are complex diagrams where suitable alt text is not possible. A list of these images is below. By September 2020 we intend to have reviewed all of these images, and where possible will have converted them to accessible format such as SVG, used a different visualisation method, built the visualisation in HTML5, or added detailed description text to the page
There are some issues with text and content which we are aware of:
not all of our content reaches our target reading age of 12 years old. We are resolving this as content comes up through its review cycle, and this should be largely complete by September 2021.
some of our page titles are long, causing a technical fail on descriptive titles for web pages which requires titles to be short. In most cases, this is related to legal or formal names for publications. We are not going to fix this, as the content is still understandable, and changing titles might cause compliance issues.
Issues with interactive tools
We are aware that we have PowerBI and Tableau visualisations available on the website. Neither of these software items are accessible, and cannot be made accessible. In some cases the information is not easily available to users in an accessible format. We are currently investigating accessible visualisation tools. If you require information from these tools, then please contact us.
The weekly report is reviewed by the website development team, with any actions taken and prioritised into our future work. We aim to fix all high priority issues with one week of them being identified.
In addition, we conduct internal testing against known accessibility issues which are not able to be found through automated testing, on a sampled basis. We last conducted an accessibility check on these areas in August 2020.
This chart shows the compliance as measured by our automated testing tool, Sitemorse against the A, AA, and AAA standards of the WCAG 2.1 specification.
Each standard has its own points of compliance, so those scores are shown separately.
However, you cannot claim a higher standard if you do not meet the lower ones, which means that the number of pages meeting AA or AAA is limited to the number of pages also passing the A standard.
What automated testing tells us
We use automated testing to drive most of our improvements to accessibility on the site.
Automated testing can't find everything that could be improved, but is rarely wrong about what it does find.
This means we have fixed tens of thousands of accessibility problems which manual checking would have missed.
We do also undertake manual testing, including testing with real users with accessibility needs. We follow best practice across the industry, and try to keep up with the latest techniques for making our site accessible.
Accessible features we test manually
There are a number of accessibility features which we test manually, which include: