Marketing reputation

Website accessibility for practices: WCAG 2.2 basics

WCAG 2.2 for GP, dental and clinic websites: who the rules cover, ten quick checks, the new criteria, online forms and the accessibility statement.

Ava research teamPublished 7 min read

On this page
  1. Who the rules apply to
  2. How many of your patients this affects
  3. Ten checks that catch most problems
  4. What changed in WCAG 2.2
  5. Forms and online consultation tools
  6. Content habits that keep a site accessible
  7. Writing your accessibility statement
  8. Example: one afternoon, three fixes
  9. Frequently asked questions
  10. References

Key takeaways

  • Public sector websites must meet WCAG 2.2 at level AA and publish an accessibility statement; every practice, NHS or private, also owes reasonable adjustments under the Equality Act 2010.
  • One in four people in the UK reported a disability in 2023 to 2024, rising to about 45% of people over State Pension age, so accessibility is about most of your list, not a niche.
  • WCAG 2.2 added nine success criteria; the ones practices fail most often concern focus visibility, small tap targets and logins that rely on memory tests.
  • Online consultation and booking forms are where accessibility failures cost most, because a patient who cannot finish a form usually phones instead.

Who the rules apply to

Public sector bodies must make their websites and apps meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, unless there is a valid legal reason not to, and publish an accessibility statement[1]. Whether a particular GP partnership or dental contractor counts as a public sector body under those regulations is a legal question worth checking with your commissioner or adviser, because practices are independent contractors. Many NHS practices are expected to meet the standard through their contracts and supplier frameworks in any case.

That question matters less than it seems. The Equality Act 2010 already requires service providers to make reasonable adjustments for disabled people, and that duty includes providing information in an accessible format. A website that a screen reader user cannot navigate, or a booking form that cannot be completed without a mouse, is hard to defend as a reasonable approach for any practice, NHS or private.

How many of your patients this affects

In 2023 to 2024, one in four people in the UK were disabled, 16.8 million people or 25% of the population[2]. The share rises sharply with age: 12% of children, 24% of working-age adults and 45% of adults over State Pension age[2]. Practices with older lists should assume that a large minority of website visitors have a visual, motor, cognitive or hearing impairment, or a combination.

People in the UK reporting a disability, by age group, 2023 to 2024
People in the UK reporting a disability, by age group, 2023 to 2024Bar chart. Children: 12%; Working-age adults: 24%; Adults over State Pension age: 45%.ChildrenChildren: 12%12%Working-age adultsWorking-age adults: 24%24%Adults over State Pension ageAdults over State Pension age: 45%45%People in the UK reporting a disability, by age group, 2023 to 2024Bar chart. Children: 12%; Working-age adults: 24%; Adults over State Pension age: 45%.ChildrenChildren: 12%12%Working-age adultsWorking-age adults: 24%24%Adults over State Pension ageAdults over State Pension age: 45%45%

Source: GOV.UK (Department for Work and Pensions), 2025[2]

Show the data
ItemValue
Children12%
Working-age adults24%
Adults over State Pension age45%

Access gaps also follow housing and income. ONS found adults renting from a council were 46% more likely than outright homeowners to report difficulty contacting their GP practice[3]. Clear pages that work on an older phone with a weak connection help the same patients who struggle most on the phone.

Ten checks that catch most problems

You do not need a specialist to find the worst issues. Set aside an hour, use a laptop and a phone, and work through these checks on your home page, your contact page and your online request form.

A one-hour accessibility check for practice websites
CheckHow to test itWhat good looks like
Keyboard onlyUnplug the mouse and press Tab through the pageEvery link, button and field can be reached and used in a logical order
Visible focusWatch where the focus goes while tabbingA clear outline shows which item is selected and nothing hides it
HeadingsUse a free browser extension that lists headingsOne main heading, then a sensible outline of section headings
Link textRead the links out of contextEach link says where it goes, not click here
Colour contrastRun a contrast checker on body text and buttonsText is readable against its background, including on photos
Zoom and reflowZoom the browser to 400% or view on a small phoneNo sideways scrolling and nothing overlaps
ImagesCheck the alternative text on key imagesMeaningful images are described; decorative ones are skipped
FormsSubmit a form with mistakesErrors are named in words next to the field, and entries are kept
Tap targetsTry every button on a phone with your thumbButtons are large enough and not crowded together
DocumentsOpen the PDFs patients are sent toKey information is also on a web page, not only in a scanned file

Write down every failure with the page address and a screenshot. That list becomes the issues section of your accessibility statement and the brief for your supplier.

What changed in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine success criteria[4]. Six of them sit at level A or AA, the levels that matter for compliance:

  • Focus Not Obscured (Minimum): the item a keyboard user has selected must not be hidden behind a sticky header, cookie banner or chat button.
  • Dragging Movements: anything done by dragging, such as a slider or map, needs a simple tap or click alternative.
  • Target Size (Minimum): pointer targets should be at least 24 by 24 CSS pixels, with listed exceptions[4].
  • Consistent Help: if you offer help, such as a phone number or contact link, it should appear in the same place on each page.
  • Redundant Entry: do not make patients type the same information twice in one process; prefill it or let them select it.
  • Accessible Authentication (Minimum): logins should not depend on memorising or transcribing codes or solving puzzles without an alternative, such as allowing password managers and copy and paste.

