Access to Video Conferencing
In this document, the Federal Communications Commission (FCC or Commission) proposes to amend its rules to ensure that interoperable video conferencing services (IVCS) are accessible to people with disabilities and to facilitate the integration and appropriate use of telecommunications relay services (TRS) with video conferencing. These amendments are proposed to meet the need for people with disabilities to participate fully in video conferences, a technology that appears to have permanently altered the norms of modern communication in the workplace, healthcare, education, social interaction, and civic life.
What this rule actually says
The FCC wants to require video conferencing platforms to work with accessibility tools (like screen readers and relay services for deaf/hard-of-hearing users). If someone uses a video conferencing service to join a meeting, they should be able to do it with whatever assistive technology they use for other digital tools. This is still a *proposed* rule, not final law—so it's not binding yet.
Who it applies to
- If you build or operate a video conferencing service (even if it's just an embedded feature in your product), this likely applies to you.
- If you offer a medical scribe, hiring assistant, or support chatbot that includes video calls, you may need to ensure video conferencing features are accessible.
- If you integrate a third-party video conferencing tool (Zoom, Google Meet, Teams), you're probably passing responsibility to them—but check your terms.
- Jurisdiction: This is a U.S. FCC rule, so it applies if you serve U.S. users. No clear geographic carve-outs mentioned.
- What's in scope: Video conferencing functionality, caption support, compatibility with relay services.
- What's out of scope: Audio-only calls, chat-only products, or phone services (those have separate rules).
What founders need to do
- Audit your video conferencing setup (2-3 days). Does your product include live video calls? If yes, document which platform you use and whether it already supports captions, screen readers, and relay services. Most major platforms (Zoom, Meet) already do.
- Monitor the rule's status (ongoing, ~1 hour/month). Since this is still proposed, check the FCC website quarterly. When finalized, you'll have a transition period—likely 12-24 months.
- If you built custom video conferencing (1-2 weeks). Test with assistive tech. Add live captioning. Ensure keyboard navigation works. If this feels heavy, consider switching to a third-party platform instead.
- Document your compliance (1 day). Keep records showing which accessibility features your video conferencing supports. This protects you if someone claims you're non-compliant.
- Don't over-rotate right now (ongoing). The rule hasn't passed. If you're using Zoom or Meet, you're likely fine already. Save major engineering effort for when the rule is finalized.
Bottom line
Monitor—but don't panic yet. This is proposed, not law. If your video conferencing is third-party-hosted (Zoom, Google Meet), you're probably already compliant. If you built it custom, start planning accessibility features now, because some form of this rule will likely pass within 12-18 months.