12:15:26 RRSAgent has joined #rqtf 12:15:30 logging to https://www.w3.org/2023/05/24-rqtf-irc 12:15:30 RRSAgent, make logs public 12:15:31 Zakim has joined #rqtf 12:15:31 Meeting: Accessible Platform Architectures Working Group Teleconference 12:15:31 Date: 24 May 2023 12:15:40 chair: jasonjgw 12:15:44 scribe+ 12:15:46 present+ 12:16:06 agenda+ New Zoom meeting arrangements continued). 12:16:06 agenda+ Collaboration Tools Accessibility User Requirements. 12:16:06 agenda+ Media Accessibility User Requirements. 12:16:07 agenda+ Miscellaneous updates and topics. 12:59:45 SteveNoble has joined #rqtf 13:00:31 I'm getting an error message from Zoom claiming the meeting ID is invalid. I'm joining directly from the W3C meeting page. 13:00:49 present+ 13:02:29 scott_h has joined #rqtf 13:03:33 present+ 13:04:05 kirkwood has joined #rqtf 13:05:09 Roy has joined #rqtf 13:05:52 zakim, next item 13:05:52 agendum 1 -- New Zoom meeting arrangements continued). -- taken up [from jasonjgw] 13:07:18 kirkwood has joined #rqtf 13:07:35 ghurlbot has joined #rqtf 13:07:39 janina has joined #rqtf 13:07:52 present+ 13:07:58 Raja_Kushalnagar has joined #rqtf 13:10:44 Janina: zoom settings for sign language interpreters are in the administrator settings 13:11:42 Interpreter: there are some issues with window spotlighting 13:12:25 Interpreter: when the popout ASL view is used, the interpreter is muted, which is not good 13:12:46 kirkwood has joined #rqtf 13:13:32 janina: We should use our experience with this new technology to update some of our documents 13:13:59 janina: May take a few weeks to identify all the issues we want to address 13:14:53 janina: Does Raja have any observations? 13:15:33 Raja_Kushalnagar: In some ways the new techniques are an improvement 13:16:01 Raja_Kushalnagar: The speaker detection is good 13:16:02 kirkwood has joined #rqtf 13:16:53 Raja_Kushalnagar: The interpreter detection is not well implemented yet...it does not work with accuracy 13:17:03 zakim, next item 13:17:03 agendum 2 -- Collaboration Tools Accessibility User Requirements. -- taken up [from jasonjgw] 13:19:46 SteveNoble: clarification? are we using the new technique or the old? 13:19:49 Roy: Using the old way on this call 13:20:29 scott_h: Some updates have been made 13:20:50 scott_h: Made it more generalized, less screen-reader specific 13:22:07 scott_h: Some technologies have an "accessibility mode" - but there are concerns that accessibility should be baked in, not require someone make a setting change 13:23:00 jasonjgw: Glad to hear we are making progress 13:23:31 jasonjgw: After Janina looks at it, we can discuss how to incorporate it into teh text 13:24:03 jasonjgw: But wondering if implementation-specific issues are in-scope 13:24:20 jasonjgw: We may need to think about that as part of the process 13:24:51 scott_h: Sounds good...we also want to sort out WCAG and ATAG connections 13:25:14 jasonjgw: Bring back next week? 13:25:42 janina: Next week should be good 13:26:12 janina: Concerning overlay technologies... 13:26:20 A11yEdge Possible Approach here: https://a11yedge.github.io/capabilities/#commandconversion 13:26:46 janina: Would love to have some feedback on this 13:27:57 janina: some details around remapping 13:28:43 scott_h: Sounds good...will read this 13:29:28 jasonjgw: Not sure why proprietary platforms are recasting functionality that is already available in standards-based technologies 13:30:12 jasonjgw: Bring back next week? 13:30:22 scott_h: Yes...sounds good 13:31:33 jasonjgw: Notice that screen-reader bleed-through is occurring in this meeting 13:32:03 jasonjgw: This is new behavior -- sorry about that 13:32:05 zakim, next item 13:32:05 agendum 3 -- Media Accessibility User Requirements. -- taken up [from jasonjgw] 13:32:50 jasonjgw: Section 2.5 discussion of media objects 13:33:40 jasonjgw: But could use an update 13:34:11 jasonjgw: Something like locating specific navigation points in media was not discussed 13:34:36 jasonjgw: Also, did not notice things like flash mitigation and color re-mapping 13:35:23 janina: Flash mitigation and color contrast we did not mention, because those were already in WCAG 13:36:03 janina: That publication was essentially frozen since 2013 13:36:17 janina: So, lots of updates will be needed 13:36:49 janina: There are also new technologies in development now being discussed by APA 13:37:54 janina: Same is true for EPUB....they are in a position to look at new possibilities such as interlinear translations 13:39:08 janina: Hope to be meeting with a number of groups during TPAC, so we can bring those discussions to bear 13:40:20 janina: The media accessibility requirements work was much easier when we focused on user needs, as opposed to tool requirements 13:41:57 jasonjgw: Some questions on where requirements need to be: authoring, vs. user agent vs. assistive technology requirements 13:42:38 janina: Some issues, like flash mitigation, are life-concerning 13:42:50 jasonjgw: Realize that 13:44:45 janina: Speech recognition: engineers love to emphasize the capabilities of automated captions, but having a script makes that even better 13:45:19 jasonjgw: One revision would be move away from simply HTML requirements to more global on media 13:45:55 Raja_Kushalnagar: It empowers the user to use these automated tools, but there is also a role for the content craeteors 13:46:35 Raja_Kushalnagar: The speaker's intent and the listeners interpretation is not always identical 13:47:17 Raja_Kushalnagar: ASR often does good with text identification, but not the speaker's intent 13:48:21 Raja_Kushalnagar: Matching what the speaker intends and the listener receives needs to be closer 13:49:22 Raja_Kushalnagar: Also, the speaker intent could help inform the generator 13:50:16 janina: There is also the spoken presentation task force which is working on automated speech output 13:50:55 jasonjgw: Not sure if we still have an active github repository to begin opening issues 13:51:29 jasonjgw: Will look into this and email the list 13:51:38 zakim, next item 13:51:38 agendum 4 -- Miscellaneous updates and topics. -- taken up [from jasonjgw] 13:51:52 ghurlbot, use w3c/rqtf 13:51:52 Roy, OK. 13:53:13 janina: New Tooling is being developed to handle repository tracking 13:53:43 janina: This will help focus on just RQTF documents 13:54:21 action: Roy to test ghurlbot for this channel 13:54:28 Created ACTION-2342 - Test ghurlbot for this channel [on Ruoxi Ran - due 2023-05-31]. 13:54:28 I created -> issue #2 https://github.com/w3c/rqtf/issues/2 13:54:28 but I could not add the "action" label. 13:54:28 That probably means I don't have push permission on w3c/rqtf. 13:54:30 janina: We will be able to create schemas to help 13:54:50 scott_h: Sounds great! 13:56:00 zakim, end meeting 13:56:00 As of this point the attendees have been jasonjgw, SteveNoble, scott_h, janina 13:56:02 RRSAgent, please draft minutes 13:56:04 I have made the request to generate https://www.w3.org/2023/05/24-rqtf-minutes.html Zakim 13:56:11 I am happy to have been of service, jasonjgw; please remember to excuse RRSAgent. Goodbye 13:56:11 Zakim has left #rqtf 14:02:20 janina has left #rqtf