Cookie banners and floating chat buttons are the most common cause of focus problems on practice sites. Test the page with the banner open and closed.

Forms and online consultation tools

The online request form is the page where accessibility costs most. In the 2026 GP Patient Survey, 75.7% of patients who used the NHS App to contact their practice rated the experience as good, compared with 67.5% of those using a different website or app[5]. Some of that gap is about familiarity and design. If your own form is harder to use than the app, patients either abandon it or phone.

  1. Ask your supplier for their current accessibility statement and the date of their last audit.
  2. Test the form yourself with the keyboard and with your phone's screen reader switched on.
  3. Check the time-out: patients who type slowly should be warned before a session expires and be able to extend it.
  4. Make sure each question has a visible label, not just grey placeholder text that disappears.
  5. Confirm what a patient sees after submitting, including a reference and what happens next.
  6. Offer an alternative route on the same page, such as phone or in person, for anyone who cannot use the form.

Content habits that keep a site accessible

Most accessibility problems on practice websites are not built into the template. They arrive later, when staff add a poster, a flu clinic notice or a new service page in a hurry. A short set of house rules prevents most of them.

  • Never publish text as an image. A photo of a poster about flu clinics cannot be read by a screen reader, enlarged cleanly or translated. Type the key details into the page and add the poster as a picture with a short description if you want it.
  • Use the page's heading styles rather than bold text, so the structure appears in the outline that screen reader users jump through.
  • Write link text that makes sense on its own, such as order a repeat prescription, instead of here or more.
  • Keep sentences short and explain clinical terms the first time you use them. Plain English helps patients with learning disabilities, patients reading in a second language and anyone reading on a small screen while worried.
  • Add captions to videos and a text summary of what they say.
  • Before uploading a PDF, ask whether the information should be a web page instead. Forms that patients must fill in should almost always be online forms or offered in other formats on request.

Put these rules on one page in your website guidance and include them in induction for anyone who can edit the site. A two-minute check before each update costs far less than a supplier audit to find the same problems a year later.

Writing your accessibility statement

The statement should explain how accessible the website is, where fixing something would be a disproportionate burden, and what your plans are for the remaining issues, particularly where the site is supplied by a third party[1]. Keep it factual and short.

  1. Say what the statement covers

    Name the website address and any separate booking or request tools hosted by suppliers.

  2. State the compliance level

    Say whether the site is fully, partially or not compliant with WCAG 2.2 AA, and why.

  3. List known issues

    Describe each problem in plain words, the page it affects and when you expect it to be fixed.

  4. Offer alternatives

    Explain how patients can get information in another format, such as large print, easy read, audio or by phone.

  5. Give a contact route

    Provide a named email address or phone number for reporting accessibility problems and say how quickly you respond.

  6. Date it

    Show when the statement was prepared and last reviewed, and review it at least yearly.

Example: one afternoon, three fixes

Example. A fictional dental practice runs the one-hour check. It finds that its book now button is hidden behind the cookie banner for keyboard users, the opening hours are an image with no text, and the new patient form clears every field when one answer is wrong. The practice asks its web supplier to fix the banner and form, replaces the image with text the same day, and publishes a statement listing the two supplier fixes with target dates. Reception logs calls from patients who say they could not use the form, so the practice can see whether the fixes worked.

Frequently asked questions

Do private clinics have to meet WCAG 2.2?

The public sector regulations are aimed at public sector bodies, but the Equality Act duty to make reasonable adjustments applies to private providers too. WCAG 2.2 AA is the clearest benchmark for showing you have taken that duty seriously.

Is an accessibility overlay or widget enough?

No tool can fix missing labels, poor headings or inaccessible forms on its own. Fix the underlying pages and treat any widget as an extra, not a solution.

How often should we test?

Run the quick check after every significant change, such as a new form or page template, and do a full review of the statement at least yearly.

Our supplier says the site is compliant. Is that enough?

Ask for their audit date and statement, then run your own quick checks. Content you add, such as images of text or scanned PDFs, can break compliance even on a compliant template.

References

  1. GOV.UK (2026). Understanding accessibility requirements for public sector bodies (opens in a new tab) ↑

  2. GOV.UK (Department for Work and Pensions) (2025). Family Resources Survey: financial year 2023 to 2024 (opens in a new tab) ↑

  3. Office for National Statistics (2026). Experiences of NHS healthcare services in England: September 2026 (opens in a new tab) ↑

  4. W3C Web Accessibility Initiative (2023). What's new in WCAG 2.2 (opens in a new tab) ↑

  5. Ipsos (GP Patient Survey provider for NHS England) (2026). 2026 GP Patient Survey results released (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo