RE: WebRTC Browser to Browser Use cases

Can WebRTC support the equivalent of Real-Time Text in the telecommunications world? That is, as a first approximation, a mode in which every character is sent to the other party (or parties) as soon as it is typed/entered, and deletion is also supported?

A quick search suggests that WebRTC supports text messages, but answering the question above requires a deeper knowledge of its capabilities than I currently possess.

Please note also that, if there is insufficient time to develop the use cases at the APA meeting, the Research Questions Task Force is available to be called upon – not that I’m recommending that course of action – I’m merely noting the option.

From: joconnor <joconnor@w3.org>
Sent: Monday, April 15, 2019 4:51 AM
To: Janina Sajka (janina@rednote.net) <janina@rednote.net>
Cc: public-apa@w3.org
Subject: WebRTC Browser to Browser Use cases


Hi Janina,

I thought this could start a useful discussion around WebRTC use cases for a11y.. Regarding WebRTC and a11y use cases - you mentioned on a recent call that there is no no browser mechanism for a user to control media and content. While I've been reviewing the WebRTC Next Version use cases, I've also looked at the original 'Web Real-Time Communication Use Cases and Requirements' doc, and notice that in 2.3.  Browser-to-Browser Use Cases > 2.3.1.  Simple Video Communication Service > 2.3.1.1.  Description., it mentions clearly that the user needs to be able to:



<quote>

Select to remove and reinsert the self-view as often as desired,

   o  change the sizes of his/her two video displays during the session,
      and

   o  pause the sending of media (audio, video, or both) and mute
      incoming media.

</quote>



Does that mean that these WebRTC use cases are just not yet implemented in browsers?

Please advise if I am missing something.



Thanks



Josh



[1] https://www.w3.org/TR/webrtc-nv-use-cases/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fwebrtc-nv-use-cases%2F&data=02%7C01%7Cjjwhite%40ets.org%7Ccbb3df6a7ac04607a41e08d6c17fa339%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636909151286661196&sdata=wvDLDOHRZczW5NdzlDPXjhhaIihIovS%2BxGzB%2FtjXepA%3D&reserved=0>

[2] https://tools.ietf.org/html/rfc7478<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7478&data=02%7C01%7Cjjwhite%40ets.org%7Ccbb3df6a7ac04607a41e08d6c17fa339%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636909151286661196&sdata=sEkbRTVpSahVW5rCuCD1OnL3%2F%2F83F9sqjmeNGqmgs2Y%3D&reserved=0>

--

Emerging Web Technology Specialist/A11y (WAI/W3C)

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________