Healthcare website accessibility is not a decorative compliance exercise. It determines whether someone can understand a service, find urgent contact information, complete a booking, read an error message or use a digital pathway with the technology and abilities they have.
For a pharmacy, clinic or online healthcare operator, the most useful approach is to treat accessibility as part of service design. Start with the journeys people must complete, use recognised technical standards, test with assistive technologies and real users, and keep accessibility under control as content and software change.
How should a healthcare organisation improve website accessibility?
Prioritise the patient tasks with the greatest consequence: understanding a service, checking eligibility, contacting the provider, booking, completing forms and obtaining support. Use WCAG 2.2 AA as a practical technical target, combine automated checks with keyboard, screen-reader, zoom and user testing, and give every defect an owner and deadline.
- Fix blockers in high-value and high-risk journeys before polishing low-traffic pages.
- Make content, forms, authentication and error recovery understandable without one particular device or sense.
- Publish a truthful accessibility position and maintain it through design, development and editorial governance.
Accessibility is part of patient access
A healthcare website often acts as the front door to a real service. If the text cannot be enlarged, a keyboard user cannot reach the booking button, a form error is shown only in red, or a screen reader receives unlabeled fields, the barrier is operational rather than cosmetic.
The Equality Act 2010 requires service providers to anticipate barriers and make reasonable adjustments for disabled people. Government guidance for service providers explains that adjustments may include changing how a service is delivered and providing information in an accessible format. Separate public-sector website and app regulations apply to public-sector bodies. A private pharmacy or clinic should not claim that every public-sector rule automatically applies to it, but it still needs to consider its Equality Act responsibilities and obtain legal advice for its circumstances.
Organisations providing publicly funded NHS care or adult social care must also have regard to the NHS England Accessible Information Standard. Its purpose is broader than a website checklist: people should receive information they can access and understand, plus the communication support they need.
Use WCAG as the technical framework, not the whole programme
The World Wide Web Consortium’s Web Content Accessibility Guidelines 2.2 organise testable requirements under four principles: content should be perceivable, operable, understandable and robust. W3C recommends using the latest WCAG version when developing or updating accessibility policies.
WCAG 2.2 AA is a sensible procurement and delivery target for many healthcare websites, but passing a checklist does not guarantee that every person can use the service. Technical conformance must be combined with plain content, usable journeys, alternative channels and testing by people with relevant access needs.
Map the critical journeys before running a scan
Create a task inventory and rank each journey by patient consequence, traffic and change frequency. Typical priorities include:
- finding the pharmacy, clinic, opening hours and contact options;
- understanding who provides a service and where it is delivered;
- checking price, eligibility and what happens next;
- booking, cancelling or changing an appointment;
- completing a consultation or enquiry form;
- reading preparation, safety and aftercare information;
- using an account, payment or identity-check journey; and
- requesting information in another format or getting human help.
Test these tasks across the complete chain, including third-party booking tools, payment pages and embedded forms. A compliant homepage does not help if the external calendar cannot be used with a keyboard.
Make healthcare content easier to perceive and understand
Use a clear hierarchy
Give every page one descriptive H1, arrange headings in a logical order and use lists for genuinely sequential or grouped information. Screen-reader users often navigate by headings, while all readers benefit from being able to scan a complex service page.
Write for decisions, not internal terminology
Explain the service, provider, location, process, fees, limitations and next step in plain UK English. Expand abbreviations on first use. Put important conditions beside the action they affect instead of hiding them in a general FAQ.
Do not rely on colour, position or imagery alone
A required field, booking status or warning needs a textual cue. Maintain sufficient contrast, provide meaningful alternative text for informative images, and leave decorative images with empty alt attributes when the implementation supports it. Captions, transcripts and audio description should be planned according to the media and information conveyed.
Let people resize and reflow content
Test text enlargement, browser zoom and narrow mobile widths. Content should not disappear behind fixed panels or force two-direction scrolling for ordinary reading. NHS England’s Accessible Information Standard requirements describe practical expectations including keyboard use, screen-reader use, speech recognition, mobile access and zoom without text spilling off the screen.
Make navigation operable without a mouse
Every link, button, menu, dialog and form control should be reachable and usable with a keyboard. The focus indicator must be visible, the order should follow the visual and logical sequence, and focus must not become trapped or disappear behind a sticky banner.
Add a skip link where repeated navigation is substantial. Use real buttons for actions and real links for destinations. Custom components need accessible names, roles, states and keyboard behaviour; styling a generic container to look clickable is not enough.
WCAG 2.2 added criteria relevant to modern healthcare journeys, including focus not being obscured, alternatives to dragging, minimum target sizes, consistent help, avoiding unnecessary repeated entry and accessible authentication. These are particularly useful checks for calendars, questionnaires and patient accounts.
Design forms around recovery, not perfect input
Healthcare forms can be stressful, long and consequential. Accessibility improves when the form makes the task and recovery route obvious:
- use a visible label for every field;
- group related choices with a clear question or legend;
- identify required fields in text, not colour alone;
- provide instructions before the input that needs them;
- show errors beside the field and in a useful summary;
- move focus to the error summary after submission;
- preserve valid answers when another field fails;
- allow review before a consequential submission; and
- provide a human support route when the digital path cannot be completed.
Avoid collecting clinical or identity information before it is necessary. Accessibility, privacy and conversion often improve together when unnecessary fields and repeated questions are removed.
Do not outsource accessibility to an overlay
An accessibility toolbar or automated overlay cannot repair missing labels, confusing content, broken keyboard behaviour or an inaccessible third-party form. Automated scanners are useful for repeatable checks such as missing attributes, contrast failures and document structure, but they cannot decide whether instructions make sense or whether a booking can be completed under real conditions.
Use automation as one layer in a broader method:
- automated testing across representative templates;
- manual keyboard and zoom checks;
- screen-reader testing on the critical journeys;
- testing with disabled users or specialist researchers;
- content and document review; and
- regression checks before and after releases.
Procure accessible suppliers and third-party tools
Accessibility can fail at a boundary the healthcare organisation does not code itself. Booking systems, chat widgets, cookie controls, maps, payment services and document viewers all need scrutiny.
Ask suppliers for a current accessibility statement or conformance report, the standard and version tested, known limitations, testing methods, remediation process and product roadmap. Verify important claims in the actual configured journey. Contract terms should identify who owns defects and how urgent blockers are handled.
For online pharmacies, accessibility sits alongside sector-specific digital governance. The GPhC’s current guidance for pharmacy services provided at a distance expects digital platforms to be clear, accurate, effective, professional and secure. Pharmacy identity, contact, feedback and privacy information should be easy to find and use.
Create an accessibility operating system
Assign ownership across product, design, development, content, clinical review and procurement. Keep a register of issues with the affected journey, user impact, severity, owner, target date and evidence of retesting. High-consequence blockers should not wait for a redesign.
Include accessibility in design acceptance criteria, code review, content publishing, supplier selection and release testing. Train editors to use headings, links, tables, alternative text and documents correctly. A technically sound template can deteriorate quickly when everyday publishing is unmanaged.
If an accessibility statement is required or voluntarily published, keep it specific and honest. State the standard used, known limitations, alternative contact routes, how to report a problem and when the page was reviewed. Do not claim full compliance on the basis of one automated scan.
A practical 90-day improvement plan
Days 1–30: find and remove blockers
- List critical patient tasks, templates and third-party components.
- Run automated and manual checks on representative journeys.
- Fix keyboard traps, missing labels, invisible focus, inaccessible errors and blocked zoom first.
- Create an issue register and name accountable owners.
Days 31–60: strengthen content and components
- Rewrite priority service pages in clear, structured language.
- Repair reusable navigation, forms, modals, cards and booking patterns.
- Review PDFs and provide accessible HTML alternatives where appropriate.
- Test the complete journey with assistive technology and relevant users.
Days 61–90: make improvement durable
- Add accessibility criteria to design, development and editorial workflows.
- Agree supplier remediation plans for third-party barriers.
- Publish or update the accessibility position and support route.
- Schedule regression testing and report unresolved high-impact issues.
Measure access and task completion
Track more than an automated score. Useful measures include completion and abandonment by journey, form-error rates, repeated errors, support contacts caused by digital barriers, time to remediate critical defects, percentage of components with test coverage and the age of the accessibility statement or audit.
Segment carefully and protect privacy. Accessibility data should help remove barriers, not create new profiling risks. Qualitative feedback and observed task completion often explain problems that analytics cannot.
Pharmacy Mentor designs and develops healthcare journeys around clarity, accessibility, trust and measurable action. Explore our pharmacy website design and development service, the UK clinic website blueprint and our approach to healthcare app development. To review a current website or plan an accessible rebuild, book a Pharmacy Mentor consultation.
Frequently asked questions
What standard should a UK healthcare website follow?
WCAG 2.2 AA is a useful current technical target for many projects. Legal requirements depend on the organisation and service, so combine the standard with Equality Act responsibilities, any public-sector rules and sector-specific obligations.
Can an automated accessibility scan prove compliance?
No. Automated tools find only some issues. Manual keyboard, zoom and screen-reader testing, content review and testing with people who have relevant access needs are also required for a credible assessment.
Does the NHS Accessible Information Standard apply to pharmacies and clinics?
Organisations providing publicly funded NHS care or adult social care must have regard to the standard. Other providers can still use its approach as useful practice, while checking the exact legal and contractual position for their services.
How often should a healthcare website be tested?
Test critical journeys before launch, after material changes and on a planned recurring basis. Reusable components and high-consequence tasks should have regression checks so accessibility does not deteriorate as the site evolves.