An "ADA compliant website" has no official certificate. For a medical practice it means a site people with disabilities can use: to read about services, find providers, call, and request an appointment. Most accessibility pages are written for every kind of business, or sell an overlay widget. This one is for practices. It explains WCAG 2.1 AA plainly, sorts out which federal rules apply, and focuses on what practice sites usually get wrong.
In short: The ADA covers medical offices' websites under Justice Department guidance, without a fixed technical standard. Practices that receive HHS funding, including Medicare Part B payments, must meet WCAG 2.1 Level AA under Section 504, from May 11, 2027 (15 or more employees) or May 10, 2028 (fewer). Fix photos, forms, widgets, contrast, captions and PDFs first.
Demand is high: "ada compliant website" and "ada website compliance" draw 5,400 searches a month together, "wcag 2.1" 4,400, "website accessibility" and "website accessibility checker" 2,900 each, and "ada website lawsuit" 170 (Google Ads Keyword Planner data via DataForSEO, US, 12-month average to Sep 2026).
This page is informational. Medfy makes no claim that any website, including the ones it builds, conforms to WCAG.
What "ADA compliant website" means for a medical practice
The Americans with Disabilities Act (ADA) bars disability discrimination by businesses open to the public. The Justice Department's web guidance (opens in a new tab) says the ADA's requirements apply to "all the goods, services, privileges, or activities offered by public accommodations", including those offered on the web, and lists hospitals and medical offices as businesses open to the public.
The same guidance says the department "does not have a regulation setting out detailed standards" for these businesses. They have flexibility in how they comply, with WCAG and the federal Section 508 standards described as helpful guidance. In practice, WCAG 2.1 AA is the yardstick most people use.
WCAG 2.1 AA in plain English
WCAG, the Web Content Accessibility Guidelines, is published by the W3C. Version 2.1 (opens in a new tab) was published on June 5, 2018. Its testable success criteria come in three levels: A, AA and AAA. "WCAG 2.1 AA" means meeting every Level A and Level AA criterion.
The criteria sit under four principles:
- Perceivable: people can see or hear the content another way, such as alt text for images and captions for video.
- Operable: everything works with a keyboard, and nothing traps or rushes the user.
- Understandable: forms have clear labels and helpful error messages; pages behave predictably.
- Robust: the code works with screen readers and other assistive technology.
WCAG 2.2, published October 5, 2023, adds criteria. The W3C says content that conforms to 2.2 also conforms to 2.1, so building to 2.2 covers both.
Which rules apply: ADA, Section 504 and Section 1557
Checked against the regulation text and the Federal Register on October 22, 2026.
| Rule | Who it covers | Web standard | Dates |
|---|---|---|---|
| ADA Title III | Businesses open to the public, including medical offices | None set by regulation; WCAG is guidance | No fixed date |
| Section 504 (Rehabilitation Act), HHS rule | Recipients of HHS federal financial assistance | WCAG 2.1 Level AA, under 45 CFR 84.84 (opens in a new tab) | May 11, 2027 (15 or more employees); May 10, 2028 (fewer than 15) |
| Section 1557 (ACA), HHS rule | Health programs receiving federal financial assistance | Accessible ICT; websites must meet Section 504, under 45 CFR 92.204 (opens in a new tab) | Follows Section 504 for web content |
Three points practices often miss:
- Medicare Part B counts. In its 2024 Section 1557 rule (opens in a new tab), HHS finalized its interpretation that Medicare Part B funding is federal financial assistance for Section 504 and Section 1557, among other civil rights laws. Many physician practices are therefore recipients.
- The dates moved. HHS's 2024 Section 504 rule originally set May 2026 and May 2027. An interim final rule (opens in a new tab) effective May 7, 2026 pushed them back one year. The WCAG 2.1 AA standard itself didn't change.
- Old PDFs aren't automatically exempt. The rule's exceptions (opens in a new tab) cover documents posted before the compliance date, but not documents currently used to apply for, access or take part in your services. An intake packet patients download today is in scope.
See Section 1557 explained for that rule's notices and language-access duties.
This is general information, not legal advice. Confirm how it applies to your practice with a qualified advisor.
The accessibility problems most practice sites have
The Justice Department's guidance names the common barriers (opens in a new tab): poor color contrast, missing alt text, videos without captions, inaccessible online forms, and navigation that only works with a mouse. On practice sites they show up as:
- Provider and office photos without alt text, so a screen reader announces "image" or a file name.
- Call and request buttons with low contrast, such as white text on pale blue.
- Text inside images, like hours or insurance logos with no text version.
- Forms with placeholder text instead of labels, and errors shown only in red.
- Chat and booking widgets that keyboard users can't reach or close.
- Videos without captions, including provider introductions.
- Scanned PDFs, especially intake forms, that screen readers can't read.
Automated checkers: what they catch and what they miss
Automated checkers, including the Lighthouse accessibility score, find problems that can be detected in code: missing alt attributes, low contrast, unlabeled fields. They're a good first pass.
They can't judge everything. The W3C says "tools cannot check all accessibility aspects automatically. Human judgement is required" (opens in a new tab), that tools can produce false or misleading results, and that they "can not determine accessibility, they can only assist". A checker can see that a photo has alt text; it can't tell whether "IMG_4022" describes Dr. Patel.
Overlay widgets that promise one-line fixes deserve extra caution. In April 2025 the FTC finalized an order (opens in a new tab) requiring accessiBe to pay $1 million over claims that its widget could make any website WCAG-compliant, claims the FTC alleged were false, misleading or unsubstantiated.
Forms and booking widgets: accessibility checkpoints
Forms are where patients act, so check them by hand:
- Every field has a visible label, not just placeholder text.
- Errors are described in words ("Enter a phone number"), not only by color.
- The whole form works with the Tab key, including date pickers and dropdowns.
- Required fields are marked in text, not only with an asterisk color.
- The booking or chat widget opens, works and closes with a keyboard, and focus returns to the page.
- Time limits can be extended, if the form or widget has any.
Accessibility and privacy meet here. A form that's accessible still has to send submissions to a vendor that signs a Business Associate Agreement. Our guide to HIPAA compliant forms covers that side.
A practical remediation plan
- Run an automated check on your home page, two service pages and your request form. Fix what it flags.
- Fix the high-traffic items by hand: alt text on provider and office photos, contrast on call and request buttons, labels and error messages on forms.
- Test with a keyboard only. Tab through the site, open the booking or chat widget, submit the form.
- Caption every video and add a text summary.
- Replace scanned PDFs in current use, intake forms first, with accessible documents or a covered online form.
- Add an accessibility contact so patients can ask for help or another format. Our list of required website notices covers related notices.
- Ask vendors for accessibility documentation on any widget you embed, and verify the claims yourself.
- Recheck after every redesign and at least yearly, before the Section 504 date that applies to you.
Our free marketing audit reviews your website's basics alongside SEO and your Google listing; treat it as a starting point, not an accessibility assessment. For speed and the rest of the technical checks, see website speed optimization.
Frequently asked questions
Do medical practice websites have to be ADA compliant?
The Justice Department's web guidance says the ADA covers the online offerings of businesses open to the public and names medical offices among them, though it sets no detailed technical standard. Practices that receive HHS financial assistance, which HHS says includes Medicare Part B, also face a Section 504 rule requiring WCAG 2.1 AA from May 11, 2027 or May 10, 2028, depending on size.
What is WCAG 2.1 AA?
WCAG is the Web Content Accessibility Guidelines, published by the W3C. Version 2.1 came out in June 2018 and sets testable success criteria at three levels: A, AA and AAA. Meeting AA means meeting every Level A and Level AA criterion, covering things like text alternatives for images, color contrast, keyboard access, labeled form fields and captions. It is the level HHS's Section 504 rule adopts.
Can a small practice be sued over website accessibility?
It can happen. The Justice Department says the ADA applies to the websites of businesses open to the public, including medical offices, and it lists web accessibility enforcement actions and settlements, including one over a pharmacy's vaccine registration portal. Practices funded by HHS also face Section 504's WCAG 2.1 AA deadline. The practical protection is to find and fix barriers, and document what you did.
Are accessibility overlay widgets enough?
Treat them with caution. The W3C says evaluation tools cannot determine accessibility on their own and that human judgment is required. In April 2025 the FTC finalized an order requiring the overlay vendor accessiBe to pay $1 million over claims that its widget could make any website WCAG-compliant, which the FTC alleged were false or unsubstantiated. Fixing the site itself is the dependable route.