Skip to content
HIPAA-Compliant AgencyBAA Signed Before PHINHS Digital StandardsWCAG 2.2 AA
HIPAA-Compliant AgencyBAA Signed Before PHINHS Digital StandardsWCAG 2.2 AA

WCAG 2.2 AA Accessibility for Healthcare

We build clinical-grade platforms that are usable by everyone—ensuring seamless and equal access for patients with visual, motor, or cognitive impairments.

WCAG 2.2 AA (Web Content Accessibility Guidelines)Equality Act 2010Public Sector Bodies Accessibility Regulations 2018
Web Interface • Accessible
WCAG 2.2

Accessibility Audit Status

Contrast Ratio7.1:1 (AAA Pass)
Keyboard FocusVisible & Trapped
ARIA LandmarksFully Implemented
Screen ReaderJAWS & NVDA Ready

Accessibility Guidelines Met

WCAG 2.2 AA Accessibility Met
No Keyboard Traps / Full Tab Order
Descriptive Alt Text for All Media
Minimum Target Touch Dimensions

Screen Reader

Tested & Optimized

Keyboard Nav

Fully Functional

Why WCAG Matters

Accessibility: A Legal and Ethical Obligation

WCAG 2.2 AA compliance ensures that every patient - regardless of disability, device, or context - can access your digital healthcare services without barriers.

Legal Exposure

UK healthcare providers must comply with the Equality Act 2010 and the Public Sector Bodies Accessibility Regulations. Failing to provide accessible digital services is not a design choice - it is potential discrimination.

1 in 5 people

In the UK have a disability. Inaccessible healthcare websites exclude 14 million potential patients from critical services.

Inclusive Healthcare Access

When a visually impaired patient tries to book an appointment, a deaf patient seeks information about their procedure, or someone with a cognitive disability attempts to understand their prescription - an inaccessible website fails them at the most critical moment. WCAG 2.2 AA compliance is the standard that prevents this.

Equality Act Risk

Failure to provide reasonable adjustments for disabled users can lead to legal claims under the Equality Act 2010.

NHS Procurement Block

DTAC and NHS Digital Service Standard require WCAG 2.2 AA compliance before NHS contracts can be awarded.

Accessibility Statement

Public sector bodies must publish a compliant accessibility statement and actively fix reported barriers.

An inaccessible healthcare website is not just a usability problem.

It is a barrier to care for the patients who need your services most.

Common Failures

Where healthcare websites fail accessibility audits

Accessibility failures in healthcare are rarely intentional - but they are consistent. These are the patterns we see repeatedly when auditing healthcare digital services.

What WCAG 2.2 AA Means

WCAG 2.2 AA: the current accessibility standard for healthcare

WCAG 2.2, published by the World Wide Web Consortium (W3C) in October 2023, is the current version of the Web Content Accessibility Guidelines. It introduces nine new success criteria on top of WCAG 2.1, with particular emphasis on improving accessibility for users with cognitive disabilities, low vision, and those using mobile or touch devices.

For healthcare websites, WCAG 2.2 AA compliance means patients with visual impairments can read appointment information using screen readers, users with motor disabilities can navigate forms using a keyboard alone, and patients with cognitive conditions can complete multi-step booking processes without confusion. These are not optional enhancements - for public sector bodies in the UK, compliance is a legal requirement under the Public Sector Bodies Accessibility Regulations 2018.

The Equality Act 2010 requires all UK service providers, including private healthcare providers, to make reasonable adjustments for disabled users. While the Act does not name WCAG directly, courts regularly use WCAG 2.2 AA as the benchmark for determining whether a website meets its duties under the Act. For US healthcare providers receiving federal funding, Section 508 of the Rehabilitation Act and the forthcoming DOJ ruling under the Americans with Disabilities Act will require WCAG 2.1 AA conformance from May 2026.

What Changed

What's new in WCAG 2.2

WCAG 2.2 introduced nine new success criteria beyond WCAG 2.1. These four have the most direct impact on healthcare websites and patient platforms.

01

3.3.8 Accessible Authentication

Authentication processes must not rely on cognitive function tests such as remembering a password, solving a puzzle, or transcribing characters. This affects patient portal logins, 2FA flows, and practitioner dashboards. Biometric options or password manager support can meet this criterion.

02

2.4.11 Focus Not Obscured

When a user navigates via keyboard, the focused element must not be hidden behind other content such as cookie banners, sticky headers, or chat widgets. Healthcare forms and booking interfaces are common offenders when floating elements overlap focused fields.

