Accessibility guidance for: - Product and delivery

If the answer to any of the following questions is 'yes', it's a sign that the project will need a higher level of accessibility expertise or support.

Does the project affect people with access needs differently?

For example, does the user's journey include physical access to a GP surgery? If so, include people who might find this difficult in your user research - for example, people with hearing, visual or mobility impairments. Read more about involving people with access needs in user research.

Will the project use any technologies you haven't already tested for accessibility?

You will need to test them, and the team working on them will need a higher level of accessibility knowledge or support.

Is the project about a complex subject with lots of jargon?

You'll need to allow time to write content that's easy to understand.

Will the interface need new components?

You should show that you've tested existing components and demonstrated a clear need for new ones. You must also make sure new components are accessible and you must test and maintain them.

Will there be a different colour scheme?

You'll need to check colour contrast, both for text and graphical elements.

Will the project use multimedia, PDFs, infographics, large data tables or other less common content?

Check the capabilities of the systems and the people creating them so that you can be sure that they will be accessible.

Is there a reason to include 'Easy Read' documents or translations?

If there is some key information that everyone must understand (such as a guide to a new national service), then consider including an Easy Read version for people with low-literacy or learning disabilities. Or you could link to Easy Read content from other organisations.

• Is it easy to understand?
• Can you use it without a mouse?
• Does it provide good contrast and allow zooming?
• Does it give screen readers appropriate information?

Large projects

For a large project, such as a new or replaced product or service or new functionality, you should record and be able to show that your team has:

• included accessibility requirements in your service design and user research
• tested its own work using the accessibility guidance for different activities
• tested any new technologies or components
• involved people with access needs in usability testing
• completed an independent accessibility audit and allowed time to make changes before your product or service goes live

If you test as you go along, the independent audit should find very little that needs changing. You will need the audit for your accessibility statement.

Small projects

For smaller projects or a small update, you have more discretion. Internal testing may be enough. Your team should follow this accessibility guidance and focus on testing new components and content.

Read more about different types of testing.