Section 504 Web Accessibility: What HHS-Funded Healthcare Providers Owe Patients

If your hospital, clinic, community health centre, or practice receives federal financial assistance from the Department of Health and Human Services, there is a web accessibility rule that applies to you specifically — separate from the ADA, and separate from the Section 1557 language access obligations you already know about.

It comes from Section 504 of the Rehabilitation Act, and HHS finalised the digital accessibility piece in its 2024 nondiscrimination rule. The compliance dates were extended by about a year via an interim final rule in May 2026, in explicit recognition that a lot of health centres and hospitals were not going to make the original date.

Am I covered?

If you receive HHS federal financial assistance, yes. In practice that captures a very wide slice of American healthcare, including:

• Hospitals and health systems participating in Medicaid
• Federally Qualified Health Centres and look-alikes
• Community health centres and primary care practices receiving HHS grants
• Behavioural health and substance use programmes with HHS funding
• State and local health departments

Note that this is a funding-based trigger, not a size-based one. A small practice receiving assistance is covered; a large one that genuinely receives none is not covered by this rule, though it may well be covered by ADA Title III.

The compliance dates run in two tiers based on employee count, and we keep the current dates in one place — the ADA Title II deadline post carries both the DOJ and HHS timelines side by side so they cannot drift apart.

The standard is WCAG 2.1 Level AA, the same technical bar as the DOJ rule. That is deliberate and helpful: if you are a public hospital district, you are likely covered by both rules and you only have to build to one standard.

What patient-facing content does this actually cover?

The rule reaches web content and mobile applications. For a healthcare provider, the list that matters is:

• The public website, including provider directories and location and hours information
• The patient portal — appointments, results, messaging, bill pay
• Mobile apps you offer patients
• Online intake and registration forms
• Documents you publish: notices of privacy practices, financial assistance policies, consent forms, discharge instructions, plan summaries, appointment letters
• Telehealth entry points, including the page a patient uses to join a visit

Two of those are worth pulling out because they carry the most risk.

The patient portal. It is usually a vendor product, it is where the highest-stakes interactions happen, and it is frequently the least accessible thing an organisation operates. Your obligation does not transfer to the vendor. What transfers is the leverage — which is why the conformance report belongs in your contract.

Financial assistance and consent documents. These are the documents where a patient’s inability to read them has direct financial and clinical consequences. They are also, almost universally, PDFs exported from Word or scanned from paper.

Where healthcare gets hit twice

Healthcare is the sector where accessibility and language access collide hardest, because Section 1557 already obliges you to provide meaningful access to people with limited English proficiency.

So the same discharge instruction sheet has to be:

• Readable by a screen reader (Section 504 / WCAG 2.1 AA), and
• Available in the languages your patient population actually speaks (Section 1557), and
• Readable by a screen reader in those languages

That third requirement is the one almost nobody satisfies. Translating a document does not make it accessible, and it introduces a failure a monolingual document cannot have: if your Spanish discharge instructions are not marked as Spanish, a screen reader pronounces them with English phonetics and a blind Spanish-speaking patient gets audible noise. We wrote that up in translated documents and WCAG language of parts.

For the clinical documents themselves, what HIPAA-compliant medical translation actually means covers the handling side, and language access and Joint Commission standards covers the accreditation overlap.

Does an accessibility overlay satisfy this?

No. A JavaScript widget that adds a contrast toggle and a text resizer does not make underlying content conform to WCAG 2.1 AA, and it does not fix an untagged PDF at all. Documents are not touched by overlays. Neither is reading order, form labelling, or alt text accuracy.

Overlays are attractive because the sales pitch is one line of code. What they do not do is change the thing the standard is actually measuring.

What should we do in the next quarter?

1. Confirm your tier and your date. Employee count decides which of the two HHS dates you are on.
2. Inventory patient-facing documents. Start with anything a patient must read to receive care or to understand what they owe.
3. Get the portal conformance report. Ask your vendor for a current VPAT or ACR. If they cannot produce one, that is itself the finding. What is a VPAT explains what a useful one looks like versus a box-ticking one.
4. Cross-reference against your language list. Every document that exists in a second language is a document that needs the language work and the tagging work.
5. Test with a screen reader on real tasks. Book an appointment. Pay a bill. Read a result. If your team cannot complete those with a screen reader, neither can a patient.
6. Fix the publishing pipeline. Clinical and financial documents change constantly. A one-time remediation with an unchanged process buys you a year at most.

Where Taika fits

We remediate patient-facing documents and web content to WCAG 2.1 AA and Section 508, and we translate medical content with the handling controls healthcare requires — meaning a discharge instruction can come back tagged, correctly structured, and correctly language-marked in every language you publish it in.

Start at document accessibility for the document estate, healthcare language access for the 1557 side, or accessibility and compliance services if you are scoping the whole obligation at once.

Working to the HHS date? Request a quote with a rough document count and your patient languages, and we will come back with a sequence that puts the highest-risk documents first. If you want evidence before an internal conversation, run a consent form or financial assistance policy through the PDF accessibility checker.