Dental & Medical Practices: The 7 Spots on Your Patient Portal Where Accessibility Quietly Breaks
You didn't go to dental or medical school to stress about web code. But here's the uncomfortable truth: the online booking and intake tools that make your front desk's life easier are also the exact spots where accessibility breaks — and where a demand letter starts.
ADA web complaints against practices almost never target your homepage. They target the flow a patient actually has to complete: request an appointment, verify insurance, fill out intake, sign consent. If a patient using a screen reader or keyboard can't finish that, they can't become your patient — and someone can build a case out of it.
To be clear, we're not a law firm and this isn't legal advice. We're the people who fix the real code (not a bolt-on widget that pretends to). Here are the seven spots we find broken most often on practice sites.
1. The 'Request Appointment' button that isn't really a button
A lot of booking buttons are just styled text or a clickable image. A screen reader announces nothing useful, and a keyboard user can't reach it with the Tab key. If a patient can't focus it and press Enter, your whole intake funnel is dead on arrival for them.
The fix
Use a real button or link element with clear, spoken text like "Request an appointment." Confirm it's reachable by keyboard and shows a visible focus outline.
2. Insurance and date-of-birth fields with no labels
Intake forms are label graveyards. Placeholder text like "MM/DD/YYYY" disappears the moment someone types, and screen readers often skip placeholders entirely. A blind patient hears "edit text, blank" and has no idea what you're asking for.
The fix
Every field gets a real, programmatically connected label. Insurance carrier, member ID, date of birth, reason for visit — all of them, spoken out loud.
3. Error messages that only exist in red
When a patient forgets a field, does your form turn the box red and stop there? Color-only errors are invisible to colorblind and low-vision patients, and screen readers won't announce them.
The fix
Pair color with text: "Please enter your date of birth." Announce errors so assistive tech reads them the moment they appear, and move focus to the first problem field.
4. The scheduling calendar that traps a keyboard
Third-party scheduling widgets (the ones that pop open a month grid) are notorious. A keyboard user tabs in, picks a date… and can't tab back out. That's a keyboard trap, and it's a classic demand-letter finding.
The fix
Test every embedded scheduler with the Tab and Escape keys only — no mouse. If you can't get in, navigate, and get out cleanly, it needs a fix or a replacement.
5. The consent PDF nobody can read
HIPAA notices and consent forms uploaded as scanned images are just pictures of text. A screen reader gets nothing. If a patient can't read what they're consenting to, that's a real accessibility gap on a legally sensitive document.
The fix
Provide real, tagged, selectable-text PDFs — or better, an accessible HTML version of the same content on your site.
6. Tiny gray text on your hours and phone number
Low-contrast text (light gray on white) is the single most common issue we find, and it hits the exact info patients need: hours, phone, address, emergency instructions.
The fix
Bump contrast to meet WCAG's minimum ratio. Your "Call now" and after-hours instructions should be readable by a 70-year-old patient on a phone in the sun.
7. The 'thank you' confirmation nobody hears
A patient submits a booking, the page updates with "We got your request!" — but if that message loads without announcing itself, a screen reader user never knows it worked. They resubmit, or give up and call your competitor.
The fix
Make confirmation messages announce to assistive tech, so every patient knows the appointment request actually went through.
Why this matters beyond the letter
Yes, fixing these lowers your demand-letter risk. But it also means more patients actually finish booking — including the older, disabled, and vision-impaired patients your practice already serves in the chair. Accessible code isn't charity. It's how you get found and get the calls (and bookings) you're currently losing.
Want to know which of these seven are hiding in your booking flow right now? Grab a free accessibility scan at rankrebels.ai/accessibility — we'll show you what's broken in plain English and what it takes to fix the real code, not slap a widget over it.
Want this done for you?
Rank Rebels builds fast websites and gets local businesses found on Google and AI search.
Get a free audit →