12:17:06 RRSAgent has joined #rqtf 12:17:10 logging to https://www.w3.org/2023/04/05-rqtf-irc 12:17:10 RRSAgent, make logs public 12:17:41 Zakim has joined #rqtf 12:17:41 Meeting: Accessible Platform Architectures Working Group Teleconference 12:17:41 Date: 05 April 2023 12:17:41 present+ 12:17:41 scribe+ 12:17:41 chair: jasonjgw 12:17:41 zakim, clear agenda 12:17:41 agenda cleared 12:19:37 agenda+ Media synchronization use cases and user needs. 12:19:37 agenda+ Collaboration Tool Accessibility User Requirements. 12:19:37 agenda+ Miscelaneous updates and topics. 12:51:19 janina has joined #rqtf 12:51:25 agenda? 12:56:28 scott_h has joined #rqtf 12:59:38 present+ 13:00:07 SteveNoble has joined #rqtf 13:00:16 JPaton has joined #rqtf 13:00:26 present+ 13:00:40 scribe: SteveNoble 13:00:53 present+ 13:01:03 zakim, next item 13:01:03 agendum 1 -- Media synchronization use cases and user needs. -- taken up [from jasonjgw] 13:01:25 present+ John_Paton 13:01:37 present+ Raja 13:02:14 jasonjgw: Updated wiki page in view of our discussion. 13:02:51 Transcript wiki at: https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Transcript_synchronization 13:03:23 jasonjgw: Some of these capabilities seem to exist already 13:04:28 SteveNoble: YouTube uses its own proprietary technology to support the interaction where users can review the video transcript, search for a particular word, and then navigate to that part of the video 13:05:21 Steve investigated, noting that the support for relevant capabilities is proprietary in YouTube. 13:05:30 Steve: it supports searching and navigation to the point where the search term is found in the video. As far as Steve has determined, this capability isn't directly supported in existing Web specifications (WebVTT, TTML). 13:06:17 raja: Google has some capabilities as well using VTT 13:07:00 raja: Times transcripts are easier to add with ASR 13:09:11 jasonjgw: Not sure if TTML or WebVTT specifications are well supported and which might be best to concentrate for new capabilities 13:10:25 janina: WebVTT was a Google tech originally 13:10:57 janina: Both are W3C specs so we can read them 13:11:36 janina: Will need to differentiate between captions and transcripts 13:12:09 Raja: The main thing is if they are inside the video or outside the video 13:14:28 janina: Some video containers may be able to include these assets, may need to investigate 13:15:38 Raja: There are differences in the way these assets are stored...whether it is streamed or a recording 13:16:42 janina: We need to be clear that we need something more than just the verbal steam 13:17:03 Links from Raja: https://www.w3.org/TR/webvtt1/ 13:17:15 https://www.youtube.com/watch?v=NLfs-SUEerY 13:17:30 https://ableplayer.github.io/ableplayer/ 13:18:08 janina: Finding what the Metraska (sp?) spec is and what it supports 13:18:34 janina: Also MP4 13:18:46 Raja: will look into this 13:19:05 Raja: All major browsers support webvtt and to show captions or timed transcripts. A major open source web based video player supports showing both captions and timed transcripts 13:19:16 https://www.w3.org/TR/2018/REC-ttml1-20181108/ 13:19:36 janina: We discuss some of this in the MAUR 13:19:54 jasonjgw: Will look at the MAUR and we can cite that 13:20:23 jasonjgw: We can bring back next week 13:20:51 zakim, next item 13:20:51 agendum 2 -- Collaboration Tool Accessibility User Requirements. -- taken up [from jasonjgw] 13:21:15 jasonjgw: Updates? 13:22:02 https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Collaboration_Tool_Accessibility 13:22:56 https://www.w3.org/TR/ctaur/ 13:25:04 janina: So, there was some confusion on what source document to examine, and COGA was looking at the wiki rather than the FPWD 13:26:18 scott_h: Have found Microsoft collaboration documents simpler than Google docs 13:26:39 Raja_Kushalnagar has joined #rqtf 13:28:28 jasonjgw: Have noticed that Microsoft has been making major changes at high frequency, so perhaps they will be more inclined for accessibility updates in this regard 13:29:29 jasonjgw: They have integrated some automated helps on document editing, so that is something else to look at in the AI discussion 13:31:10 janina: We seem to be on the right track now on getting comments 13:32:38 janina: Expect comments in perhaps 3 weeks 13:33:42 scott_h: Have been looking more on this and have some contributions to make 13:34:48 zakim, next item 13:34:48 agendum 3 -- Miscelaneous updates and topics. -- taken up [from jasonjgw] 13:35:14 subtopic: XR and accessibility 13:35:50 jasonjgw: Need to look at the Benetech grant, but still waiting for an email response 13:36:09 subtopic: Metaverse 13:37:33 janina: Discussed in recent leadership meeting. Desire to pull together related specifications and best practices on accessibility in the metaverse 13:38:26 janina: Desire to identify anything that is at least FPWD 13:38:46 janina: Need to get this done in 2 weeks 13:40:10 jasonjgw: We have some of this in some of our documents, like SAUR and Natural Language 13:42:26 Raja: Both time and space. Time, speech and video are typical to track, but with XR one also has to track space 13:44:00 janina: Good to consider updates to these documents with XR in mind 13:45:00 jasonjgw: Can bring back Metaverse standards discussion next week 13:47:04 jasonjgw: Future of Interface workshop recordings are available. Would be good to investigate 13:47:07 https://futureofinterface.org/ 13:48:25 zakim, bye 13:48:25 leaving. As of this point the attendees have been jasonjgw, scott_h, SteveNoble, janina, John_Paton, Raja 13:48:25 Zakim has left #rqtf 13:48:28 rrsagent, make minutes 13:48:29 I have made the request to generate https://www.w3.org/2023/04/05-rqtf-minutes.html jasonjgw 13:56:51 janina has left #rqtf