Do pharmacy websites have to meet accessibility law?

Who actually uses a pharmacy website?

The argument for accessibility in pharmacy does not need the law — the demographics establish it first. Pharmacy's users are older than the general retail population and more likely to have a disability. By the nature of the service, they are also disproportionately managing precisely the conditions that affect the capacity to use a website.

Consider what a pharmacy's own patient list contains. People with diabetic retinopathy, glaucoma and macular degeneration, whose sight is affected by the conditions for which they collect medicines. People with rheumatoid arthritis, Parkinson's disease and the consequences of stroke, whose dexterity affects their capacity to operate small targets and complete timed interactions. People experiencing cognitive change, whether through age, medication or condition. People whose first language is not English, in a service where misunderstanding carries clinical consequence. And carers, often older themselves, using the service on another person's behalf.

A retailer whose checkout is inaccessible loses a sale. A pharmacy whose consultation flow is inaccessible has excluded a person from a health service — and excluded them on the basis of the very characteristics that brought them to a pharmacy. That distinction is why accessibility in this sector deserves treatment as a clinical access matter, not a design preference.

What is the legal position?

The Equality Act 2010 requires those providing services to the public not to discriminate against disabled people, and to make reasonable adjustments so that disabled people are not placed at a substantial disadvantage. A website that offers services, provides information and takes transactions falls within that framework. No statute prescribes a specific technical standard for private businesses, but that does not alter the position. The duty attaches to the outcome, not the specification.

Separate regulations impose more prescriptive obligations on public sector bodies, including published accessibility statements and conformance with a named standard. Whether any particular NHS contracting arrangement brings a community pharmacy within those regulations is a question of scope — take specific advice rather than assuming. The Equality Act duty, however, applies to private providers either way. The practical answer for a pharmacy does not depend on resolving it.

What is the benchmark for reasonableness?

The law requires reasonable adjustment without defining it technically, so the recognised international standard operates as the measure of reasonableness. The Web Content Accessibility Guidelines, at level AA, are that benchmark. A site conforming to them is substantially better placed than one that does not — practically, and in any later dispute.

The guidelines organise around four principles a pharmacy operator can usefully understand without mastering the individual criteria. Content must be perceivable: available to senses other than the one the designer assumed, which means text alternatives for images, captions for audio and sufficient contrast. It must be operable: usable without a mouse, without precise timing and without movement that may cause difficulty. It must be understandable: predictable in behaviour, clear in language and helpful when an error occurs. And it must be robust: built so that assistive technologies can interpret it reliably.

An operator does not need expertise in the criteria. An operator needs conformance stated in the build specification, plus evidence of testing at handover — the arrangement the protective brief already provides for.

Where do pharmacy sites fail specifically?

The general failures affect every sector. Several, though, are characteristic of pharmacy and worth naming individually.

Notice the pattern in that table. Almost every remedy concerns how the site is built rather than what is added to it. That is why the cost of conformance is modest at specification and considerable at retrofit.

Why is the consultation flow the highest-stakes surface?

Every accessibility failure on a pharmacy website is a failure. A failure in the consultation flow is a different order of problem. A person who cannot complete the assessment cannot obtain the medicine. And the flow is the gateway the design guide describes as clinical instrument, conversion surface and evidence generator at once.

Four characteristics make it the surface most likely to exclude. It is long, which compounds every difficulty with timing, memory and fatigue. It is conditional: questions appear and disappear according to previous answers, which assistive technology handles poorly unless the changes are announced deliberately. It is consequential: an error is not an inconvenience but a clinical inaccuracy entering a record. And it often involves uploads — photographs and documents — which are among the least accessible interactions in ordinary web design.

The design responses correspond to those characteristics. Announce conditional changes, so a screen reader user learns that new questions have appeared. Preserve answers across interruption — a person who needs forty minutes should not lose the first thirty. Provide alternatives to upload wherever the clinical purpose permits, and a human route wherever it does not. And apply the site's error-handling discipline most rigorously here. The applicant who abandons at an unexplained validation failure has been excluded by a defect, not by a decision.

What of alternative channels?

An accessible telephone route, a supported in-person option and a willingness to complete the process alongside a patient are all legitimate reasonable adjustments. A pharmacy should offer them however accessible its website becomes.

They do not, however, discharge the duty by themselves. Directing disabled users away from the service every other user may access is hard to call equivalent treatment. That is especially true where the online route offers advantages the alternative does not: privacy on sensitive matters, availability outside opening hours, and a written record the patient keeps. A person seeking treatment for a condition they would rather not discuss aloud has a real interest in the accessible online route, not a telephone alternative. That interest is precisely what an anticipatory duty exists to protect.

The correct answer is therefore both: a website the great majority can use independently, plus genuine alternatives for those no website will suit, staffed by people who know they exist.

How is it built in rather than retrofitted?

Accessibility is procured, not purchased. You get it by specifying it before construction, not by buying it afterwards. The mechanism is the build brief, and three clauses carry the requirement.

A stated standard, naming conformance at level AA as a deliverable rather than an aspiration. An acceptance test, requiring testing evidence at handover rather than an assurance — an untested claim of conformance is the most common form the requirement takes, and the least useful. And ownership of remediation, establishing who corrects defects found after launch and at whose cost. That determines whether findings are welcomed or resisted.

The economics strongly favour this arrangement. Building accessibly costs comparatively little. Most criteria concern semantics, keyboard behaviour, contrast and error handling — all things a competent developer implements at no extra time once specified. Retrofitting costs materially more. Where an inaccessible consultation flow needs rebuilding rather than adjustment, the cost approaches that of the original build. This mirrors the wider point the agency guide makes about regulated builds: the expensive failures are architectural, while the cheap corrections are cosmetic.

How is it tested without a specialist budget?

A pharmacy need not commission a formal audit to identify the majority of its problems. Four methods available at no cost will find most of what matters.

Automated scanning finds a proportion of issues, commonly estimated at around a third. It is a reasonable first pass and wholly insufficient alone. Keyboard testing needs nothing more than setting the mouse aside and trying to complete a consultation using only the keyboard. It exposes focus, order and trap problems immediately, and it is the single most informative test available. Zoom and reflow testing means enlarging text substantially and checking whether the page remains usable — which matters to a large share of a pharmacy's actual users. And screen reader spot-checking, using the software already on most operating systems, establishes whether the site makes sense when it cannot be seen.

Beyond those, the most valuable testing involves disabled users themselves. A pharmacy is unusually well placed to arrange it: its patient list contains the people concerned, and many will help willingly if asked respectfully and compensated for their time. A single session watching a person with limited vision attempt a consultation will produce findings no automated tool reports.

What of the accessibility statement?

A published accessibility statement is mandatory for public sector bodies and good practice for everyone else. For a private pharmacy its value is practical rather than formal. It records what conformance has been achieved, discloses known limitations honestly, and gives a person in difficulty a route to prompt help.

A statement that claims full conformance without evidence is worse than none — it converts a technical shortcoming into a misleading representation. Better to acknowledge that certain older documents remain unconverted, that remediation is scheduled, and that any user in difficulty can telephone a named route for help. That is both more accurate and considerably more useful to the person reading it.

The statement also belongs in the change-control arrangements that govern the website's other regulated surfaces. A document describing a site as it stood two redesigns ago serves nobody.

Key takeaways

FAQs