Re: WebRTC Browser to Browser Use cases

Hi, Josh:

Really delighted to have your help with WebRTC review. It's likely to
become an important communication framework for the 21st Century, imho.

A response below.

Joshue O Connor writes:
> 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.
> 

I suspect these may be implemented, though I don't know for sure. Also,
WebRTC is likely to be implemented as a separate application, e.g.
Skype, and not just as browser plugins. So, we need to canvas for
implementation experience beyond the browser. Face Time comes to
mind--is it RTC? I don't know. Another highly likely platform would be
Android.

We should probably learn whether or not Zoom is implementing RTC:
https://zoom.us. Please note that Zoom claims WCAG 2 conformance.
W3C/WAI would likely be on Zoom except that we benefit from the MIT
Webex deployment contract.

However, what's missing in the above requirements is any concept of more
than one camera, microphone, display unit, or audio device.


Also, somewhere in the reqs and specs, there's a data channel
replicating what we now do on IRC. That needs to be directable to the
user's device of choice--perhaps a BlueTooth connected braille display?

These are a11y concerns, but I submit we can easily write scenarios that
make them mainstream concerns. What grandparent wouldn't want to cast
the video stream of the grandkids up on the giant 4K 85 inch display
mounted in the living room?

I believe we need the concept of a communications controller able to
shunt video, audio, and/or text to one or more devices in the local
environment both in lieu of the default communicating device, or in
addition to.

hth

Janina

> 
> Thanks
> 
> 
> Josh
> 
> 
> [1] https://www.w3.org/TR/webrtc-nv-use-cases/
> 
> [2] https://tools.ietf.org/html/rfc7478
> 
> -- 
> 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 Monday, 15 April 2019 09:12:28 UTC