You're the 1557 Coordinator: The Law Behind the Job

Three separate regimes, three separate clocks, and only one of them is actually new. Here's how to tell them apart.

If you're new to this seat, the first thing that'll trip you up isn't the law itself. It's that everyone around you talks about "the healthcare accessibility deadline" like there's exactly one, and there isn't. There are at least three regimes stacked on top of each other, and confusing them is how a coordinator ends up telling leadership "we have time" about the one obligation that's already overdue.

Let me untangle the stack once, so it stops being confusing.

Regime one: Section 1557, and it's mostly already due

Section 1557 of the Affordable Care Act (opens in new window) is the federal law prohibiting disability discrimination — among other grounds — in health programs that receive federal financial assistance, which through Medicare and Medicaid alone covers nearly every provider reading this. Its coordinator designation requirement (15 or more employees), written policies and grievance procedures, staff training, and the annual nondiscrimination notice with its language-access companion are not future deadlines. Their compliance dates have already passed. If any of that is missing at your organization, it's overdue, not upcoming — and it's also the cheapest fix in this entire series.

Section 1557's general duty that health programs delivered through websites, apps, kiosks, and telehealth be accessible has applied since the rule took effect, with no phase-in. That's worth reading twice, because it's the opposite of what most new coordinators assume.

Regime two: the WCAG clock that actually moved

The dated requirement — WCAG 2.1 AA for web content and mobile apps, with an actual compliance calendar — lives in HHS's regulations implementing Section 1557 (opens in new window), and that's the specific clock that's moved by rulemaking as recently as this year. HHS's own announcement of the extension (opens in new window) is worth reading closely, because of what it does and doesn't cover — more on that below.

I'm not printing the actual dates in this piece. They've moved once already and the pattern suggests they could move again. Check the current requirement before you make any decision that depends on a specific date.

What the moved date didn't touch

Here's the mistake I see constantly, and it's an expensive one: hearing "the healthcare accessibility deadline was extended" and assuming everything got easier. The extension moved exactly one clock — WCAG conformance for web content and mobile apps. It did not touch kiosk accessibility, which is a general duty already in force with no phase-in at all. And it did not touch the equipment rules.

Separate from anything digital, the Access Board's medical diagnostic equipment standards (opens in new window) require accessible exam tables, chairs, weight scales, and x-ray equipment — covering purchases and leases until a set share of each equipment type is accessible, with a higher share required for rehabilitation and mobility-specialty facilities. The initial requirement, for at least one accessible exam table and one accessible weight scale, has already arrived, and it was not extended when the web dates were. If nobody in your organization owns a medical equipment inventory, that's a this-quarter item, not a someday one.

Regime three: the ADA, layered on top

If you're a public hospital, health district, or public health agency, Title II of the ADA applies too, with its own web rule and its own dated compliance tiers. If you're a private provider, Title III's general accessibility obligations apply instead. Map your organization against all three regimes once, in writing, with your counsel — because which rules reach you depends on your entity type and your funding sources, and that's not a question I can answer generically in an article.

What this actually means clinically

The regulatory language here is nondiscrimination. The operational reality is patient safety, and I want to say that plainly because it changes how the conversation lands with your quality and risk committees. A patient portal that can't be operated by keyboard is a missed test result. A discharge instruction locked inside a scanned image is a readmission risk. An inaccessible consent form is consent that may not actually hold up. And telehealth platforms are covered health programs under this same duty — the effective-communication obligation, interpreters and captioning included, applies to the virtual visit exactly as it applies to the in-person one.

Framing accessibility defects as clinical-risk items isn't spin. It's the accurate frame, and it's the one your organization is already built to act on.

Enforcement, in practice

Recent federal disability enforcement in this sector has centered heavily on effective communication — interpreter and auxiliary-aid failures — and the resolution pattern is consistent: a designated coordinator, written policies, training, and a monitoring period. That's not a coincidence, and it's good news in a specific way: your organization already knows how to run a corrective-action cycle. This series just points that machinery at a new class of defect.

None of this is legal advice, and none of it substitutes for your own counsel confirming which rules reach your specific entity type. If you want a fast read on how a specific patient-facing page actually measures up before you bring it to counsel or your compliance committee, ask Luke to check it. Our WCAG reference and methodology cover how we verify claims like the ones in this series.

Next: your first ninety days as a 1557 coordinator — what to actually do with all of this, starting Monday.

---

Sources: HHS Final Rule — Nondiscrimination in Health Programs and Activities (opens in new window) · HHS Guidance on Section 1557 (opens in new window) · HHS Press Release — Web and Mobile Accessibility Deadline Extension (opens in new window) · U.S. Access Board — Medical Diagnostic Equipment Standards (opens in new window)