Your Waiting Room Has a Ramp. Your Website Probably Doesn't.
Your practice is already accessible.
There’s a ramp at the building, the exam tables adjust, and the front desk reads forms aloud when someone asks. You did that because a meaningful share of your patients need it, and because it’s simply how a medical office should work.
Your website serves the same panel.
If you treat adults, a predictable fraction of the people trying to book with you online have low vision, hand tremor, hearing loss, color vision deficiency, or they’re seventy-four years old and squinting at a phone in bright sunlight.
Many practice websites were built by someone who never once pictured that visitor.
So you end up with a digital front door that a portion of your own panel can’t get through, and you never hear about it, because the patient who gives up on your booking form doesn’t call to tell you. They book with whoever came next in the search results.
What this looks like in practice
The failures are small and specific. Pale gray text on a white background that a younger designer found elegant and a 68-year-old with early cataracts finds unreadable.
A “Book Now” button you can only tell from the background by its color, which fails quietly for roughly one in twelve of your male patients.
Form fields labeled only by placeholder text that vanishes the moment someone starts typing, so a patient who gets interrupted mid-form loses track of which field is which.
Tap targets sized for a mouse pointer and clustered together, so a patient with any tremor keeps hitting the wrong one and eventually gives up.
Your services and hours locked inside an image or a PDF, invisible to the screen reader a blind patient uses and, as it happens, just as invisible to the AI assistants a growing number of patients now ask for recommendations.
None of it is exotic. Each one is an ordinary design decision that nobody ever checked against the full range of people who’d actually use it.
The lawsuit angle, briefly
You may have heard about the ADA demand letters aimed at medical practice websites. That wave is real, and a properly built site does protect you.
But a site fixed only to satisfy a legal audit usually gets the minimum, which in practice means an “accessibility overlay” widget bolted on top of an unchanged design, a hidden compliance statement, and alt text written for a scanner.
The experience stays broken for the actual patients while the practice believes the problem is handled.
Build it right instead.
Contrast, labels, tap targets, readable structure, all designed in from the start, the same way speed and mobile layout should be. Do that and the legal protection comes along free, as a side effect of a site that works.
The part that makes this worth doing regardless
Nearly every change that helps the patient with a disability helps everyone else too.
Higher-contrast text is easier for every patient reading on a phone in a parking lot. Persistent form labels reduce abandoned bookings across the board. Bigger tap targets mean fewer mis-taps for anyone with a thumb.
And your services and hours written out as ordinary page text are exactly what a screen reader and ChatGPT both need in order to recommend you accurately.
Think of it the way you think of universal precautions. You don’t screen each visitor and then apply the standard selectively.
You build the standard in, and every patient gets it.
Five checks will tell you where your own site stands, and they take about ten minutes.
Take your phone outside and hold it at arm’s length in daylight; if you have to squint at your own body text, so do your patients.
Unplug the mouse and tab through the site with the keyboard alone to see whether you can reach the booking button and the phone number. If you can’t, then neither can a patient who can’t use a mouse.
Start typing in your contact form and stop halfway. If you can’t tell anymore what the half-finished fields were asking for, they have no real labels.
Then check that your hours, services, and providers exist as ordinary text on the page. A photo, a slider, or a PDF doesn’t count.
And if a vendor proposes an accessibility overlay widget as the fix, ask what changes underneath it. If the answer is nothing, you’re buying a disclaimer, and your patients are still locked out.
Questions practices ask about this
How do I know if my own site has this problem?
Four quick checks will tell you, and they take about ten minutes. Read your own body text on a phone outside in daylight and see if you squint. Unplug the mouse and tab through to the booking button. Start the contact form, stop halfway, and see if you can still tell what each field wants. Then confirm your hours and services exist as real page text, not a photo or a PDF.
Can my current web person handle this, or do I need to hire a specialist?
Plenty of competent web developers can do this work if you hand them a specific list. Contrast ratios, real form labels, keyboard focus, and tap target sizes are standard front-end work with published numbers behind them. Where people get stuck is the auditing, so get one audit against WCAG 2.1 AA from someone who does it regularly, then have your usual developer work through the findings as a punch list.
I already have an accessibility overlay widget on the site. Am I covered?
Probably less than the vendor implied. No government body certifies a website as compliant, so the badge is the vendor's own claim, and practices running overlays have still received demand letters. An overlay also leaves the page's underlying markup untouched, which is what a screen reader reads. Ask your attorney what your exposure looks like, and ask the vendor exactly what changes in the markup.
Is this worth doing for a single-location practice that gets patients mostly by referral?
Yes, since the same fixes carry into every other way patients find you. A referred patient still checks the site before calling, so a booking form that breaks loses you someone who was already headed your way. Small panels feel that loss harder than large ones. Hours, services, and providers written as ordinary page text also feed your Google listing.
Photograph: Matt Webster / Pexels