ADA Website Compliance

ADA Website Compliance for Healthcare

Real, hand-built accessibility remediation that makes your site WCAG 2.1 AA compliant — and keeps the lawyers away. No overlays, no shortcuts.

  • WCAG 2.1 AA conformance
  • Manual remediation, not overlays
  • Section 1557 + ADA aligned
  • Patient-portal and form expertise

ADA compliance for healthcare, done the durable way

Healthcare websites carry obligations most businesses don’t. A medical practice site isn’t just marketing — it’s where patients book appointments, refill prescriptions, message clinicians, read lab results, and pay bills. When any of that is unusable for someone who relies on a screen reader or keyboard navigation, you’ve created both an access barrier and legal exposure. Curbcut makes your healthcare website and patient portal genuinely usable by remediating the code itself to WCAG 2.1 AA — by hand, never with an overlay.

Why healthcare faces heightened obligations

Most US businesses worry about one law. Healthcare providers typically face two overlapping ones.

  • ADA Title III treats hospitals, clinics, dental offices, and most provider websites as places of public accommodation. The DOJ has consistently taken the position that the ADA covers the goods and services offered through a business’s website.
  • Section 1557 of the Affordable Care Act is the bigger differentiator. It prohibits disability discrimination in any health program or activity that receives federal financial assistance — which includes nearly any practice billing Medicare or Medicaid. A 2024 HHS final rule under Section 1557 directly addresses web content and mobile apps and ties accessibility to WCAG 2.1 AA.

Because these obligations overlap, the practical path is simple: conform to WCAG 2.1 AA and you satisfy the common denominator. (This page is general information, not legal advice — talk to a healthcare attorney about your exact situation.)

FrameworkApplies toWeb standard referenced
ADA Title IIIPublic accommodations (most providers)WCAG 2.1 AA (DOJ guidance)
Section 1557 (ACA)Programs receiving federal health fundsWCAG 2.1 AA (2024 HHS rule)
Section 508Federal agencies and many federal contractorsWCAG 2.0/2.1 AA

If you serve any government or federally funded program, Section 508 may also apply. For a plain-language breakdown of how these relate, see ADA vs Section 508 vs WCAG.

The patient portal is your highest-risk surface

Brochure pages are easy to make accessible. Portals are where healthcare sites fail. They lean on dynamic, JavaScript-heavy components — appointment pickers, secure messaging, results dashboards, payment forms — and those are exactly the elements that break for assistive technology when ARIA is misused or keyboard focus is lost.

Common portal failures we find:

  • Login and scheduling forms with unlabeled fields, so screen readers announce “edit text” with no context
  • Appointment calendars that can’t be operated without a mouse
  • Error messages that appear visually but are never announced
  • Modal dialogs that trap or lose keyboard focus
  • Downloadable intake forms and result summaries delivered as inaccessible PDFs

Each maps to a measurable POUR principle — Perceivable, Operable, Understandable, Robust — and each is fixable. For the underlying techniques, see our guides on accessible forms, ARIA labels and roles, and accessible PDFs.

What WCAG 2.1 AA actually requires here

Conformance is organized by levels — A, AA, and AAA. The legal and practical target is Level AA. In a healthcare context that means, among other things:

  • Alt text on every meaningful image, including provider photos, facility maps, and informational graphics
  • Color contrast that meets the 4.5:1 ratio so appointment buttons and lab values are readable for low-vision patients
  • Full keyboard navigation through booking, messaging, and payment flows
  • Visible focus indicators and logical reading order across headings and landmarks
  • Forms with programmatic labels, instructions, and announced errors

A proper audit tests these against real assistive technology — NVDA, JAWS, and VoiceOver — not just an automated scanner. Automated tools catch roughly a third of issues; the rest require human testing. That distinction is the whole game in healthcare, where a “passing” scan can still leave a portal unusable. Learn more about WCAG 2.1 AA and conformance levels.

Why overlays fail healthcare specifically

