Request for joint meeting at TPAC

Dear W3C Colleagues:

This is a request for a joint meeting from the Accessible Platform
Architectures (APA) Working Group. We note that both our WGs are meeting
Thursday and Friday at TPAC, and we would appreciate an hour of your
time on several accessibility topics of joint interest.

Most critically we in APA are concerned that implementations of WebRTC
support cann support the Real Time Text (RTT) protocol being required of
telecommunications providers in the U.S. by the Federal Communications
Commission (FCC). There are several wrinkles to this requirement,
several of which are addressed in the forwarded message below. We want
you to be fully aware of the requirements as they currently exist, and
their impact on persons who are deaf or hearing impaired (primarily).

Beyond this most immediate concern we have been developing several
accessibility related use cases we would hope you can address in future
revisions of WebRTC, if not already supported. An early draft of our
document is available here:

https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases

Please advise if and when we might meet during Thursday or Friday of
TPAC.

Thanking you in advance for your consideration,

Janina Sajka, Chair
Accessible Platform Architectures (APA) WG
http://www.w3.org/WAI/APA/


Joshue O Connor writes:
> Hi Dom,
> 
> [with Janina and Jason - leads on APA/RQTF respectively, and Judy]
> 
> It was good to talk earlier and hope here to unpick the question about RTT
> interoperability and how WebRTC will need to support that. [1]
> 
> I'm outlining the 'case' here and looking forward to input from Janina,
> Jason and Judy on this, especially in light of FCC requirements. [2]
> 
> Looking back at this, and now trying to put together a 'case' - My own
> reading of the FCC requirements is that it is referencing RTT IETF and that
> it is implicit (if not explicit ) that there will be interoperability
> requirements. For example, in the transition from TTY to RTT is that this
> the case where IETF RFC 4103 is referenced directly in the 'transitioning
> to' doc. [3]
> 
> There were some interesting insights from Jason on a private mail - where he
> mentions for example that if running a relay service, that would need some
> level of interoperability, so that the RTT wouldn’t be handled differently
> depending on which WebRTC-based application was bringing the user into the
> conversation.  There is also interoperability with SIP and other existing
> protocols to consider.
> 
> Jason also makes the point that it may not be sufficient for each WebRTC
> application to create its own means of real-time text handling. Should the
> question is, should this be defined and handled in WebRTC user cases for
> example?
> 
> OK, this mail was to get the ball rolling and start to make the case for RTT
> interoperability support in WebRTC.
> 
> Thanks and I hope this is helpful Dom - looking forward to your input
> 
> Josh
> 
> [1] http://realtimetext.org/rtt_in_detail/standards/ietf
> 
> [2] https://www.fcc.gov/document/transition-tty-real-time-text-technology
> 
> [3] https://www.ietf.org/rfc/rfc4103.txt
> 
> 
> -- 
> Emerging Web Technology Specialist/A11y (WAI/W3C)

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Received on Wednesday, 14 August 2019 19:37:05 UTC