ADA Website Accessibility for Healthcare Practices (2026)

This article explains how accessibility rules apply to practice websites. It is general information, not legal advice. Talk to a health care attorney about your specific situation.

Does the ADA apply to my practice’s website?

Almost certainly yes. A medical or dental office is a “public accommodation” under Title III of the ADA, and the Department of Justice says the ADA applies to the goods and services a public accommodation offers online. If patients use your site to learn about care, book visits or fill out forms, it needs to work for people with disabilities.

The DOJ’s web accessibility guidance (DOJ, 2022) states that businesses open to the public must make their online services accessible, and that they “have flexibility in how they comply.” There is still no DOJ regulation that sets a technical standard for private businesses under Title III. In practice, courts, plaintiffs and settlement agreements point to the Web Content Accessibility Guidelines (WCAG) as the yardstick.

The audience is large. The CDC (2024) reports that more than 1 in 4 U.S. adults have some type of disability. Many of them are exactly the patients who need your care most often: older adults, people with low vision, and people managing chronic conditions.

What did the DOJ and HHS actually require, and when?

Two federal rules adopted in 2024 named WCAG 2.1 Level AA as the required standard, and both had their deadlines pushed back by one year in 2026. The DOJ rule covers state and local governments. The HHS rule covers organizations that receive HHS funding, which can include private practices.

The DOJ’s Title II rule applies to public entities such as county hospitals and state university clinics. In an interim final rule (DOJ, April 2026), the DOJ moved the first deadline from April 24, 2026 to April 26, 2027, and the deadline for smaller governments to April 26, 2028. Private practices are not covered by Title II, but the rule shows which standard regulators consider reasonable.

The rule that matters most for many private practices is the HHS rule under Section 504 of the Rehabilitation Act, published in May 2024 (HHS, 2024). On May 7, 2026, HHS extended its web and mobile app deadlines by one year (HHS, 2026).

Rule	Who it covers	Standard	Current compliance date
HHS Section 504 (45 CFR part 84, subpart I)	HHS funding recipients with 15 or more employees	WCAG 2.1 AA	May 11, 2027 (was May 11, 2026)
HHS Section 504	HHS funding recipients with fewer than 15 employees	WCAG 2.1 AA	May 10, 2028 (was May 10, 2027)
DOJ ADA Title II	State and local governments with 50,000+ residents	WCAG 2.1 AA	April 26, 2027 (was April 24, 2026)
DOJ ADA Title II	Smaller governments and special districts	WCAG 2.1 AA	April 26, 2028 (was April 26, 2027)
ADA Title III	Private practices open to the public	No set standard; WCAG used in practice	Applies now

The extension does not pause your obligations. HHS said recipients are still required to make the web content and apps they provide “readily accessible to, and usable by, people with disabilities.” Title III exposure also exists today, regardless of any HHS date.

From audit to accessible site

1. 1Inventory key pages
2. 2Scan and test
3. 3Fix templates
4. 4Fix content and PDFs
5. 5Monitor and publish

Doctorsinternet

Does the HHS Section 504 rule cover my practice?

It covers your practice if you receive federal financial assistance from HHS. Billing Medicaid or CHIP, or receiving an HHS grant, are the most common ways a practice becomes a recipient. Once covered, your website, patient portal and any mobile app must meet WCAG 2.1 AA by your compliance date.

Whether other payment arrangements make you a recipient can be a technical legal question. If you are unsure, ask your health care attorney rather than guessing. In our work with 3,200+ practices, we advise teams to plan as if the rule applies, because the same fixes also reduce Title III risk.

Your deadline depends on headcount. Practices with 15 or more employees must comply by May 11, 2027; smaller practices have until May 10, 2028, according to the current regulation text (eCFR, 2026). Count all employees, not just clinical staff.

What content is exempt?

The rule lists five exceptions in 45 CFR 84.85. They are narrower than many owners assume:

• Archived web content that is kept only for reference and not updated.
• Older PDFs and documents posted before your compliance date, unless patients still use them to apply for or access care (your new patient packet does not qualify).
• Third-party content you don’t control, unless it’s posted under a contract or license with you.
• Password-protected documents about one individual, such as a specific patient’s statement.
• Social media posts made before the compliance date.

Booking widgets, payment pages, intake forms and portals you license from vendors are not exempt. You are responsible for choosing tools that meet the standard.

What does WCAG 2.1 AA mean for a practice website?

WCAG 2.1 AA is a set of testable criteria that make a site usable by people who are blind, have low vision, are deaf or hard of hearing, or can’t use a mouse. For a practice site, it mostly means readable contrast, real text alternatives, labeled forms, captioned video and full keyboard access.

