Accessible forms and chat: booking that works for every patient

Updated November 14, 2026 · 5 min read
Short answer

Your booking forms, intake and chat widget need to work for patients who use a keyboard, a screen reader, voice control or a magnified screen. Private medical offices are covered by ADA Title III, and practices that receive HHS federal financial assistance face a WCAG 2.1 Level AA standard on dates starting May 11, 2027. A ten minute keyboard test finds many of the worst problems.

Which rules reach your forms and chat

Two sets of federal rules matter for most practices. This is general information, not legal advice, so confirm with counsel which apply to you.

  • The ADA. The Justice Department's ADA site states that private hospitals and medical offices are covered by Title III as places of public accommodation, and its web guidance says those obligations extend to services offered online. The Department has not set one technical standard for private businesses, but it points to WCAG as a helpful reference, and it names unlabeled form fields and sites that cannot be used with a keyboard among common barriers.
  • Section 504, for recipients of HHS funding. HHS's 2024 rule adopted WCAG 2.1 Level AA as the technical standard for the web content and mobile apps of recipients of its federal financial assistance, including content provided through contracts or licensing arrangements. In May 2026 HHS moved the compliance dates back a year: May 11, 2027 for recipients with fifteen or more employees, and May 10, 2028 for smaller ones. HHS's Section 1557 rule separately requires recipients' websites to meet Section 504.

The practical message is the same either way: build and buy forms and chat that meet WCAG 2.1 AA now. The legal risk is covered in ADA website lawsuits against medical practices.

The ten minute keyboard test

Put your mouse in a drawer and open your booking page.

  1. Press Tab repeatedly. Can you always see which element has focus?
  2. Reach the booking button, choose a visit type, pick a date and time, fill every field and submit, using only Tab, Shift Tab, Enter, Space and the arrow keys.
  3. Make a mistake on purpose. Does the error message say what is wrong, and can you get to the field to fix it?
  4. Open the chat with the keyboard, type a message, send it and close the chat with Escape. Does focus return to where you were?
  5. On your phone, zoom the page to double size. Can you still complete the form without scrolling sideways?
  6. Turn on the screen reader built into your phone and move through a few fields. Does each one announce its label?

Any step you cannot finish is a step some patients cannot finish either. Write each failure down with the page and field, and send the list to whoever built the page or tool.

See your Surge Score in about a minute

Does ChatGPT recommend your practice?

The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.

Form problems that block patients

These are the barriers that turn up most often on practice booking and intake forms, with the WCAG idea behind each fix.

  • Fields without labels, or labels that vanish once the patient starts typing. The W3C forms tutorial starts here: every control needs a label assistive technology can read.
  • Errors shown only in red, or not announced at all. Say in words what went wrong and how to fix it.
  • Required fields marked only by color or a lone asterisk with no explanation.
  • Date pickers and dropdowns that only work with a mouse or a finger.
  • Timeouts with no warning. WCAG 2.2.1 gives several options, such as letting users turn off or extend the limit, with at least 20 seconds to extend when that is the approach.
  • Retyping information already given, which WCAG 2.2 addresses in its Redundant Entry criterion.
  • Silent confirmations. A message such as "Your form was successfully submitted" is what WCAG calls a status message, and it should be announced without moving focus.
  • PDF forms that cannot be filled in on screen.

For the bigger picture on your site as a whole, see not accessible to patients with disabilities.

Chat widgets have their own failure modes

Chat is often the least accessible thing on a practice website, because it sits on top of the page and was built separately.

  • The launcher button has no accessible name, so a screen reader announces only "button"
  • The chat window opens, but keyboard focus stays on the page behind it
  • New replies appear without being announced, so a screen reader user does not know the assistant answered
  • The session ends after a short idle time while someone is still typing slowly or with a switch device
  • On a phone, the window covers the page and its close button sits off screen
  • The chat opens itself, interrupting a patient who was reading

Chat can also improve access. Patients who are deaf or hard of hearing, or who find phone calls difficult, may prefer a text channel, which is a good reason to get it right. For what chat should say, see AI chat on a medical website.

