Accessibility Statement for NHS Pathways Web

Pathways Accessibility Statement

This accessibility statement applies to NHS Pathways Web.

NHS England is committed to making our digital services accessible in accordance with The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This legislation mandates that public sector websites and applications meet the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

We want as many people as possible, including patients, clinicians and support staff, to be able to use NHS Pathways Web. 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
  • navigate most of NHS Pathways Web using a keyboard or speech recognition software
  • listen to most of NHS Pathways Web using a screen reader (including the most recent versions of Job Access with Speech (JAWS), NonVisual Desktop Access (NVDA) and VoiceOver)

We also aim to make NHS Pathways Web text as simple as possible to understand while being clinically correct.

You can get more advice from AbilityNet about how to make your computer or mobile phone easier to use if you have accessibility needs.

How accessible is NHS Pathways Web

We are aware that some parts of NHS Pathways Web are not fully accessible:

  • Pathways question screens: There is an issue where the focus order - the sequence in which users navigate through interactive elements using a keyboard - unpredictably shifts to answer buttons or explanatory text instead of the question heading, causing navigation difficulties. This fails WCAG 2.4.3 (Focus Order).

Feedback and contact information

If you find any problems not listed on this page, think we're not meeting accessibility requirements or wish to send us feedback, please contact us using the following email address: england.nhspathways-admin@nhs.net.

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 and Advisory and Support Service (EASS).

Technical information about NHS Pathways Web accessibility

NHS England 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

NHS Pathways Web has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard. NHS Pathways Web is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA Standard, due to the non-compliances listed below.

Non-compliance with accessibility regulations

  • Inconsistent focus order on Pathways question screen. We have identified an inconsistent behaviour affecting the focus order on the Pathways question screen, particularly when using different screen readers. This issue relates to WCAG 2.4.3. While the focus sometimes correctly lands on the question heading, allowing users to navigate through the answer options as intended, there are instances where reloading on screen unpredictably shifts the focus to one of the answer buttons or surrounding explanatory text. This requires users to manually locate the question heading or adjust their navigation, which may cause confusion and disrupt the expected flow of interaction. Fails WCAG 2.4.3 (Focus Order)

Preparation of this accessibility statement

This statement was prepared on 30 September 2024 and last reviewed on 30 September 2024. NHS Pathways web was last tested on 30 September 2024 against the WCAG 2.2 AA standard. We are committed to continuously improving accessibility and will conduct regular reviews and updates to ensure ongoing compliance and address any new issues that arise.

The test was carried out by a Pathways accessibility specialist. The most viewed pages based on a typical scenario of use were tested using automated testing tools. A further audit of the website was carried out to the WCAG 2.2 AA standard.