The criteria are organized under four principles: content must be perceivable, operable, understandable and robust. The W3C has since published WCAG 2.2 (W3C), which adds criteria such as larger touch targets. Building to 2.2 AA also satisfies 2.1 AA, so we use it as our target on new builds.

Most sites fail on basics, not edge cases. The WebAIM Million report (WebAIM, 2026) found detectable WCAG failures on 95.9% of the top one million home pages, with an average of 56.1 errors per page. The most common problems are the ones we find on practice sites every week:

• Low-contrast text: 83.9% of home pages
• Images missing alternative text: 53.1%
• Form fields without labels: 51%
• Empty links: 46.3%
• Empty buttons: 30.6%
• Missing page language: 13.5%

Every one of these shows up on healthcare sites in the places that matter: pale gray text on hero images, icon-only phone buttons, appointment forms with placeholder text instead of labels, and “click here” links.

By the numbers95.9%of top home pages had detectable WCAG failuresWebAIM, 2026Doctorsinternet

Will an accessibility widget or overlay make my site compliant?

No. An overlay or toolbar widget can’t fix the underlying code, and regulators have said so. In April 2025 the FTC finalized an order requiring accessiBe to pay $1 million (FTC, 2025) over claims that its plug-in could make any website WCAG-compliant.

Overlays can also interfere with the screen readers that blind users already rely on. Some practices have been sued while running a widget. Real compliance comes from fixing the templates, content and forms themselves, then testing with actual assistive technology.

That doesn’t mean every tool is useless. Automated scanners are helpful for finding issues at scale. They just can’t certify compliance, and they catch only part of what a manual review finds.

How do we audit and fix our website?

Start with an automated scan, then do a manual review of your most important pages and every form, then fix templates before individual pages. A practice site usually has a handful of templates, so fixing the header, footer and form components clears a large share of errors at once.

1. Inventory what patients use. List your home page, service pages, location pages, contact and booking pages, forms, portal links, payment pages and any PDFs patients must complete.
2. Run automated checks. Use a free tool such as WAVE or Lighthouse on each template type to catch contrast, alt text and labeling issues.
3. Test by keyboard. Tab through each page without a mouse. You should see where focus is, reach every link and button, and never get trapped in a menu or pop-up.
4. Test with a screen reader. Use VoiceOver (Mac and iPhone) or NVDA (Windows) on your booking flow and forms. Each field should announce its label and errors should be read aloud.
5. Fix components, then content. Repair shared templates first, then write alt text, caption videos and convert required PDFs to accessible web forms.
6. Vet your vendors. Ask booking, payment, chat and portal vendors for a current accessibility conformance report (often called a VPAT) and how they meet WCAG 2.1 AA.
7. Publish an accessibility statement. Give a phone number and email for patients who hit a barrier, and respond quickly.

When we build or rebuild a site through our website design service, accessibility is part of the template work, not an add-on. Ongoing web management matters too, because new blog posts, images and plugins can reintroduce errors.

What about forms and patient intake?

Forms are where accessibility and privacy meet. Intake forms need visible labels, clear error messages and logical tab order, and they must also be HIPAA-compliant. Our HIPAA-compliant forms are built with labeled fields so a patient using a screen reader can complete them without calling the office.

What should our practice do this month?

Put a date on the calendar, assign an owner and fix the highest-traffic pages first. Use this checklist to get from “we should look at that” to a documented plan you can show an attorney or regulator.

Task	Owner	Done when
Confirm whether you receive HHS funding (Medicaid, CHIP, grants) and count employees	Practice owner	You know your Section 504 date: May 11, 2027 or May 10, 2028
Scan home, service, location, contact and booking pages	Web team	Error list saved with screenshots
Keyboard and screen reader test of the booking flow and forms	Web team	A patient can book and submit forms without a mouse
Fix contrast, alt text, labels, empty links and buttons	Web team	Re-scan shows those errors cleared
Caption all videos and replace required PDFs with web forms	Marketing	No required patient document is image-only
Request accessibility reports from booking, chat and payment vendors	Office manager	Each vendor’s WCAG status is on file
Remove any overlay you rely on for “compliance”	Web team	Fixes live in the code itself
Publish an accessibility statement with a contact method	Practice owner	Statement linked in the footer

Accessible sites also tend to perform better in search and AI answers, because clean headings, descriptive links and text alternatives make content easier for machines to read. If you’re working on your website as a conversion tool, fold these fixes into the same project.