The deadline passed. If your healthcare organization's telecom systems aren't fully Section 504-compliant, you're now operating in enforcement territory. That doesn't mean a penalty is imminent — but it does mean your exposure is real and the window for proactive remediation is open right now. Here's what your actual risk looks like, what OCR does with it, and what to fix first.
May 11, 2026 — HHS Final Rule Compliance Window Closed
OCR is now authorized to investigate telecom accessibility complaints against covered healthcare organizations. Enforcement doesn't happen automatically — it starts with a complaint or a directed compliance review. Your window to remediate before a complaint lands is still open. Use it.
What Your Actual Exposure Is
Missing the May 11 deadline doesn't trigger an automatic penalty. The Section 504 enforcement mechanism is complaint-driven and investigation-based — not a license revocation that fires on a date. OCR doesn't audit every healthcare organization proactively. What they do is respond to complaints filed by patients, advocacy groups, and (increasingly) competitors.
Your exposure depends on how quickly you remediate and how well you document the effort. An organization that missed the deadline but has an active, documented remediation plan is in a materially different position than one that has never thought about it. OCR's published guidance on enforcement priorities explicitly references "good-faith compliance efforts" as a factor in how they respond.
Organizations at highest complaint risk: large health systems with complex IVR trees, FQHCs serving high proportions of patients with disabilities, any organization that has received prior OCR correspondence on accessibility issues, and organizations where a patient has recently reported a problem communicating via relay services. If any of these apply — move fast on documentation and remediation.
The telecom-specific obligations that most commonly generate complaints are: VRS call failures (a deaf patient couldn't reach you via their video relay interpreter), 711 relay call disconnects (a relay operator got dropped by your IVR), and IP CTS incompatibility (a patient with hearing loss couldn't get captions during your phone call). These three failure modes account for the majority of Section 504 telecom complaints in the post-2024 rule enforcement pattern.
The OCR Complaint Investigation Timeline
Understanding the enforcement timeline matters because it defines how much runway you have. OCR investigations are not fast. A typical Section 504 complaint follows this arc:
Complaint Filed & Intake Review
After a complaint is filed, OCR's intake team reviews whether the complaint is timely (filed within 180 days of the alleged violation), whether OCR has jurisdiction (federally funded healthcare organization), and whether the complaint contains enough information to investigate. Most telecom accessibility complaints clear this bar easily — the barrier to filing is low and advocacy groups help patients navigate the process.
If you have remediation documentation in place before a complaint is even filed, OCR's intake reviewers will see your current compliance status during their initial assessment.
Notice to Covered Entity
You'll receive a written notice from OCR's regional office with a description of the complaint allegations and a request for a written response plus supporting documentation. The response deadline is typically 30 days from the notice date, with extensions available on request.
This is where your documentation log becomes critical. OCR is asking: what is your current compliance status? What have you done to achieve compliance? If you have nothing — no audit records, no remediation plan, no test documentation — that void is visible to the investigator.
Investigation & Information Gathering
The bulk of the timeline is here. OCR reviews the documentation you've provided, may request additional records or technical specifications from your UCaaS vendor, and in some cases conducts its own technical testing of your phone systems. For telecom accessibility complaints, OCR increasingly relies on technical consultants who test VRS call acceptance, IP CTS compatibility, and 711 relay IVR access.
Organizations that have completed their own documented testing — and can show they identified gaps and are actively remediating — consistently receive better outcomes than those where OCR's testing is the first time anyone has tested the systems.
Finding & Resolution
OCR issues one of three outcomes. A no-violation finding closes the case. A voluntary resolution agreement (VRA) is the most common outcome — your organization agrees to specific remediation steps and a monitoring period, typically 1–2 years. OCR publishes VRAs publicly; they include your organization's name, the violation findings, and the corrective terms. A referral for formal enforcement — including potential funding termination proceedings — is reserved for willful non-compliance or organizations that obstruct the investigation.
Organizations that proactively remediate before or during the investigation period — and document it — almost never face formal enforcement action. The goal is compliance, not punishment. OCR's pattern consistently shows resolution agreements for cooperative organizations.
Free Section 504 Healthcare Compliance Guide
Covers all 6 telecom requirements, a 10-point audit checklist, and documentation templates — exactly what you need to build your remediation record.
Remediation Priority Matrix: What to Fix First
Not all telecom accessibility gaps are equal. Some are fast to fix (IVR configuration changes), some require vendor cooperation (SBC reconfiguration), and some may require a platform evaluation (VRS-incompatible systems). Here's the priority order based on OCR enforcement patterns and remediation complexity.
| Fix | Priority | Why This Order | Typical Fix Time |
|---|---|---|---|
| 711 Relay IVR Access | P1 — Immediate | Fastest to fix (DTMF timeout + spam filter config). Documented fix within 24–48 hours demonstrates immediate remediation action. Most visible to patients. | 1–2 days |
| IP CTS Compatibility (CapTel, InnoCaption) | P2 — This Week | Often a SBC/codec configuration issue — vendor can resolve in hours once escalated. Test and document before and after the fix. | 2–5 days |
| VRS Call Support (Video Relay) | P2 — This Week | Most commonly cited in OCR complaints. If your system supports it but quality is poor, a QoS configuration may resolve it. True incompatibility requires vendor engagement or platform evaluation. | 3–10 days |
| Hearing Aid Compatible (HAC) Endpoints | P3 — 2–4 Weeks | Hardware-dependent. Inventory patient-facing handsets and identify non-HAC endpoints. Replace priority stations first (reception, scheduling, nurse lines). | 2–4 weeks |
| TTY/TDD Compatibility | P3 — 2–4 Weeks | Lower complaint frequency in 2026 (711 relay has largely replaced direct TTY use) but required for full compliance. Validate your analog gateway or SIP-to-TTY adapter. | 1–3 weeks |
| RTT (Real-Time Text) Support | P4 — 30–60 Days | Lowest current complaint frequency. RTT requires SIP standard compliance at the protocol level. Most modern UCaaS platforms support it — verify with your vendor. | Vendor-dependent |
Most 711 relay failures are caused by two things your IT team can fix today: (1) DTMF timeout windows set too short for relay operator keystroke cadence — increase to 5–7 seconds between digits, and (2) relay operator introductory announcements ("This is a relay call…") triggering spam detection and disconnecting the call. Whitelist relay carrier numbers (AT&T Relay: 800-735-2988, Sprint Relay: various state numbers, T-Mobile Relay). Document the configuration change with timestamps. That's your first evidence of good-faith remediation.
The Documentation Strategy That Protects You
Documentation is not bureaucratic cover — it is the mechanism through which OCR evaluates good-faith effort. Your documentation log should establish a clear timeline: when you identified the compliance gaps, what you found, what you changed, and what the current state is. Here's what to build right now.
Compliance Assessment Log
Create a dated log with one row per compliance requirement. For each: tested (yes/no), test date, result (pass/fail/partial), identified gap (if any), responsible party for remediation, and target date. This is your compliance baseline — OCR reviewers are specifically trained to look for this kind of structured documentation.
- Run a 711 relay test today. Log the result — pass or fail, both matter. A failed test with a documented fix plan is better than no test.
- Request VRS and IP CTS compatibility documentation from your UCaaS vendor in writing — email is fine. The request itself creates a compliance timestamp.
- Assign a named compliance owner — a specific person, not "IT." OCR looks for named responsible parties in remediation documentation.
- Date-stamp everything. Your documentation only protects you if OCR can see that specific actions happened on specific dates.
Interim Accommodation Plan
An interim accommodation plan documents that while a technical gap is being fixed, you have an alternative path for patients who need accessibility. For example: "While VRS call quality issues on Line 3 are being resolved (target: May 22), patients requiring VRS can be routed to Line 1 which has verified VRS support. Staff are trained to offer this redirect." OCR consistently treats organizations with interim accommodations more favorably — it shows awareness and active mitigation.
- Identify at least one confirmed-accessible phone endpoint at each patient-facing location.
- Train reception staff on how to assist a 711 relay call, a VRS call, or a request from a patient using IP CTS.
- Document the training: date, who attended, what was covered. One email to staff with a summary is sufficient.
Remediation Timeline
For each gap you've identified, write a remediation item: what the gap is, what the fix is, who is responsible for the fix, and a target completion date. This doesn't have to be long — one paragraph per item is fine. The existence of a written, dated remediation schedule is what distinguishes "aware and working on it" from "had no idea."
- Keep targets realistic — OCR prefers achievable commitments over aggressive dates that slip. If a vendor change will take 60 days, write 60 days.
- Update the log as items complete. The history of completed items is as important as the open ones.
- File the plan with your compliance officer, legal counsel, or whoever handles HHS correspondence. This documentation needs to live somewhere it can be retrieved quickly.
Run Your Self-Audit Right Now
If you haven't run any compliance tests yet, start today. The three tests below take a combined 90 minutes and produce the foundational compliance documentation your log needs. A failed test with documentation is materially better than no test.
- Dial 711 from a phone outside your organization's network
- Ask the relay operator to call your main patient-facing number
- Navigate your IVR as a patient would — with 3–5 second pauses between selections
- Verify the relay operator's introductory announcement doesn't disconnect the call
- Test after-hours routing separately
- Log: date, time, tester name, result for each step
- Contact Purple Communications (purple.us) or ZVRS (zvrs.com) — both offer test calls for healthcare IT teams
- Request a test call to your patient-facing main number during business hours (not off-peak)
- Verify video quality remains stable for 5+ minutes
- Check that your network QoS doesn't deprioritize video traffic during the test
- Log: provider used, date, call duration, quality observed, any failures
- Contact InnoCaption (innocaption.com) — they support inbound test calls for healthcare IT validation
- During the test call, check UCaaS platform logs for SIP errors
- Verify two-way audio quality without codec degradation
- If your SBC shows errors, escalate to your UCaaS vendor with "Section 504 compliance" as the priority flag
- Log: date, service provider, SIP errors (if any), outcome
Not Sure If Your Vendor Is the Problem?
Answer 20 questions about your telecom setup and get a ranked comparison of Section 504-compliant UCaaS vendors. Know in 8 minutes whether to fix or replace.
If Your Vendor Is the Problem
For some organizations, the remediation path is configuration changes and documentation. For others, the UCaaS platform itself is the bottleneck — VRS-incompatible SBC architecture, IP CTS SIP issues the vendor can't resolve, or a legacy on-prem system that can't support relay calls at all.
If your vendor is the problem, the compliance clock is still running. "We're evaluating vendors" is not a compliant state — but it is a documented remediation action. Start a formal vendor evaluation now, document it, and implement interim accommodations (dedicated accessible line, staff-assisted routing) while the evaluation proceeds.
A vendor transition for a healthcare organization typically takes 60–120 days from decision to go-live. If you start now, you're looking at full compliance by late summer 2026 — which, combined with documented good-faith effort from today, puts you in a strong position relative to any OCR timeline.
Clearony's needs analysis was built for exactly this situation. Answer 20 questions about your organization's size, patient population, current vendor, and compliance requirements — and get a ranked comparison of Section 504-compliant UCaaS vendors with actual compliance scores (not vendor self-attestations). You'll know within 10 minutes which vendors pass, which fall short, and what the switching considerations are for your specific situation.
Find a Compliant Vendor — Know in 8 Minutes
Answer 20 questions about your telecom setup and get a ranked, scored comparison of Section 504-compliant UCaaS vendors matched to your requirements. Free, instant results.