12:51:59 RRSAgent has joined #rqtf 12:51:59 logging to https://www.w3.org/2019/09/11-rqtf-irc 12:52:01 RRSAgent, make logs world 12:52:01 Zakim has joined #rqtf 12:52:03 Meeting: Accessible Platform Architectures Working Group Teleconference 12:52:03 Date: 11 September 2019 12:53:02 agenda+ Real-time communication accessibility: interdependencies and opportunities for coordination. 12:53:23 agenda+ XAUR draft. 12:53:27 present+ 12:53:31 chair: jasonjgw 12:59:28 Joshue108_ has joined #rqtf 13:02:47 janina has joined #rqtf 13:03:15 I'm on my way, but I need to reboot my phone ... 13:06:51 zakim, agenda? 13:06:51 I see 2 items remaining on the agenda: 13:06:52 1. Real-time communication accessibility: interdependencies and opportunities for coordination. [from jasonjgw] 13:06:52 2. XAUR draft. [from jasonjgw] 13:06:58 present+ 13:07:56 SteveNoble has joined #rqtf 13:07:58 zakim, next item 13:07:58 agendum 1. "Real-time communication accessibility: interdependencies and opportunities for coordination." taken up [from jasonjgw] 13:08:09 present+ 13:08:10 scribe: Joshue108 13:08:57 JW: I understand that we are concentrating on the interdependencies between groups etc that arise between use cases and user requirements etc 13:09:07 I've written a summary and posted that to list. 13:09:41 For each one there are dependencies between one or more working groups or community groups etc 13:10:03 I'm not totally sure which ones are addressed and/or are a matter of implementation. 13:10:39 The AGWG are clearly a dependency for all that needs to be implemented in RTC type communications. 13:11:13 There may be other requirements that Silver will need to look at. 13:11:54 https://lists.w3.org/Archives/Public/public-rqtf/2019Sep/0026.html 13:12:07 Real-time communication accessibility - working group interdependencies mail from Jason 13:14:37 JOC:Can we walk thru them 13:14:43 JW: Sounds good. 13:14:59 scribe: SteveNoble 13:15:58 Josh: Incoming calls - added this with callerID merged these 13:16:39 Josh: User need - where the user needs to know identity of incoming calls 13:17:09 Janina: suggests the ability of routing this through a differt device 13:17:55 For instance one streat through a buetooth headset and another stream through another device 13:18:55 Call notification could be routed to a briller without interupting the audio stream 13:19:57 Is there an API in RTC for notifications? 13:20:29 Not sure, but we could ask about this. 13:21:06 But we could ask for standard notification techniques to be used 13:21:53 Strandards may differ per browser and platform 13:21:54 q? 13:22:31 Janina: Could be a role for ARIA, but we don't know yet 13:23:38 Could be a use case for ARIA live regions for notifications when these appear in the same HTML document 13:23:55 I've captured Janinas suggestions a la ARIA. 13:24:29 Accessible Call Set up 13:26:53 Josh: safe to take this out 13:27:02 Judy has joined #rqtf 13:27:27 Josh: Audio rooting of multi channel 13:28:45 Josh: second screen issues 13:29:52 Josh to discuss Audio Routing use case with Second Screen at TPAC. 13:32:35 Use case to manipultae volume levels of independent audio streams with audio description 13:32:57 Josh to mention Dynamic Audio description values Media Working Group, Web and Networks IG, Second Screen at TPAC 13:34:54 Jason: the content of the audio stream can be filtered to go to the desired output 13:36:18 Audio-subtitling/spoken subtitles 13:37:21 User need example, Spanish subtitles need to be spoken during a movie 13:37:58 Janina: this is a rare use case - where would this happen? 13:39:02 Janina: probably not a WebRTC use case 13:39:35 More of a media-retated thing 13:40:20 Josh: will take that one out 13:40:36 Communications Control of Alternate Content 13:41:37 Josh: had a merge flag on this one - perhaps with data channel? 13:42:19 Jason: live captions in a teleconference session 13:42:56 Janina: this is a growing use case 13:43:40 Josh: will merge this is another example of the text communication 13:44:25 Josh: change to communication chanel control 13:46:22 Janina: mentioned focus tracking bug issue in Android, but should remove that as it is ephemeral 13:48:59 Judy: pleased with the process of this document - looking good 13:52:05 q+ to suggest looking at the Merge items 13:52:13 ack me 13:52:13 Joshue108_, you wanted to suggest looking at the Merge items 13:52:27 Jason: we will postpone the second agenda item 13:56:24 merge “Audio routing and multi-channel” and "communication channel control" 13:56:39 Am making that edit now.. 13:57:26 Audio Routing and Communication channel control 13:57:42 https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases#Audio_Routing_and_Communication_channel_control 13:58:51 Janina: components need to be individually controlled 14:03:59 “Control relative volume and panning position for multiple audio" could be merged with "“Audio routing and multi-channel” as long as we include the different use cases 14:04:12 zakim, bye 14:04:12 leaving. As of this point the attendees have been jasonjgw, Joshue108_, SteveNoble 14:04:12 Zakim has left #rqtf 14:04:26 rrsagent, make minutes 14:04:26 I have made the request to generate https://www.w3.org/2019/09/11-rqtf-minutes.html jasonjgw 14:05:41 janina has left #rqtf 14:41:40 Judy has joined #rqtf 15:07:56 Joshue108_ has joined #rqtf 15:41:02 Joshue108_ has joined #rqtf 15:41:14 interaccess has joined #rqtf 17:44:55 Judy has joined #rqtf