Website Accessibility for Clinics: A Plain-English Guide to WCAG (Without the Jargon)
Here's the thing nobody tells clinic owners when they're picking fonts and photos for their new website: the patients who most need clear, easy access to your booking page are often the same patients your beautiful new design is quietly locking out. We've sat with physio clinics, psych practices and dental surgeries who poured genuine 💖 into their branding and never once checked whether someone with low vision could actually read their opening hours. This isn't about ticking a legal box (though that matters too) — it's about whether the person who most needs your help can find your phone number.
What most clinics get wrong
We see the same handful of issues over and over, and almost none of them come from carelessness — they come from nobody knowing to check.
Gorgeous colour palettes that fail contrast ratios
Soft pastel-on-white or light-grey-on-white text looks calming and on-brand, and it's genuinely unreadable for a huge chunk of visitors — not just people with diagnosed low vision, but anyone on a phone in bright sunlight, or anyone over 45 whose eyes have changed and they haven't quite admitted it yet.
PDF-only intake forms
A downloadable PDF that a patient has to print, fill in by hand and bring to their appointment (or worse, one that isn't actually fillable on screen) is a wall for anyone using a screen reader, anyone with a tremor or limited fine motor control, and honestly, most people under 40 who don't own a printer.
Images with no alt text, and forms with no labels
A photo of your treatment room that a screen reader just calls "image" tells a blind visitor nothing. A booking field that just shows a placeholder like "Name" that disappears the second you click into it does the same thing — the label vanishes right when someone needs it most.
No visible way to navigate without a mouse
Plenty of people — including many with motor impairments, and plenty of power users besides — navigate entirely by keyboard (tab, enter, arrow keys). If your site's focus outline has been styled away or your dropdown menus only open on hover, keyboard-only visitors simply can't get through your site.
- Colour contrast: Paste your text and background hex codes into a free contrast checker (WebAIM's Contrast Checker is the standard one). You're aiming for a ratio of at least 4.5:1 for normal body text.
- Alt text: Right-click any image on your site and inspect it, or use a free browser extension like WAVE (from WebAIM) — it flags every image missing alt text on the page in one scan.
- Form labels: Click into every field on your booking and intake forms, then keep typing after you've filled it in. If the label disappears and doesn't come back, it's a placeholder, not a real label — it needs fixing.
- Heading structure: Use the WAVE extension's "structure" view (or your browser's inspector) to check your page runs one H1, then H2s, then H3s in order — not skipping levels or using headings purely for visual size.
- Keyboard navigation test: Put your mouse away entirely. Use only Tab, Shift+Tab and Enter to move through your homepage and your booking flow. Can you see, at every step, exactly which element is focused? Can you actually complete a booking?
How it actually works: WCAG levels in plain English
WCAG (Web Content Accessibility Guidelines) is the internationally recognised standard, and it's organised into three levels: A, AA and AAA. Think of A as the absolute floor — the minimum needed for a website to function at all for assistive technology. AA is the level most guidance, including Australian government and industry expectations, points to as the practical target — it covers contrast, labelling, keyboard access and structure, the exact things in the checklist above. AAA is a much higher, more specialised bar (things like sign-language interpretation for video content) that's genuinely difficult for most small business sites to fully achieve and isn't generally expected of a clinic website. For a clinic, aiming solidly at AA is the sensible, achievable goal.
Mistakes to avoid
- Relying on colour alone to convey meaning (like a red asterisk with no text label for required fields) — colour-blind visitors miss it entirely.
- Auto-playing video or carousels with no pause button, which can be genuinely distressing for visitors with cognitive or attention-related conditions.
- Treating an accessibility overlay widget (the little floating icon that promises instant compliance) as a substitute for actually fixing your contrast, labels and structure — they fix very little and can even interfere with screen readers.
- Writing alt text that's either missing or unhelpfully generic, like "IMG_2481" or "photo" — describe what's actually useful to know, like "physiotherapist assisting patient with resistance band exercise."
Worth being upfront about: full WCAG AA compliance across an entire website is a genuine, ongoing project — it touches every page, every PDF, every new blog post you publish, and ideally involves testing with actual assistive technology users. The checklist above is a genuinely useful starting point that catches the most common and most damaging issues, but it isn't a guarantee of full compliance, and it isn't a substitute for a proper accessibility audit if your clinic wants that level of assurance.
Frequently asked questions
Is website accessibility actually a legal requirement in Australia?
Australia's Disability Discrimination Act prohibits discrimination on the basis of disability in the provision of services, and an inaccessible website can potentially fall within that if it stops someone accessing your services. There's no single, universally mandated technical standard specifically written into the Act for private business websites, which is exactly why getting general guidance (and legal advice if you want certainty) is worthwhile rather than assuming either "we're fine" or "we're definitely exposed."
Do I need to hire a developer to fix these issues?
Not for most of the basics. Contrast, alt text, form labels and heading structure can usually be adjusted directly in Shopify's theme editor or your website builder's content settings. More technical fixes — like rebuilding a hover-only menu or restructuring keyboard focus — may need a developer, but they're usually small, contained jobs rather than a full rebuild.
How often should we re-check our site?
Any time you add a new page, blog post, image gallery or form, it's worth running it through the same quick checks — accessibility isn't a one-off fix, it's a habit that has to travel with every new bit of content you publish.
Will fixing accessibility issues change how our site looks?
Usually barely at all. Most fixes are things like darkening text a shade, adding text that's only visible to screen readers, or keeping a label on screen instead of letting it vanish — visually, almost nobody will notice the difference except that everything is easier to read.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