03

2.5.8 Target Size (Minimum)

Interactive targets must be at least 24 by 24 CSS pixels, with exceptions for inline links and essential controls. This directly affects appointment booking buttons, dosage selectors, and mobile patient portal navigation elements.

04

3.3.7 Redundant Entry

Multi-step forms must not require users to re-enter the same information across steps. For healthcare, this means once a patient enters their name, date of birth, or NHS number, that data must auto-populate in subsequent steps of long intake forms.

Legal Framework

UK legal requirements for accessible healthcare websites

Website accessibility is not just a best practice - it is a legal requirement under multiple overlapping frameworks. Here is how they apply to healthcare organisations.

01

Equality Act 2010

The Equality Act 2010 requires all UK service providers - including private healthcare clinics, hospitals, and telehealth platforms - to make reasonable adjustments for disabled users. Courts have consistently interpreted this to include digital accessibility. Non-compliance can result in claims for compensation, and the Act does not exclude small or private healthcare providers.

02

Public Sector Bodies Accessibility Regulations 2018

These regulations require UK public sector bodies - including NHS Trusts, GP surgeries, and publicly funded health organisations - to meet WCAG 2.1 AA standards (now superseded by WCAG 2.2 AA) and publish an accessibility statement. Compliance is monitored by the Government Digital Service (GDS), and sites that fail to meet the standard may face enforcement action.

03

European Accessibility Act 2025

The European Accessibility Act (EAA) comes into full effect across EU member states in June 2025, requiring digital products and services - including healthcare websites and patient portals - to meet harmonised accessibility standards. While the UK is no longer in the EU, UK healthcare providers serving EU patients will need to comply, and the EAA is expected to influence future UK legislation.

Why Accessibility Matters

The scale of the accessibility gap in healthcare

Accessible design is not optional - it affects millions of users and carries legal obligations.

0 million

Disabled people in the UK—roughly 1 in 5 adults facing significant digital barriers.

Office for National Statistics; Scope

0%

Top homepages with detectable WCAG failures in recent industry audits.

WebAIM Million Report 2024

0

New success criteria added in WCAG 2.2 to improve modern accessibility.

W3C, w3.org

0

The year UK law mandated WCAG compliance for public sector websites.

UK Public Sector Regulations 2018

These numbers show that accessibility is not a niche concern. With 14.6 million disabled people in the UK and 95.9% of homepages failing basic checks, the gap between what the law requires and what websites deliver is enormous - especially in healthcare.

Self-Assessment

WCAG 2.2 AA self-assessment checklist for healthcare websites

Use this 10-point checklist to evaluate whether your healthcare website or patient platform meets the WCAG 2.2 AA standard. Each item tests one of the most commonly failed success criteria.

01

Minimum 4.5:1 color contrast ratio for text and 3:1 for large elements.

02

Full keyboard operability for all menus, forms, and interactive buttons.

03

Visible focus indicators for all elements during keyboard navigation.

04

Associated labels and accessible names for all form controls and inputs.

05

Descriptive alt text for meaningful images and empty attributes for decorative ones.

06

Synchronized captions and audio descriptions for all video content.

07

Minimum 24x24 CSS pixel touch targets with sufficient adjacent spacing.

08

Authentication processes free from puzzles or complex cognitive tests.

09

No redundant data entry required in multi-step patient intake forms.

10

Full usability and readability at 400% zoom with no horizontal scrolling.

FAQ's

Frequently Asked Questions

Common questions about WCAG 2.2 AA compliance for healthcare websites, the law, and what it means for your platform.

Let's talk about your project

Get in touch with our team to discuss your project or ask any questions.

In the UK, yes. The Equality Act 2010 requires all service providers, including private healthcare providers, to make reasonable adjustments for disabled users. For public sector healthcare organisations, the Public Sector Bodies Accessibility Regulations 2018 specifically require WCAG 2.1 AA compliance (now superseded by WCAG 2.2 AA). In the US, Section 508 of the Rehabilitation Act applies to federally funded healthcare organisations, and from May 2026, websites of state and local government entities receiving federal funding must meet WCAG 2.1 AA under the DOJ's final ruling on ADA Title II.

Ready to Start Your Healthcare Project?

Let's discuss your goals and show you how we can build a secure, accessible, and high-performing healthcare website.

Healthcare projects portfolio brief - HIPAA & NHS Compliant Web Development