Access to Video Conferencing
In this document, the Federal Communications Commission (FCC or Commission) takes steps to ensure the accessibility of interoperable video conferencing services (IVCS). The Commission provides additional clarity on how the Commission's accessibility performance objectives apply to interoperable video conferencing services (IVCS), modifies those performance objectives to ensure access to IVCS, and addresses how the Interstate telecommunications relay services (TRS) Fund will support the provision of Video Relay Service (VRS) and other forms of TRS in video conferences.
What this rule actually says
The FCC is requiring video conferencing services to be accessible to people who are deaf, hard of hearing, blind, or have low vision. This means if a product lets people video call each other—whether it's a native feature or integration—it needs captions, screen reader compatibility, and other accessibility features built in. The rule also clarifies how relay services (like sign language interpreters) get funded when used in video conferences.
Who it applies to
- If you have a video conferencing feature (live video calls between users, even as a secondary feature), this applies to you
- If you're in the US, this applies; international services used by US customers likely count too
- Excluded: Audio-only calls, recorded videos, pre-recorded content, internal employee meetings (mostly)
- Included: AI medical scribes with video intake, hiring assistants with video interviews, support chatbots with video capability, any product where users video call each other or call into your service
- User data scope: The rule covers accessibility features and relay service integration—not general data privacy
What founders need to do
- Audit your product for video conferencing (1-2 days): Does your app/platform include live video calls or video meetings? If no, you're likely out of scope; if yes, proceed.
- Implement accessibility features (2-4 weeks): Add real-time captions, keyboard navigation, screen reader support, and high-contrast mode. Use existing tools (WebRTC libraries often have built-in accessibility hooks).
- Integrate with relay services (1-2 weeks): Ensure users can connect Video Relay Service (VRS) interpreters during calls. This usually means accepting phone numbers and enabling dial-in alongside video, plus clear UI to request relay services.
- Test with actual users (ongoing): Run accessibility testing with deaf and blind users—automated tools miss real-world friction. Budget 5-10 hours quarterly.
- Document your compliance (2-3 days): Write down which accessibility features you've built and how relay services work in your product. You don't need formal certification, but FCC complaints will ask for this.
Bottom line
Act now if you have video calling; monitor if you're planning to add it; ignore if you're audio-only or text-only for the next 12 months, but expect this to tighten.