The NHS is for everyone, so NHS digital services should be accessible to everyone too.
Accessibility and the law
If your service isn't accessible to everyone who needs it, you may be breaking the 2010 Equality Act.
Public sector websites must meet the Public Sector Bodies Accessibility Regulations 2018 and publish an accessibility statement. Find out about the accessibility requirements for public sector bodies on GOV.UK.
Meeting the requirements
Digital services in the NHS must:
- meet at least level AA of the Web Content Accessibility Guidelines (WCAG 2.2) and aim for AAA where possible
- work on the most commonly used assistive technologies (follow GOV.UK guidance on testing with assistive technologies)
- include people with access needs in user research
- publish an accessibility statement that complies with GOV.UK requirements
Teams on short deadlines
If you're working to a tight deadline, you must:
- check the GOV.UK guidance on making services in an emergency
- consider exclusion as you design your service, for example, with GOV.UK's user profiles for understanding disabilities and impairments
- use the NHS production code and design system
- set up automated accessibility testing and fix issues you identify
- use the NHS accessibility checklist to carry out an initial WCAG evaluation
- test service journeys with a range of assistive technologies
- plan user research to identify and remove barriers
Internal services
NHS staff and civil servants are users too and the NHS is committed to equality, diversity and inclusion. Internal services need to meet the same accessibility requirements.
Suppliers and contractors
External suppliers contracted to the NHS must also make sure their work meets the same standard.
The NHS may test the product or ask suppliers to arrange an independent accessibility test.
Why it's important
In the UK, almost 1 in 5 people have a disability of some kind. Many more have temporary or situational disabilities, like an illness or injury.
When you're working on NHS services, think about how people with different needs might use what you're making.
For example, can someone with dyslexia read your content easily? Or how would someone with a broken arm interact on a mobile device?
Updated: January 2024