18:17:16 RRSAgent has joined #a11yedge 18:17:20 logging to https://www.w3.org/2024/05/29-a11yedge-irc 18:17:20 RRSAgent, make logs Public 18:17:21 please title this meeting ("meeting: ..."), janina 18:17:30 Meeting: Accessibility at the Edge Community Group Teleconference 18:17:42 Date: 29 May 2024 18:17:47 Chair: Janina 18:18:02 agenda+Welcome & Introductions (As needed) 18:18:43 agenda+CG Overview: Where we are, and what we're developing 18:19:08 agenda+Capabilities Development (Continued) 18:19:16 agenda+Actions and Next Steps 18:19:25 agenda+Be Done 18:30:07 Lionel_Wolberger has joined #a11yedge 18:31:08 agenda? 18:36:17 present+ 18:36:22 present+ 18:36:24 scribe+ 18:36:27 present+ Jason 18:41:00 zakim, next item 18:41:00 agendum 1 -- Welcome & Introductions (As needed) -- taken up [from janina] 18:41:12 Lionel_Wolberger: We have received regrets. 18:41:24 zakim, close this item 18:41:24 agendum 1 closed 18:41:25 I see 4 items remaining on the agenda; the next one is 18:41:25 2. CG Overview: Where we are, and what we're developing [from janina] 18:41:33 Topic: Automatability 18:41:44 janina: I cleaned up the document 18:42:39 https://lists.w3.org/Archives/Public/public-a11yedge/2024May/0011.html 18:42:52 ... for details see link, https://lists.w3.org/Archives/Public/public-a11yedge/2024May/0011.html 18:43:30 janina: We resume 'automatabilities' from the heading, Accessibility Provider Identification 18:44:38 Lionel_Wolberger: Accessibility Issue Reporting is really about Accessibility Issue Reportability, is it possible to report Accessibility issues 18:45:53 janina: We expect to have a specification at some point specifying a well known destination for reporting accessibility issues 18:49:54 Lionel_Wolberger: automation can help create the trouble ticket as well. 18:50:16 jason: I can think of many situations where automation would be quite challenging 19:05:14 https://w3c.github.io/ctaur/ 19:10:09 jason: I'd like to clarify what we mean by automatability 19:10:21 ... we are assuming that we cannot change what people are doing right now 19:11:16 ... we are not assuming that given, if websites and their managers did so-and-so, then we would be automatable 19:11:44 ... instead, we are looking at how technologies can change user outcomes in the current environment and scenarios 19:12:10 ... I was thinking, how could this be useful outside of the community of people who do accessibility 19:12:33 ... imagine coming to a CMS provider and saying, here are things that you can do in your CMS to help your users 19:12:55 ... this is not about debating whether overlays are making false claims or not 19:13:12 ... this is about CMSs and entitites that makes thousands of websites, how they can improve their user outcomes 19:13:21 ... this focus can set us up for a bigger goal 19:13:32 ... browsers can do a better job, CMSs can do a better job 19:20:06 janina: We labeled each item. Good work team! 19:20:21 Topic: Next steps 19:21:09 janina: I will find that orphaned H1 after the Appendix 19:21:32 jason: Propose we discuss the big picture question next time 19:23:10 ... I propose post-source 19:23:34 ... 'Accessibility at the Edge' encompasses the technologies that we might agree are post-source 19:23:51 ... I have made a list of those technologies; you might add more 19:24:11 janina: Getting back to my actions, I will check the nesting 19:24:52 ... for next time, we either have the high level discussion, or go through the H2s and think about organization 19:29:25 jason: I'm on board H2s 19:31:56 zakim, end meeting 19:31:56 As of this point the attendees have been Lionel_Wolberger, janina, Jason 19:31:58 RRSAgent, please draft minutes 19:32:00 I have made the request to generate https://www.w3.org/2024/05/29-a11yedge-minutes.html Zakim 19:32:07 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 19:32:07 Zakim has left #a11yedge