Loading...
Healthcare's digital front door — portals, scheduling, telehealth, and medical documents — now sits under the strictest accessibility rules in US law, and the first hard WCAG deadline has already passed. Here is what applies to you and how to close the gap.
HHS Section 504 web rule deadline for most covered entities — already in effect, and it was not extended
US adults has a disability, and people with disabilities use healthcare services more than any other group
the technical standard the HHS Section 504 rule adopts for websites, patient portals, and mobile apps
healthcare's share of private accessibility litigation is climbing as regulators set explicit standards
No industry's users need accessibility more. People with disabilities are healthcare's core constituency, not an edge case: roughly one in four US adults lives with a disability, disability prevalence rises steeply with age, and the patients who interact with health systems most frequently — older adults and people managing chronic conditions — are exactly those most likely to rely on screen readers, magnification, captions, voice control, or keyboard navigation. A health system whose portal fails these users is failing its highest-utilization patients.
The stakes are also categorically higher than in other sectors. An inaccessible checkout loses a sale; an inaccessible patient portal delays a lab result, blocks a medication refill, or prevents a deaf patient from conducting a telehealth visit. Research consistently shows people with disabilities experience worse health outcomes and more barriers to care — and since the pandemic pushed intake, scheduling, and visits online, digital barriers have become clinical barriers. Accessibility failures here translate directly into delayed care, privacy loss (needing a sighted helper to read your own diagnosis), and health inequity.
The business case follows: portals and telehealth only reduce cost if patients can actually self-serve. Every patient who cannot book online books by phone; every unreadable statement becomes a billing call. Accessible digital care pathways raise portal adoption, telehealth completion rates, and patient satisfaction scores — while keeping you inside the legal lines described below.
Healthcare organizations typically sit under several regimes at once. For background on the ADA generally, see our ADA compliance guide; public health systems should also review Section 508 if they touch federal programs.
In May 2024, HHS finalized a rule under Section 504 of the Rehabilitation Act requiring recipients of HHS funding — hospitals that bill Medicare or Medicaid, clinics, state health agencies, health plans, and grantees — to make websites, patient portals, kiosks, and mobile apps conform to WCAG 2.1 Level AA. The compliance date for most covered entities was May 11, 2026, with smaller entities on phased timelines. Unlike the DOJ's Title II web rule, this deadline was not extended. If your organization takes HHS money and your digital front door is not WCAG 2.1 AA conformant today, you are out of compliance. See our Section 504 deadline guide for who is covered and what to do if you missed it.
The 2024 Section 1557 final rule prohibits disability discrimination in health programs and activities that receive federal financial assistance, and it explicitly extends to services delivered through websites, mobile apps, and telehealth. Covered entities must ensure telehealth services are accessible to patients with disabilities and provide effective communication — captions, interpreters, accessible documents — as part of care delivery. HHS's Office for Civil Rights enforces 1557 through complaint investigations, resolution agreements, and, ultimately, the threat of losing federal funding.
Private hospitals, physician practices, dental offices, pharmacies, and health insurers are places of public accommodation under ADA Title III; public hospitals and county health systems fall under Title II. Courts have applied both to digital services, and DOJ has repeatedly taken the position that the ADA covers web content. Private plaintiffs have sued health systems over inaccessible appointment scheduling, portals, and vaccine-booking sites — pandemic-era vaccine registration lawsuits were an early warning of how quickly digital health barriers become litigation. A public hospital covered by both Title II and Section 504 must meet the earlier, stricter Section 504 deadline.
Independent of any WCAG rulemaking, the ADA and Section 504 have always required effective communication with patients — auxiliary aids, accessible formats, and interpreters. OCR has resolved cases against providers whose inaccessible billing statements, discharge instructions, and consent forms denied blind and deaf patients equal access to their own health information. Digital accessibility is the modern form of an obligation healthcare has carried since 1990: a patient portal a screen reader cannot operate is legally equivalent to a printed form a blind patient cannot read.
Deep dive: read our guide to the Section 504 web accessibility deadline — the rule that was not extended.
Healthcare audits surface the same categories again and again. Each links to the relevant WCAG success criterion.
Healthcare runs on forms — new-patient registration, symptom questionnaires, insurance verification, consent, appointment booking. Fields without programmatic labels, required-field indicators conveyed only by color, error messages that never reach a screen reader, and date pickers that trap keyboard users all block patients at the first step of care. Multi-step intake flows must preserve entered data and announce progress and validation errors accessibly.
After-visit summaries, lab results, billing statements, consent forms, and plan documents are overwhelmingly delivered as PDFs — and most are untagged scans or exports with no reading order, no heading structure, and no alt text. An untagged PDF is effectively blank to a screen reader, which means a blind patient cannot privately read their own diagnosis or bill. Run key documents through our free PDF accessibility checker, fix templates at the source system, and prefer accessible HTML over PDF wherever possible.
Section 1557 explicitly requires accessible telehealth. That means the join flow, waiting room, and in-call controls must be keyboard operable and screen-reader compatible; live visits need real-time captioning or interpreter support for deaf and hard-of-hearing patients; and prerecorded patient-education video needs accurate captions. Because most telehealth runs on third-party platforms, providers must vet vendors — the legal obligation to the patient stays with the covered entity.
Healthcare skews older: the heaviest users of patient portals are also the most likely to have reduced vision. Light gray lab values, thin fonts over hero imagery, and dense unstructured result tables make portals unusable well before legal blindness. Clear heading hierarchies, descriptive section labels, and 4.5:1 contrast minimums are low-cost fixes with outsized impact on the actual patient population.
Health systems serve multilingual populations and publish translated content, but pages frequently omit the lang attribute — so screen readers pronounce Spanish text with English phonetics, rendering translations useless. Pair correct language markup with plain-language writing for critical instructions; comprehension barriers are accessibility barriers when the reader has a cognitive disability, low literacy, or is in crisis.
With the Section 504 deadline already passed for most covered entities, the sequence below is built for catching up fast and documenting progress.
Determine which rules bind you: HHS funding triggers Section 504 (deadline passed) and usually Section 1557; public ownership adds ADA Title II; private status adds Title III. Inventory every patient-facing digital property — main site, portal, mobile app, telehealth platform, kiosks, and document delivery systems — because the Section 504 rule covers all of them.
Audit finding a provider, booking, intake, the telehealth visit, results retrieval, and bill payment as one continuous journey, combining automated scans with manual screen reader and keyboard testing. Prioritize the portal and scheduling first — they are the highest-traffic and highest-obligation surfaces.
Remediate intake and scheduling forms at the template level so every deployment inherits the fix. Retag high-volume PDF templates (statements, summaries, consents) in the generating system rather than one document at a time, and migrate what you can to accessible HTML. Establish a captioning pipeline for all patient-education video.
Most patient-facing healthcare software is vendor-built (portals, telehealth, scheduling). Require WCAG 2.1 AA conformance and a current ACR/VPAT in contracts and renewals, test vendor releases yourself, and document remediation commitments — OCR expects covered entities to manage their vendors, not hide behind them.
Adopt an accessibility policy, train clinical-content and portal teams, publish an accessibility statement with a monitored contact channel, and schedule recurring audits. Under Section 504 and 1557, documented good-faith processes materially change how OCR treats a complaint.
Test statements, consents, and after-visit summaries for tagging and structure.
Covers everything WCAG 2.1 AA requires — the Section 504 standard — and more.
Portal, scheduling, and telehealth audits mapped to Section 504 and 1557 obligations.
Litigation data, including healthcare's rising share of accessibility suits.
At minimum, ADA Title III applies to private practices as places of public accommodation, covering websites, portals, and apps under prevailing DOJ and court interpretations. If the practice bills Medicare or Medicaid or receives any other HHS funding — which nearly all do — the HHS Section 504 web rule also applies, imposing WCAG 2.1 AA on web content, mobile apps, and kiosks, and Section 1557 of the ACA adds effective-communication and telehealth accessibility obligations. State civil rights laws such as California's Unruh Act can add statutory damages on top.
The HHS Section 504 rule set a compliance date of May 11, 2026 for most covered entities, with smaller entities on phased later timelines — and unlike the DOJ Title II rule, it was not extended. If you missed it, do not wait for a complaint: commission an audit immediately, fix the highest-impact barriers (portal login, scheduling, forms, key PDFs) first, and document a dated remediation plan. Demonstrable progress and a credible plan are the strongest position you can be in if OCR opens an investigation.
Yes. The Section 504 rule explicitly covers web content and mobile applications that covered entities provide or make available, which includes patient portals, telehealth apps, and prescription-refill apps — even when a vendor like an EHR company builds and hosts them. The covered entity remains legally responsible, so vendor contracts should require WCAG 2.1 AA conformance, current accessibility documentation, and remediation timelines for known defects.
Section 1557 and the ADA's effective-communication rules require that telehealth be as accessible as in-person care. Practically: the scheduling and join flow must work with screen readers and keyboards, video visits must support real-time captioning or qualified sign-language interpreters when needed for effective communication, in-call controls need accessible names and states, and any prerecorded instructional video needs captions. If your telehealth vendor cannot support these, the compliance failure is yours, not just theirs.
Yes — documents are one of the most common findings in healthcare accessibility reviews and OCR resolutions. An untagged PDF has no structure a screen reader can navigate, which denies blind patients private, independent access to their own health information — precisely what effective-communication rules protect. Fix the templates in the systems that generate documents at volume, tag the high-traffic static PDFs, and prefer HTML delivery for new content.
Both. Healthcare's share of private accessibility litigation is smaller than retail's but rising, with suits over appointment scheduling, portals, and pharmacy sites — and the Section 504 rule taking effect in May 2026 gives plaintiffs and regulators an explicit technical standard to measure against. Section 504 also carries a private right of action, so missing the WCAG 2.1 AA requirement creates exposure on two fronts at once. Our lawsuit tracker follows the trend.
We audit patient portals, scheduling flows, telehealth platforms, and document pipelines against WCAG 2.1 AA, and deliver a remediation plan you can show a regulator.