Is web accessibility a legal requirement for care providers?

Under the Equality Act 2010, service providers must make reasonable adjustments so disabled people aren't put at a substantial disadvantage, and that includes websites. Public sector bodies have stricter, explicit rules, but private care providers are still expected not to exclude disabled users. WCAG 2.2 AA is the recognised standard for meeting that bar. This is general guidance, not legal advice.

What level of WCAG should a care website aim for?

Aim for WCAG 2.2 Level AA. It is the widely accepted target for public-facing sites and covers the things that matter most for an older audience: readable text, strong colour contrast, keyboard navigation and clear focus states.

Do accessibility overlay widgets make my site compliant?

No. Overlay or 'accessibility toolbar' widgets bolt onto a site but rarely fix the underlying problems, and can get in the way of the assistive technology people already use. Real accessibility comes from how the pages are built, not a plugin laid on top.

Web Accessibility (WCAG 2.2) for Care Providers

Accessibility often gets filed under "technical compliance" — a box to tick, a badge to add. But for a care provider it's something more practical than that. The people using your website are, on average, older than the general web. Many have reduced vision, less steady hands, hearing loss, or are navigating a stressful moment on a phone in a hospital corridor. If your site doesn't work for them, you don't just fail an audit — you lose the very people you exist to help. Here's what accessibility really means, in plain terms.

What WCAG 2.2 actually is

WCAG stands for the Web Content Accessibility Guidelines — the internationally recognised standard for making websites usable by people with disabilities. Version 2.2 is the current release, and it's organised into three levels: A, AA and AAA. For a public-facing care website, Level AA is the sensible target. It's the level regulators, procurement teams and accessibility auditors look for, and it covers the issues that affect the most people without demanding perfection.

Why it matters more in care than most sectors

Think about who actually reads a care home or clinic website. It's an 82-year-old checking your services, a daughter with a migraine researching at midnight, a patient with a tremor trying to book an appointment. Accessibility features aren't a niche courtesy for these visitors — they're the difference between a completed enquiry and a frustrated exit. Larger text, strong contrast and a form that works with a screen reader help everyone, but for an older care audience they're close to essential.

The fixes that make the biggest difference

You don't need to memorise all fifty-odd WCAG criteria. A handful of things account for most of the real-world benefit:

Readable text. Generous font sizes, real headings, and text that reflows when someone zooms to 200%. No tiny grey captions on white.
Strong colour contrast. Body text needs a contrast ratio of at least 4.5:1 against its background. Pale-on-pale looks elegant to a designer and invisible to someone with cataracts.
Keyboard and focus. Every link, button and form field should be reachable with the Tab key, with a clear visible outline showing where you are. Plenty of people never touch a mouse.
Descriptive alt text. Photos of your home or team need written descriptions so screen-reader users get the same sense of the place.
Labelled, forgiving forms. Clear labels, helpful error messages, and large tap targets. WCAG 2.2 specifically added rules to make forms and dragging easier for people with limited dexterity.

What to be wary of

The biggest trap is the "accessibility overlay" — a widget you drop onto a site that promises instant compliance with a floating toolbar. They rarely fix the underlying problems, sometimes clash with the assistive technology people already rely on, and have been the subject of legal complaints in their own right. Real accessibility lives in how the pages are built: clean HTML, sensible structure, proper contrast. There's no plugin shortcut. Be equally cautious of a "get compliant" badge that no one has actually tested against real assistive technology.

Where the law sits

Under the Equality Act 2010, providers of services to the public must make reasonable adjustments so disabled people aren't placed at a substantial disadvantage — and courts and regulators increasingly read that as including websites. Public sector bodies have explicit, stricter obligations; private care providers aren't off the hook, but the expectation is proportionate. Meeting WCAG 2.2 AA is the clearest way to show you've taken it seriously. This is general guidance, not legal advice — check your specific obligations with a qualified adviser.

The upshot

Accessibility and good design aren't in tension — they're the same thing done properly. A site that's fast, clearly written, easy to navigate and readable by everyone tends to convert better, rank better and age better. Treat WCAG 2.2 AA not as a hurdle but as a description of a website that genuinely works for the people you serve.

Accessibility is baked into every care website we build, and it underpins how we approach healthcare SEO too — because a site that's easy for people to use is easy for search engines to read. See how it comes together for care homes.

Web accessibility (WCAG 2.2) for care providers: a plain guide