Update on Accessibility WebRTC user requirements document

Hi all,

[+Dom - as staff contact for WebRTC group]

FYI, I've updated our WebRTC use cases document based on the discussion 
on yesterdays call. [1]

I found all your input very useful yesterday and am glad to see the 
progress we are making.

A couple of things to note:

* To progress things - where a user requirement may not be squarely a 
WebRTC thing, I've added [Remove] to it's main heading as a note that 
this may not be in the end, presented to the WebRTC group as a use case. 
This is based on the previous discussions on these specific user 
requirements. If anyone feels this to be inaccurate, and that the use 
case can be presented to the WebRTC group then do let me know. My main 
thinking is to ensure that we have user requirements going to where they 
belong and to hopefully create a clear understanding of what the group 
can do to realise that user requirement.

These can also be moved into another document later as needed as non 
'tech or group specific' user requirements.

* I've renamed the Multiple Audio user requirement to 'Multi Channel 
Audio' - as I think that makes the requirement clearer.

* I've added Second Screen as a target group to the use case for 'Multi 
Channel Audio'.

With regard to the above - I've a question about the Second screen 
groups work  - can we say that they have some responsibility for our 
user requirements that involve different output devices even if they are 
not 'screens'? They say in their charter that the API is agnostic but my 
reading of it is that they are focused on visual displays.[2]

I'm thinking in the context of Janina's comments yesterday and the APA 
preference for 'Second Screen' as a nomenclature for 'other devices'? 
Using this term makes sense to me 'in house' or team side but in terms 
of what the second screen group do, I'm not so sure. [2]

Am I wrong?

Comments and feedback welcome!

[1] https://www.w3.org/WAI/APA/wiki/WebRTC_next_version_use_cases

[2] https://www.w3.org/2014/secondscreen/charter-2018.html

Thanks

Josh

-- 
Emerging Web Technology Specialist/A11y (WAI/W3C)

Received on Thursday, 27 June 2019 11:18:00 UTC