Accessibility overlay widgets — the JavaScript scripts that promise instant compliance — are a poor fit anywhere, but they’re especially dangerous for providers. They don’t repair the underlying HTML, they frequently conflict with the screen readers patients already use, and they leave your most sensitive flows untouched. Courts have ruled against businesses that leaned on them, and a wave of lawsuits and demand letters now names overlay users specifically. For healthcare, a half-working widget on a results page isn’t just a compliance gap — it’s a care barrier.

Curbcut does the opposite: durable manual remediation in your real codebase. If you’re weighing the two approaches, read overlay vs manual remediation.

Our process for healthcare sites

  1. Audit. A manual + automated accessibility audit of your public site and portal flows against WCAG 2.1 AA, tested with screen readers and keyboard-only navigation.
  2. Remediate. Hands-on fixes to your HTML, ARIA, forms, and PDFs — prioritized by patient impact and legal risk.
  3. Document. A VPAT / Accessibility Conformance Report and an accessibility statement so you can show evidence of conformance.
  4. Monitor. Optional ongoing monitoring so new content and portal updates don’t reintroduce barriers.

Thousands of ADA web accessibility lawsuits and far more demand letters are filed each year, and healthcare is a frequent target because of the volume of transactional, sensitive workflows on provider sites. If you’ve already been contacted, don’t install a widget and hope — start a real audit so you can demonstrate good-faith remediation, and read how to avoid an ADA lawsuit. For authoritative background, see the ADA.gov guidance, the W3C Web Accessibility Initiative, and Section508.gov. For testing methodology, WebAIM is a trusted reference.

Get started

The fastest way to understand your exposure is to see where your site stands today. Start with a free accessibility scan, or contact us to scope a healthcare-specific audit and remediation plan. We’ll show you exactly which barriers exist on your site and portal — and fix them for real.

Frequently asked questions

Does my medical practice website have to be ADA compliant?

In practice, yes. Healthcare providers are covered by ADA Title III as places of public accommodation, and most also fall under Section 1557 of the Affordable Care Act if they receive federal funds like Medicare or Medicaid. Both are read to require websites and patient portals that work for people with disabilities. The recognized standard is WCAG 2.1 AA. This is general information, not legal advice — confirm your specific obligations with an attorney.

What is Section 1557 and how is it different from the ADA?

Section 1557 is the nondiscrimination provision of the ACA. It prohibits disability discrimination in health programs that get federal financial assistance, and a 2024 HHS rule explicitly addresses accessible web content and mobile apps tied to WCAG 2.1 AA. The ADA applies more broadly to public accommodations. Many healthcare organizations are covered by both, so meeting WCAG 2.1 AA addresses the overlapping requirements.

Are patient portals covered by accessibility rules?

Yes — and they are often the highest-risk surface. Portals handle appointments, lab results, secure messaging, and bill pay, frequently through forms and dynamic widgets that break for screen reader and keyboard users. We test and remediate portal flows the same way we treat the main site.

Will an accessibility overlay make my healthcare site compliant?

No. Overlays do not fix the underlying code, they routinely break with assistive technology, and courts have ruled against businesses that relied on them. Healthcare sites carry sensitive workflows where a half-working widget creates real patient harm. We do manual remediation instead. See why overlays don't ensure compliance.

We got an ADA demand letter about our clinic website. What now?

Act quickly but don't panic-install a widget. Preserve the letter, avoid public statements, and get a real accessibility audit started so you can demonstrate good-faith remediation. Read our demand-letter response guide, then consult an attorney.

How long does it take to make a healthcare website ADA compliant?

Most single-location practice sites take a few weeks: a manual audit against WCAG 2.1 AA, then a remediation sprint scoped to the findings. Sites with patient portals, scheduling tools, or PDF forms take longer because those flows need careful retesting. You get a timeline after the audit.

Get a clear path to compliance

Start with a free accessibility scan. We'll show you exactly where your site fails WCAG 2.1 AA — and what real remediation costs.