We’ve just published guidance setting out accessibility standards for NHS digital services for the public. It grew out of work we've been doing to improve the accessibility of the NHS website, but we hope it'll be used by digital teams across the NHS and inspire the broader public sector.

When we launched our front end library and prototyping tools in February 2019, all of the code and patterns were tested for accessibility, and we developed some initial guidance around accessibility.

We’ve now updated that guidance to be more comprehensive, and more useful, to people working in digital delivery teams. It’s advice that we think everyone needs to know, whether you’re building a service, or commissioning one. It sets out what should be done and, importantly, how to do it on a practical level.

We also plan to publish more things that will help people embed accessibility thinking in their practice – for example, checklists and templates, particularly for testers. We’ll also be building an Accessibility Lab in our office in Leeds (based on GDS’s ‘Empathy’ Lab), and a ‘roaming suitcase’ of accessibility equipment for London and the other regions.

So, how have we assembled our accessibility pages in the service manual? Our core guidance opens with three topics for everyone:

• what all NHS services need to do about accessibility: an overview of the law and what you need to do to meet the new requirements (WCAG2.1)
• how to make digital services accessible: some broad principles and our approach to accessibility
• getting started with accessibility: things you can learn with links to useful resources, including from our friends in the Government Digital Service

The NHS digital service manual team is a multi-disciplinary team. Not all teams across the NHS will have specialist roles but people involved in projects may be involved in multiple types of activities. For example, an interaction designer may also be involved in conducting user research. We’ve therefore labelled the guidance by activity rather than roles.