Key takeaways
- Practices that receive HHS federal financial assistance must meet WCAG 2.1 Level AA for web content and apps from May 11, 2027 with 15 or more employees, or May 10, 2028 with fewer.
- The ADA already applies to websites of businesses open to the public, even without a detailed federal web standard for private practices.
- Almost every website has detectable accessibility failures; low contrast text, missing image descriptions and unlabeled form fields top the list.
- Fix the paths patients use most first: booking, forms, phone numbers, the portal link and directions.
Two rules, one goal
Two federal laws reach a medical or dental practice's website. The first is Section 504 of the Rehabilitation Act, which applies to recipients of HHS federal financial assistance. HHS amended its Section 504 rule to set a specific technical standard: web content and mobile apps must meet WCAG 2.1 Level AA, starting May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for those with fewer than 15[1].
The second is the Americans with Disabilities Act. The Department of Justice's guidance says the ADA's requirements apply to the goods and services of businesses open to the public, including those offered on the web[2]. For private businesses it has no regulation setting detailed standards; it points to WCAG and the federal Section 508 standards as helpful guidance and leaves flexibility in how to comply[2]. In practice, WCAG 2.1 Level AA is the benchmark most practices should work toward, because it is the standard the HHS rule names and the one most accessibility audits test against.
May 11, 2027
HHS Section 504 deadline for recipients with 15 or more employees to meet WCAG 2.1 Level AA on web content and mobile apps[1]
Who is affected
Accessibility is not a niche concern for a medical audience. CDC reports that more than one in four US adults have some type of disability, with cognitive, mobility, hearing and vision disabilities among the most common[3]. Many of your patients use screen readers, magnification, captions, voice control or keyboard-only navigation, and many more are older adults whose eyesight and dexterity make small, low-contrast buttons hard to use.
Most of them reach you on a phone. About nine in ten US adults own a smartphone[4], so the mobile version of your site, and any app or portal you link to, is the version that matters most. The HHS rule explicitly covers mobile apps as well as web content[1].
Smaller practices should not read the later HHS deadline as a reason to wait. The ADA applies now, whatever the employee count, and a patient who cannot book or fill in a form online will simply call, or go elsewhere. Every inaccessible form also adds work at the front desk, because staff end up completing it over the phone. Fixing the site is as much about access and workload as about legal risk, so start with the improvements that also make the site easier for everyone, such as clearer forms and larger buttons.
WCAG in plain terms
WCAG, the Web Content Accessibility Guidelines, can look intimidating, but its success criteria sit under four simple ideas. Level AA is the middle of three conformance levels and the one most laws and contracts use. For a practice website, the four ideas translate into everyday questions.
- Perceivable: can people take in the content however they see or hear? Text alternatives for images, captions for video, enough color contrast, text that can be enlarged.
- Operable: can people use the site however they navigate? Everything works with a keyboard, focus is visible, nothing flashes, and people have enough time to complete forms.
- Understandable: is the site predictable and clear? Plain language, consistent menus, labeled fields and error messages that explain how to fix the problem.
- Robust: does it work with assistive technology? Clean, standard code that screen readers and voice control can interpret, including in third-party widgets.
Documents count too. New patient packets, privacy notices, financial policies and pre-visit instructions are often posted as scanned PDFs, which a screen reader cannot read at all. Convert the most used ones to accessible web pages or properly tagged PDFs, and remove outdated documents rather than leaving them online unfixed.
What most sites get wrong
The scale of the problem is large. WebAIM's 2026 analysis of the home pages of the top one million websites found detectable WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page[5]. The same six problems account for most of what automated tools find.
These are fixable. Low contrast text is usually a theme color choice. Missing image descriptions and empty links or buttons are content and template issues that a web developer can correct in hours. Missing form labels matter most for practices, because forms are how patients book, register and ask for help. The DOJ guidance lists many of the same barriers: poor color contrast, color alone used to convey information, missing text alternatives for images, videos without captions, inaccessible online forms and mouse-only navigation[2].
Fix the patient paths first
You do not need to fix everything at once. Start with the pages and tasks that stand between a patient and care, then work outward.
Booking and contact
Make sure a keyboard-only user can request or book an appointment, every form field has a visible label, error messages are written in text and the phone number is a tappable link, not an image.
Forms and intake
Replace scanned PDF forms with accessible web forms or tagged PDFs. Offer a phone alternative for anyone who cannot complete a form online.
Contrast and text size
Raise text contrast to meet WCAG AA, avoid light gray on white, and make sure the page still works when text is enlarged.
Images and icons
Add short, meaningful alternative text to informative images, and labels to icon-only buttons such as menus and search.
Video and audio
Caption videos and provide transcripts for audio, including welcome videos and provider introductions.
Third-party tools
Check the booking widget, portal, payment page and chat tool. Ask each vendor for its accessibility conformance report and a timeline for known issues.
Quick tests anyone on staff can do
- Unplug the mouse and try to book an appointment with only the Tab, Enter and arrow keys. Can you see where you are on the page at every step?
- Zoom the browser to 200 percent on a laptop. Does anything overlap, disappear or need sideways scrolling?
- Turn on your phone's screen reader for two minutes on the home page. Are buttons announced with meaningful names?
- Run a free automated checker on the home page and booking page, and note the errors it finds.
- Read the page with the sound off: do videos have captions?
Automated tools catch only part of the problem, so treat a clean scan as a start rather than proof. For a full review before the HHS deadline, ask a web developer with accessibility experience to test against WCAG 2.1 AA and give you a prioritized list.
Overlays, statements and vendors
Plug-in overlays that promise one-line compliance are tempting, but they do not fix the underlying code, and they can interfere with the assistive technology patients already use. Spend the money on fixing templates and forms instead.
- Publish a short accessibility statement with a phone number and email for anyone who has trouble using the site, and answer those messages quickly.
- Write accessibility into contracts for your website, booking, portal and payment vendors, including WCAG 2.1 AA conformance and a fix timeline.
- Add an accessibility check to your process for new pages, PDFs and videos, so problems are not reintroduced after the cleanup.
- Keep a dated record of reviews and fixes; it shows good faith if anyone raises a complaint.
Example: a two-month cleanup
Example (fictional): An orthopedic practice with 22 employees learns it is covered by the HHS rule and has until May 2027. A developer's review finds low contrast in the site theme, an online intake form with unlabeled fields, an image-only phone number in the header and an uncaptioned welcome video.
In the first month, the developer fixes the theme colors, labels every form field and replaces the phone image with a text link. In the second month, the practice captions its videos, asks its booking vendor for a conformance report and publishes an accessibility statement. The front desk is briefed to help anyone who calls about the site. The practice diaries a full re-test six months before the deadline.
Frequently asked questions
Does the ADA require a specific website standard for private practices?
The Department of Justice has not set a detailed regulation for private businesses' websites, but says the ADA applies to services offered on the web. WCAG 2.1 Level AA is the practical benchmark.
When do we have to comply with the HHS Section 504 web rule?
Recipients of HHS federal financial assistance with 15 or more employees must meet WCAG 2.1 Level AA from May 11, 2027. Those with fewer than 15 employees have until May 10, 2028.
Does the rule cover our patient portal and booking widget?
Content and apps you provide to patients are in scope, including through vendors. Ask each vendor for an accessibility conformance report and build accessibility into contracts.
Will an accessibility overlay make us compliant?
Overlays do not fix the underlying problems and can interfere with assistive technology. Fixing the site's templates, forms and content is the reliable route.
References
Legal Information Institute, Cornell Law School (2026). 45 CFR ยง 84.84 - Requirements for web and mobile accessibility (opens in a new tab) โ
U.S. Department of Justice, Civil Rights Division (ADA.gov) (2022). Guidance on Web Accessibility and the ADA (opens in a new tab) โ
Centers for Disease Control and Prevention (2024). Disability Impacts All of Us (infographic) (opens in a new tab) โ
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ
WebAIM, Utah State University (2026). The WebAIM Million: an accessibility analysis of the top 1,000,000 home pages (opens in a new tab) โ