Third party tools are still your responsibility

Most practices do not build their own scheduler, intake or chat. The HHS rule covers content provided through contractual and licensing arrangements, and patients do not care whose code failed. Treat accessibility as a purchasing requirement.

  • Ask for the vendor's accessibility conformance report against WCAG 2.1 AA, or WCAG 2.2, which W3C says is backward compatible: content that conforms to 2.2 also conforms to 2.1
  • Ask them to demo a full booking using only a keyboard, and then with a screen reader
  • Put a commitment to fix reported accessibility defects, with a timeline, in the contract
  • Re-run your keyboard test after every vendor update

A toolbar or overlay added on top of a page does not change how a vendor's form is built underneath. Judge the form itself.

Always offer more than one way in

No single channel works for everyone. Patients who cannot use a form can call, and patients who cannot call can text or chat. Put the alternatives next to each other, so a patient who is stuck has somewhere to go.

Use the booking flow to ask about accommodations for the visit itself. A simple optional question, such as whether the patient needs a sign language interpreter, wheelchair access or other help, gives your team time to arrange it. The Justice Department's guidance on effective communication says covered entities are responsible for providing interpreters and other aids and cannot require a person to bring their own interpreter.

Carry that answer into the record so the front desk sees it before the patient arrives. Intake is the natural place to confirm it; see online intake forms that patients finish.

Checklist

  • A full booking can be completed with a keyboard alone
  • Every form field has a visible label that a screen reader announces
  • Errors and confirmations are stated in words and announced
  • The chat opens, works and closes from the keyboard, and announces new replies
  • Forms still work at double zoom on a phone without sideways scrolling
  • Vendors provide a WCAG conformance report and fix defects on a timeline
  • Booking asks whether the patient needs accommodations for the visit

Frequently asked

Does the ADA require a specific accessibility standard for practice websites?

For private businesses, the Justice Department has not mandated one technical standard, but it points to WCAG as a helpful reference. Practices that receive HHS federal financial assistance face WCAG 2.1 Level AA under HHS's Section 504 rule on the dates it sets. Ask counsel which applies to you.

When do the HHS web accessibility requirements take effect?

Under the May 2026 extension, recipients of HHS federal financial assistance with fifteen or more employees must meet WCAG 2.1 Level AA starting May 11, 2027, and those with fewer than fifteen starting May 10, 2028.

Is our booking vendor responsible for accessibility, or are we?

Treat it as yours. The HHS rule reaches content you provide through contracts and licensing, and patients experience it as your website. Make accessibility a purchasing and contract requirement, and test the vendor's tool yourself.

Will an accessibility overlay fix our forms?

Do not rely on one. A toolbar added on top of the page does not change how a form or chat widget is coded underneath. Test the actual form with a keyboard and a screen reader, and fix what fails at the source.

Sources

  1. Access to Medical Care for Individuals with Mobility Disabilities, U.S. Department of Justice, ADA.gov
  2. Guidance on Web Accessibility and the ADA, U.S. Department of Justice, ADA.gov
  3. ADA Requirements: Effective Communication, U.S. Department of Justice, ADA.gov
  4. Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Content and Mobile Applications of Recipients of Departmental Financial Assistance, Federal Register, U.S. Department of Health and Human Services
  5. 45 CFR 92.204, Accessibility of information and communication technology, Electronic Code of Federal Regulations
  6. Forms Tutorial, W3C Web Accessibility Initiative
  7. WCAG 2 Overview, W3C Web Accessibility Initiative
  8. Understanding Success Criterion 2.2.1: Timing Adjustable, W3C Web Accessibility Initiative
  9. Understanding Success Criterion 3.3.7: Redundant Entry, W3C Web Accessibility Initiative
  10. Understanding Success Criterion 4.1.3: Status Messages, W3C Web Accessibility Initiative
Prefer to talk it through?

Book a strategy call with the team.

Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.

AI patient discovery audit

Is AI recommending you, or your competitor?

See who ChatGPT, Gemini and Perplexity recommend to patients in your area.

Free. Built by physicians.