Dental & Medical Practices: What a Demand Letter Actually Claims About Your Booking Page (and How to Answer It)

You open the mail (or an email with a scary PDF attached) and there it is: a demand letter claiming your practice website is inaccessible under the ADA. Maybe it names your online scheduler. Maybe it mentions your new-patient intake form. Either way, your stomach drops.

Let's cut through the panic. We're not a law firm, and we're not here to scare you into anything. But we fix this stuff for dental and medical offices every week, and the letters almost always make the same claims. Once you know what they're actually alleging, you can stop guessing and start fixing the real problems in your code.

What these letters almost always claim

Demand letters rarely say "your whole website is bad." They point at specific, provable failures a tester (or screen-reader user) hit when trying to book an appointment or fill out intake forms. The usual suspects:

• Form fields with no labels. Your "First Name" box is just an empty box to a screen reader. The letter will say a blind patient couldn't complete your new-patient form.
• An inaccessible date picker. That slick calendar widget on your scheduler often can't be operated with a keyboard alone — a classic cited failure.
• Error messages nobody can hear. Someone misses a required field, the form turns red, but a screen reader announces nothing. The patient is stuck with no idea why.
• Low-contrast text and buttons. Pale gray "Request Appointment" buttons on white fail contrast ratios — easy for a tester to screenshot.
• Images and buttons with no alt or name. A "Book Now" button that's just an image reads as "button, button" — useless.
• A third-party scheduler you don't control. Many letters target the embedded booking tool itself, which means you need a plan even for code you didn't write.

Why practices get targeted more than most

It's not bad luck. Dental and medical sites are transaction-heavy — you've got booking, intake, patient portals, bill pay. Every form is a potential failure point, and every failure is easy for a tester to document. You're a soft, obvious target compared to a brochure site with one "Contact Us" page.

The thing most offices get wrong: the widget trap

In a panic, a lot of practices slap an "accessibility overlay" widget on the site — that little wheelchair icon in the corner that promises instant compliance. Here's the honest truth: those widgets don't fix your actual code, and demand letters increasingly name sites because they use one. The fix has to happen in the real HTML, not in a floating button that paints over the problem.

What actually answers the complaint

When we respond to these for a practice, the goal is to make the specific allegations untrue going forward. That means fixing the code so a screen-reader and keyboard-only user can genuinely book and intake. The core work:

1. Programmatic labels on every field. Each input gets a real, associated <label> so the screen reader announces what it is.
2. Keyboard operability end to end. You should be able to tab through the entire booking flow and submit it without a mouse — date picker included.
3. Announced errors and required fields. When validation fires, the message is tied to the field and read aloud, so the user knows exactly what to fix.
4. Contrast that passes. Buttons and text meet WCAG AA ratios — your "Request Appointment" button shouldn't vanish into the background.
5. Named buttons, links, and images. Every actionable element has an accessible name. No more "button, button."
6. A scheduler plan. If your embedded tool fails, we either configure its accessible version, swap it, or build an accessible fallback path to request a visit.

The target most teams aim for is WCAG 2.1 AA — the standard these letters reference. Hit it on your real pages and you've taken away the ammunition.

Do this today

Open your own booking page. Put the mouse down. Try to book an appointment using only the Tab key and Enter. If you get stuck, trapped, or lost — that's exactly where a tester (and a real patient) gets stuck too. That five-minute test tells you more than any sales pitch.

Getting a demand letter doesn't mean you did something evil — it means your forms have fixable gaps, and fixable is good news. We fix the real code behind your booking and intake so patients can actually use it, and so the common allegations don't stick. Want to know where you stand before anyone else does? Grab a free accessibility scan at rankrebels.ai/accessibility and we'll show you the real problems in plain English.