18:24:29 RRSAgent has joined #a11yedge 18:24:33 logging to https://www.w3.org/2024/09/11-a11yedge-irc 18:24:33 RRSAgent, make logs Public 18:24:34 please title this meeting ("meeting: ..."), janina 18:24:48 Meeting: Accessibility at the Edge Community Group Teleconference 18:24:55 ate: 11 Sep 2024 18:25:00 Chair: Janina 18:25:16 agenda+ Welcome & Introductions (As needed) 18:25:26 agenda+ Whither Capabilities? 18:32:21 Lionel_Wolberger has joined #a11yedge 18:32:29 present+ 18:32:33 agenda? 18:32:42 scribe+ 18:33:44 present+ 18:33:55 scribe+ 18:34:00 present+ Jason 18:34:08 present+ Shari 18:34:15 present+ Mike 18:34:21 zakim, who is here? 18:34:21 Present: Lionel_Wolberger, janina, Jason, Shari, Mike 18:34:23 On IRC I see Lionel_Wolberger, RRSAgent, Zakim, janina, Daniel 18:36:28 janina: Proposing we meet next week 18 Sept, then take off 25 Sept and week following 18:36:31 ... due to TPAC 18:37:22 Lionel_Wolberger: 2 Oct is Rosh Hashanna 18:37:53 Lionel_Wolberger: The group agrees. 18:38:03 zakim, next item 18:38:03 agendum 1 -- Welcome & Introductions (As needed) -- taken up [from janina] 18:38:07 zakim, close this item 18:38:07 agendum 1 closed 18:38:08 I see 1 item remaining on the agenda: 18:38:08 2. Whither Capabilities? [from janina] 18:38:14 zakim, next item 18:38:14 agendum 2 -- Whither Capabilities? -- taken up [from janina] 18:39:21 janina: Frames the issue of how to get the most value out of this document as it stands now. 18:40:14 ... propose re-titling the document 18:40:23 ... Jason has been proposing that for a long time 18:40:33 ... after re-titling, we re-write the abstract 18:40:49 ... this document examines the opportunities to refine accessibility after the source is committed 18:41:17 ... this is the minimum 18:43:06 Mike: I suggest we put a time limit or deadline as well 18:43:08 +1 18:44:12 Lionel: Proposing titles 18:44:15 ... ... Post-Source Accessibility Capabilities 18:45:09 Mike: Who is the audience? 18:45:45 ... let's brainstorm here, as I'd like time to consider 18:46:03 janina: Let's get a provisional title 18:46:17 jason: Post-source accesibility techniques and capabilities 18:46:44 Mike: Post-Source Accessibility 18:47:09 Mike: What is 'source'? 18:47:30 Lionel: The group continued to brainstorm. Post Source Code Accessibility 18:48:11 ... post production accessibility 18:49:05 janina: 9 am Thursday 26 September we are getting an overview of what is coming in WCAG 3 18:49:26 Shari: Invite me too 18:50:50 Lionel_Wolberger: Accessibility capabilities post-source code or content 18:52:16 Jason: AS long it includes browsers 18:52:29 ... something is live. How to we further improve something once it is live 18:52:40 ... could be browser manufacturers, AT, etc 18:53:04 janina: there could be a sub-title 18:53:37 Lionel_Wolberger: "Improving" in the subtitle 18:54:07 Lionel_Wolberger: Accessibility capabilities, post-source code or content 18:54:39 Mike: +1 18:54:42 +1 18:54:44 Jason: +1 18:54:50 Shari: +1 19:01:48 Topic: TPAC 19:01:51 janina: https://www.w3.org/2024/09/TPAC/registration.html 19:01:57 rrsagent, make minutes 19:01:59 I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger 19:02:55 Topic: Next edits 19:03:10 Jason: We need a new abstract 19:08:16 Jason: Let's re-examine the recurring subheadings (the current definition list) 19:08:35 ... Source, Trade-offs, Benefit, Automatability 19:08:55 Lionel_Wolberger: Perhaps we can combine the first three into one subheading, Considerations 19:09:31 janina: There are recurring themes 19:09:47 ... such as a portable configuration that a user takes to every website 19:09:54 ... this requires being done in post-source 19:14:57 jason: Most things are likely best, when done at source 19:15:11 ... but there are often compelling commercial reasons to do it post-source 19:15:28 ... and often there is minimal to no downside 19:16:09 ... The document is a guide to how you can do things post-source 19:16:23 ... and should show the potential pitfalls 19:16:55 ... as for example, when post-source code hinges on source code (where the source developer does not know there are downstream code ) 19:17:26 ... and if the source developer makes a change, it will essentially turn off the post-source code 19:18:06 ... so there is a level of collaboration with the people who manage the source code that is required 19:18:20 ... for much of these post-source fixes to be robust 19:27:00 janina: Clarifying that the audience is W3C brings new nuances to the fore 19:32:43 rrsagent, make minutes 19:32:45 I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger 19:35:37 janina: Can we go with Accessibility capabilities, post-source code and content 19:35:50 Shari: +1 19:35:53 Jason: +1 19:35:57 Lionel_Wolberger: +1 19:36:03 rrsagent, make minutes 19:36:05 I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Lionel_Wolberger 19:36:25 zakim, end meeting 19:36:25 As of this point the attendees have been Lionel_Wolberger, janina, Jason, Shari, Mike 19:36:27 RRSAgent, please draft minutes 19:36:28 I have made the request to generate https://www.w3.org/2024/09/11-a11yedge-minutes.html Zakim 19:36:33 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 19:36:35 Zakim has left #a11yedge