Millions of patients live with a disability, and most aren't visible: vision impairments, motor limitations, cognitive differences, hearing loss. These patients use your intake forms too. Forms they can't complete exclude them.
There's also a legal side: the ADA applies to healthcare providers, and WCAG is the standard used to judge accessibility.
What "accessible" means
It's a set of design principles, summarized by WCAG's four:
Perceivable. A screen reader user needs every label, instruction, and error read aloud. A low-vision patient needs enough color contrast.
Operable. Many patients with motor disabilities navigate by keyboard only. Anything you can't reach by tabbing blocks them.
Understandable. Plain language helps everyone and is essential for patients with cognitive disabilities or limited literacy.
Robust. The form must work with screen readers, voice control, switch devices, and magnifiers.
The baseline checklist
Every field has a persistent label. Placeholder text that disappears while typing isn't a label. Screen readers depend on real labels.
Keyboard navigation works. Tab through the whole form: everything reachable, in a logical order, with dropdowns, checkboxes, and submit operable.
Color is never the only signal. A red border alone is invisible to colorblind patients. Add an icon or text.
Contrast is high enough. WCAG requires 4.5:1 for normal text. Light gray on white fails.
Errors are specific and next to the field. "Phone number must be 10 digits", not "There was an error", and announced by screen readers.
Focus is visible. Patients tabbing through need to see where they are.
On mobile
- Touch targets of at least 44x44 pixels
- Pinch-to-zoom left on
- Portrait and landscape both working
- VoiceOver and TalkBack able to reach every field and control
Time
Some patients need longer: assistive technology can be slower, and some need to reread or take breaks. Don't put time limits on forms.
How to test
Automated tools (WAVE, axe, Lighthouse) catch missing labels and low contrast, but only part of the problems.
Keyboard: complete the whole form without a mouse.
Screen readers: VoiceOver, NVDA, or TalkBack. Are labels read correctly and errors announced?
Real users: patients who use assistive technology find what tools and manual checks miss.
It helps everyone
Clear labels, logical navigation, good contrast, and specific errors make forms better for every patient. Accessible design is good design that also happens to be required.
Related: patient intake software | intake form templates
Send intake forms patients actually finish.
- Forms, consents, and signatures before the visit
- Your paper forms converted by AI
- BAA included