The Section 504 telecom compliance deadline is May 11, 2026 — three days from today. Every healthcare organization that receives federal financial assistance is required to have its phone and communications systems accessible to patients with hearing loss, speech disabilities, and those who rely on relay services. If you haven't done this audit yet, here's exactly what to check this week, what failure looks like, and where to get help before the clock runs out.
May 11, 2026 — HHS Final Rule Compliance Window Closes
The 2024 HHS update to 45 C.F.R. Part 84 gave healthcare organizations two years to comply. That window closes this Sunday. After May 11, the Office for Civil Rights (OCR) can begin accepting enforcement complaints and initiating compliance reviews against organizations that haven't met the telecom accessibility standard.
What Section 504 Actually Requires from Your Telecom Stack
Section 504 of the Rehabilitation Act prohibits disability discrimination in any program receiving federal financial assistance. For healthcare organizations — which almost universally accept Medicare or Medicaid — that means your phone systems must be accessible to patients with disabilities who need to communicate with your organization.
The 2024 HHS Final Rule didn't invent this obligation. It clarified and codified it for modern communications technology. In plain terms: if a patient uses a hearing aid, relies on a sign language interpreter via video relay, uses a 711 relay operator to make calls, or needs real-time captioning to participate in a phone conversation — your system must support that. A generic "ADA compliant" claim from your vendor does not satisfy this standard.
Any healthcare organization that receives any federal financial assistance — including Medicare reimbursements, Medicaid payments, NIH or HRSA grants, federal employee health plan reimbursements — is covered by Section 504. This includes hospitals, health systems, FQHCs, independent clinics, and most private practices with even minimal federal payer mix.
The specific telecom-related obligations under Section 504 include: TTY/TDD device compatibility, hearing aid compatible (HAC) endpoints at patient-facing stations, Real-Time Text (RTT) capability, Video Relay Service (VRS) call support, IP Captioned Telephone Service (IP CTS) compatibility, and 711 relay service access through your IVR and auto-attendant. Each of these is a distinct technical requirement — not a checkbox a vendor can claim by policy alone.
For a complete breakdown of each requirement and a 10-point compliance checklist, see our full guide: Section 504 Telecom Compliance Checklist for Healthcare Organizations.
Three Audits to Run This Week
With three days to the deadline, you can't run a complete compliance program from scratch. But you can create a documented compliance posture — which is what OCR looks for when evaluating good-faith efforts. Here are the three highest-impact audits your IT team can complete before May 11.
Video Relay Service (VRS) Call Quality Test
Patients who are deaf and communicate in American Sign Language use Video Relay Services — a certified interpreter connects via video and voices the call to you while signing back to the patient. Your phone system must accept these calls and maintain stable video quality throughout the conversation. The interpreter needs to see the patient clearly enough to accurately translate — bandwidth degradation mid-call isn't a minor annoyance, it's a communication breakdown.
- Place a test call from at least two major VRS providers — Purple Communications (purple.us) and ZVRS (zvrs.com) both offer test lines. Call your main patient-facing number.
- Verify video quality remains stable for 5+ minutes under your normal network load (don't test at 2 AM when no one else is on the network).
- Confirm your network QoS configuration doesn't deprioritize video traffic. Check with your network team that VoIP + video traffic is prioritized over general web traffic on patient-facing network segments.
- Document the test: date, time, provider used, call quality observed, and who conducted it. This documentation is your compliance record.
IP Captioned Telephone Service (IP CTS) Compatibility
IP Captioned Telephone Services (CapTel, CaptionCall, InnoCaption) allow patients with hearing loss to read real-time captions of what's said during a phone call. These services work by routing the call through a captioning center that transcribes the audio in near-real-time. For this to work, your phone system's SIP implementation must be compatible with the captioning service provider's infrastructure. SIP interoperability failures are common — and they fail silently from the patient's perspective.
- Request a compatibility test call from InnoCaption (innovatec.com) — they support inbound test calls for healthcare IT validation purposes.
- During the test call, verify that audio is transmitted clearly in both directions and that there are no SIP negotiation errors in your UCaaS platform logs.
- Check your Session Border Controller (SBC) or carrier gateway configuration for known IP CTS incompatibility flags — ask your UCaaS vendor directly: "Does your SBC have known incompatibilities with CapTel or CaptionCall?"
- Document the test outcome. If it passes, file it as evidence. If it fails, document the gap and the remediation steps you're taking.
711 Relay Service Access Through Your IVR
When a patient uses 711 relay, a relay operator dials your organization on the patient's behalf. The interaction pattern is different from a standard caller: the relay operator will identify themselves at the start ("This is a relay call from…"), there will be pauses between relay operator keystrokes as they wait for the patient to type responses, and DTMF timing is extended. IVR systems designed for normal callers routinely fail on relay calls — and the patient simply gets disconnected with no explanation.
- Dial 711 from a phone not in your organization's network. When connected to the relay operator, ask them to call your main patient-facing number. Navigate your IVR as a patient would.
- Specifically test: (a) whether DTMF inputs work with a 3–5 second delay between keystrokes, and (b) whether voice-recognition-only prompts have a DTMF fallback option.
- Verify that the relay operator's introductory announcement doesn't trigger your system's spam/fraud detection and immediately disconnect the call.
- Test your after-hours line separately — after-hours IVR systems are often independently configured and frequently fail relay calls even when the main system passes.
Free Section 504 Healthcare Compliance Guide
Download the complete guide — covers all 6 telecom requirements, vendor evaluation criteria, and documentation templates your compliance team needs.
What Non-Compliance Looks Like
Non-compliance with Section 504 telecom requirements isn't a paperwork fine. It's federal civil rights enforcement with consequences that range from mandated remediation programs to — in serious cases — suspension of federal funding. Here's what the enforcement landscape looks like post-May 11.
| Enforcement Action | What It Means | Severity |
|---|---|---|
| OCR Complaint Investigation | A patient, advocacy organization, or competitor files a complaint. OCR investigates your telecom systems. You must produce documentation of compliance — or a remediation plan if gaps exist. | High |
| Corrective Action Plan (CAP) | If OCR finds violations, they issue a CAP requiring you to remediate specific systems on a defined timeline, with regular reporting. You're under monitored oversight until resolved. | High |
| Public Resolution Agreement | OCR frequently publishes resolution agreements. Your organization's name, the violations found, and the corrective terms become public record — visible to patients, press, and competitors. | High |
| Federal Funding Termination | In cases of persistent or willful non-compliance, OCR can initiate proceedings to suspend or terminate Medicare and Medicaid reimbursements, plus other federal grants. | Critical |
| Private Lawsuit | Section 504 creates a private right of action. Patients can sue directly for disability discrimination and seek compensatory damages, injunctive relief, and attorney's fees — without going through OCR. | Critical |
OCR consistently treats organizations with documented compliance efforts more favorably than those with no compliance posture. If you haven't completed a full audit by May 11, the most important thing you can do today is start documenting: what you've tested, what gaps you've found, what interim accommodations you've put in place, and what your remediation timeline is. A written, dated compliance log is your protection even if you're not fully compliant on the deadline date.
One nuance worth understanding: the May 11 deadline applies to the 2024 HHS Final Rule updates. The underlying Section 504 obligation has existed since 1973. OCR does investigate complaints about telecom accessibility practices that predate the 2024 rule. The deadline isn't a clean slate — it's the point at which the updated standard becomes formally enforceable. Organizations that have been non-compliant for years don't get amnesty because the rule was updated.
Get the Free Compliance Guide
Clearony's Section 504 healthcare telecom compliance guide was built for healthcare IT and compliance teams who need to move fast. It covers all six telecom accessibility requirements under the 2024 HHS Final Rule, provides a 10-point audit checklist, includes vendor evaluation criteria, and contains documentation templates you can hand directly to your compliance and legal teams.
The guide is available free, gated only by email — because this deadline is real and we'd rather you have it than not. You'll also get a follow-up with our UCaaS vendor compliance matrix, which scores 27 major platforms against Section 504, HIPAA, and HITRUST criteria.
Section 504 Healthcare Telecom Compliance Guide
10-point checklist · Vendor evaluation criteria · Documentation templates · 2024 HHS Final Rule breakdown. Free with email.
Not Sure If Your Telecom Vendor Is Compliant?
The most common situation we see: an IT leader runs the audit above, gets vague answers from their UCaaS vendor, and isn't sure whether they have a real gap or a documentation problem. The difference matters — a documentation problem is fast to fix; a real platform gap may require a vendor change.
Clearony's needs analysis wizard was built to answer this in under 10 minutes. Answer 20 questions about your organization's size, patient population, current telecom vendor, and compliance requirements — and get a ranked comparison of UCaaS vendors scored against Section 504, HIPAA, and HITRUST criteria. You'll know within 10 minutes whether your current vendor passes, falls short, or needs clarification.
It's free, takes about 8 minutes, and gives you a defensible starting point for both vendor evaluation and your compliance documentation.
Find Out If Your Vendor Is Compliant — In 8 Minutes
Answer 20 questions about your telecom setup and get a ranked list of Section 504-compliant UCaaS vendors matched to your requirements. Free, instant results.