NHS Digital Accessibility Standards — WCAG 2.1 AA Requirements 2026

„What digital accessibility standards does the NHS require?" That's a question many NHS managers, digital leads, and healthcare providers ask when they hear about the growing legal requirements for accessible digital services.

In this guide, we'll explain what the NHS digital accessibility standards are, who they apply to, and what you need to do to comply.

What are NHS Digital Accessibility Standards?

NHS England has established clear digital accessibility standards that apply to all NHS organisations. These standards are based on:

• WCAG 2.1 Level AA — the core technical standard
• Equality Act 2010 — the legal framework
• Public Sector Bodies Accessibility Regulations 2018 (PSBAR) — the regulatory requirement
• NHS England guidance — specific NHS implementation guidance

Who must comply with NHS digital accessibility standards?

The standards apply to all NHS organisations that provide digital services:

1. NHS Trusts

• Acute trusts — hospitals and specialist services
• Mental health trusts — mental health services
• Community trusts — community health services
• Ambulance trusts — emergency services

2. Integrated Care Boards (ICBs)

• ICBs — planning and commissioning services
• Primary care — GP practices, dental, pharmacy

3. Other NHS bodies

• NHS England — national digital services
• NHS Digital — digital infrastructure
• NHS Improvement — quality and improvement

What are the specific requirements?

The NHS digital accessibility standards require compliance with WCAG 2.1 Level AA. Here are the key requirements:

1. Websites

All NHS websites must be accessible:

• Alternative text — for all clinical and non-clinical images (WCAG 1.1.1)
• Colour contrast — minimum 4.5:1 for normal text (WCAG 1.4.3)
• Keyboard accessibility — all functions with Tab key (WCAG 2.1.1)
• Form labels — all input fields must have labels (WCAG 3.3.2)
• Heading structure — logical H1-H6 hierarchy (WCAG 1.3.1)
• Skip links — „Skip to main content" (WCAG 2.4.1)
• Focus indicators — visible focus (WCAG 2.4.7)

2. Patient portals

Patient portals are critical functionality and must be accessible:

• Login and registration — screen reader and keyboard compatible
• Appointment booking — accessible date selection, provider choice
• Test results — accessible PDFs with proper tagging
• Billing and payments — accessible payment processes
• Messaging — accessible chat and notifications

3. Mobile apps

NHS mobile apps must be accessible:

• Screen reader compatibility — VoiceOver, TalkBack (WCAG 4.1.2)
• Keyboard operation — all functions with keyboard (WCAG 2.1.1)
• Touch targets — minimum 44x44px (WCAG 2.5.5)
• Contrast — sufficient contrast (WCAG 1.4.3)

4. Telehealth platforms

Telehealth services must be accessible:

• Captions — for all video consultations (WCAG 1.2.2)
• Keyboard operation — all functions with keyboard (WCAG 2.1.1)
• Chat function — accessible with ARIA, keyboard, focus (WCAG 4.1.2)

5. Digital documents

All digital documents must be accessible:

• PDF tagging — proper tagging structure
• Alternative text — for images in documents
• Reading order — logical reading order
• Language — language specified

WCAG 2.1 AA vs WCAG 2.2 AA — What's the difference for NHS?

NHS England currently requires WCAG 2.1 Level AA. However, NHS App integration requires WCAG 2.2 Level AA.

Recommendation: NHS organisations should aim for WCAG 2.2 Level AA to be prepared for future requirements and NHS App integration.

What are the accessibility statement requirements?

Under PSBAR 2018, all NHS organisations must publish an accessibility statement on their website. The statement must:

• Explain how accessible the website is
• List non-accessible parts
• Explain how users can report problems
• State when the statement was last updated

How to test your NHS website for accessibility

Step 1: Use a free HHS checker

Use the free UK HHS checker to scan your healthcare website against WCAG 2.2 Level AA.

Step 2: Manual testing

Conduct manual tests:

• Keyboard test — can everything be operated with the Tab key?
• Screen reader test — is the content logical with a screen reader?
• Contrast test — is the text readable?

Step 3: Patient portal testing

Test your patient portal specifically — this is often the most critical functionality for patients.

Step 4: Document everything

Document all tests and improvements. This serves as evidence of your compliance efforts.

Frequently Asked Questions — NHS Digital Accessibility

Internal links — NHS Accessibility Resources