12:03:35 RRSAgent has joined #rqtf 12:03:39 logging to https://www.w3.org/2023/07/05-rqtf-irc 12:03:40 RRSAgent, make logs Public 12:03:41 please title this meeting ("meeting: ..."), jasonjgw_ 12:03:45 present+ 12:03:47 chair: jasonjgw 12:03:50 scribe+ 12:03:52 agenda+ Collaboration Tools Accessibility User Requirements. 12:03:52 agenda+ Media accessibility: issue identification. 12:03:52 agenda+ Miscellaneous updates and topics. 12:57:32 scott_h has joined #rqtf 12:57:53 present+ 13:01:02 SteveNoble has joined #rqtf 13:01:13 present+ 13:02:06 scribe: SteveNoble 13:02:09 zakim, next item 13:02:09 agendum 1 -- Collaboration Tools Accessibility User Requirements. -- taken up [from jasonjgw_] 13:03:57 subtopic: WebEdit Working Group 13:03:57 janina_ has joined #rqtf 13:04:01 present+ 13:04:09 https://github.com/w3c/strategy/issues/417 13:05:41 jasonjgw_: Basically clarifies APIs associated with ContentEditable 13:06:14 jasonjgw_: Which allows users to edit content in the browser 13:06:38 jasonjgw_: Includes clipboard and events support 13:06:59 jasonjgw_: Some connection to a highlighting API 13:07:10 jasonjgw_: Non-text editing is out of scope 13:08:19 janina_: CTAUR has a broader scope, but curious to know if ContentEditable is used in such things as Google Docs 13:09:08 jasonjgw_: Unclear...Google may use proprietary techniques 13:09:35 jasonjgw_: Charter does not include ARIA as a dependency 13:15:07 scott_h: There could be some potential impacts on our document work if editable text is using spec-based techniques rather than all proprietary interactions 13:15:54 janina_: APA monitors charters, which is why this is coming up now 13:16:31 jasonjgw_: Agree with Scott's point 13:18:12 jasonjgw_: Editing support sometimes use JavaScript libraries which may not be supported in assistive technology through standard means 13:19:07 jasonjgw_: They mention WCAG in the charter, but not ARIA, which could be problematic 13:20:02 janina_: Seems like we have a good understanding at this point 13:21:06 scott_h: May explain why Google Docs has problems with AT, but Office online seems to provide a better level of access 13:23:35 jasonjgw_: Will continue CTAUR work next week 13:27:44 zakim, next item 13:27:44 agendum 2 -- Media accessibility: issue identification. -- taken up [from jasonjgw_] 13:28:17 janina_: Has MAUR repository been raeted? 13:28:44 jasonjgw_: Yes...all ready to begin work 13:29:02 jasonjgw_: No issues added yet, but everything is ready 13:29:59 jasonjgw_: Should have more to discuss next week 13:30:45 janina_: The document goes back to 2013, so is long past due a refresh 13:32:08 janina_: The interlinear use case was brought up in this doc, but no issues were raised back then 13:32:59 jasonjgw_: If it is something else other than just text, then it likely fits 13:34:49 janina_: Good place now to look at standardizing some of these interactions 13:35:48 jasonjgw_: Repository is ready, so we are good to go on starting work 13:38:12 zakim, next item 13:38:12 agendum 3 -- Miscellaneous updates and topics. -- taken up [from jasonjgw_] 13:39:02 jasonjgw_: Not sure if anything is going to dicsuss today 13:39:39 jasonjgw_: A lot going on with AI these days 13:41:12 jasonjgw_: Predict a lot of automated transformation for cognitive accessibility in future 13:41:45 janina_: Similar to what has happened with automated captions 13:42:14 jasonjgw_: Will have to deal with this at some point 13:44:36 zakim, end meeting 13:44:36 As of this point the attendees have been jasonjgw_, scott_h, SteveNoble, janina_ 13:44:38 RRSAgent, please draft minutes 13:44:40 I have made the request to generate https://www.w3.org/2023/07/05-rqtf-minutes.html Zakim 13:44:48 I am happy to have been of service, jasonjgw_; please remember to excuse RRSAgent. Goodbye 13:44:48 Zakim has left #rqtf 13:48:09 janina_ has left #rqtf