NHS App Accessibility — WCAG 2.2 AA Requirements 2026

„What accessibility standards does the NHS App require?" That's a question many healthcare organisations and developers ask when they start integrating with the NHS App.

In this guide, we'll explain what the NHS App accessibility requirements are, why they matter, and what you need to do to ensure compliance.

What is the NHS App?

The NHS App is the National Health Service's official mobile application. It allows patients to:

• View their health records — including test results, medications, and allergies
• Book appointments — with their GP practice
• Order prescriptions — manage repeat prescriptions
• Contact their GP — via secure messaging
• Manage their health — track health goals, access health information
• Access COVID-19 services — vaccination status, test results

The NHS App is being developed as a "world-leading tool for patient access", with the Single Patient Record (SPR) expected to be available via the App by 2028.

What are the NHS App accessibility requirements?

The NHS App integration requires WCAG 2.2 Level AA compliance. This is a higher standard than the NHS's general requirement of WCAG 2.1 Level AA.

Why WCAG 2.2 AA?

WCAG 2.2 Level AA adds 9 new success criteria compared to WCAG 2.1. These new criteria focus on:

• Mobile accessibility — better support for touch devices
• Cognitive accessibility — easier for people with cognitive disabilities
• User privacy — protection of user data
• Focus and navigation — better keyboard navigation

Key WCAG 2.2 AA requirements:

1. Target Size (2.5.8)

Pointer targets must be at least 24x24 CSS pixels (or have sufficient spacing). This is smaller than WCAG 2.1's 44x44px, but still ensures touch targets are accessible.

2. Consistent Help (3.2.6)

Help mechanisms must appear in the same place on every page.

3. Redundant Entry (3.3.7)

Information previously entered should be auto-populated to avoid redundant entry.

4. Accessible Authentication (3.3.8)

Authentication processes should not require cognitive function tests (like remembering passwords or solving puzzles).

5. Dragging Movements (2.5.7)

All operations that use dragging can be performed with a single pointer without dragging.

6. Focus Not Obscured (2.4.11)

Focus indicators must not be fully hidden by other content.

Why does accessibility matter for the NHS App?

Accessibility matters for the NHS App because:

1. Legal requirements

The NHS App must comply with the Equality Act 2010 and PSBAR 2018. Failure to make the App accessible could lead to discrimination claims.

2. Patient inclusion

All patients should be able to access their health records. 15% of disabled people have never used the internet, so the App must be accessible to those who can use it — and non-digital alternatives must be available for those who cannot.

3. NHS values

The NHS is committed to providing equal access to healthcare for all patients. Accessibility is a core NHS value.

4. Audit evidence required

NHS App integration requires accessibility audit evidence to demonstrate compliance.

What are the consequences of non-compliance?

1. Integration rejection

If your service does not meet WCAG 2.2 Level AA, your integration request will be rejected by NHS Digital.

2. Discrimination claims

Disabled patients can bring a discrimination claim under the Equality Act 2010. If successful, you could be ordered to pay unlimited compensation.

3. EHRC investigations

The EHRC can investigate and issue a non-discrimination notice.

4. Reputational damage

Failure to make your service accessible can lead to negative publicity and loss of patient trust.

How to achieve NHS App accessibility compliance

Step 1: Review WCAG 2.2 AA requirements

Review the WCAG 2.2 Level AA requirements and understand what is needed for compliance.

Step 2: Conduct an accessibility audit

Use the free UK HHS checker to scan your service against WCAG 2.2 Level AA. Document all violations and create a plan to fix them.

Step 3: Fix all violations

Follow the recommendations in the report to fix all violations.

Step 4: Conduct a formal accessibility audit

Conduct a formal accessibility audit with documented evidence of compliance.

Step 5: Submit evidence to NHS Digital

Submit your accessibility audit evidence as part of your NHS App integration request.

Frequently Asked Questions — NHS App Accessibility

Internal links — Healthcare Accessibility Resources