18:20:31 RRSAgent has joined #a11yedge 18:20:35 logging to https://www.w3.org/2024/05/22-a11yedge-irc 18:20:35 RRSAgent, make logs Public 18:20:36 please title this meeting ("meeting: ..."), janina 18:20:50 Meeting: Accessibility at the Edge Community Group Teleconference 18:20:57 Date: 22 May 2024 18:21:01 Chair: Janina 18:21:17 agenda+Welcome & Introductions (As needed) 18:21:36 agenda+Capabilities Development: Remaining Automatabilities 18:21:44 agenda+Next Steps and Actions 18:21:49 agenda+Be done 18:30:44 regrets: Chris_Novell 18:30:49 present+ 18:30:59 scribe+ 18:35:38 Lionel_Wolberger has joined #a11yedge 18:35:44 present+ 18:35:47 agenda? 18:43:26 Topic: Consistency 18:43:34 present+ Jason 18:44:11 Jason: This item, "Having Sufficient Knowledge & Skills" seems inconsistent with the others, in fact it does not sound like a capability 18:44:33 .. the whole management area might need a different handling 18:44:36 +1 18:45:08 janina: One job at a time. Let's complete the 'automatability' pass then discuss restructuring. 18:49:08 janina: "Only The Edge Knows For Sure" is talking about the business side and is "do not apply" 18:49:27 Lionel_Wolberger: We have expanded the Automatability options to include "does not apply", or DNA 18:54:23 jason: We cut and pasted the same categories across all headings, but they apply very poorly in this "management" area 18:54:57 ... we likely will not need to have 'Source' in this section as well 18:55:28 janina: These items go to the heart of the edge debate, or the viability of "not-at-source" accessibility solutions 18:56:08 jason: The dimensions of Source, Trade-offs, Benefit, Automatability just do not apply in this section. 18:57:33 janina: Can you make a business process decision to rely on automatability as a viable accessibility solution for some sites? 19:03:24 Topic: DNA abbreviation 19:03:31 janina: DNA stands for "does not apply" 19:11:48 Topic: Accessibility Editing, By Site Owner 19:11:52 Lionel_Wolberger: DNA 19:17:21 Topic: Accessibility Statement Discoverability 19:19:46 WAI-Adapt there is a specification in development called Well Known Destinations 19:20:00 Lionel_Wolberger: In WAI-Adapt there is a specification in development called Well Known Destinations 19:20:21 ... this will enable the consistent discovery of an accessibility statement 19:20:33 ... and hols the promise of making those statements machine readable in the future 19:21:04 jason: But this item, "Accessibility Statement Availability" is about accessibility statement generation 19:21:24 janina: The idea is that we take common destinations, like an accessibility statement, and make them discoverable 19:24:19 jason: I do think you can generate an accessibility statement automatically. It might not include everything, but you could. 19:25:54 Lionel_Wolberger: I agree, many cogent parts of such a statement can be automatically generated 19:26:55 jason: You need permission to create it, but it could be hosted anywhere 19:27:11 ... but the discoverable 'well known destination' would need to be configured by Amazon 19:31:54 Topic: Next meeting agenda 19:32:12 jason: If a new member joins, we should start at the concept of a11y at the edge, or post-source 19:32:16 janina: +1 19:32:19 Lionel_Wolberger: +1 19:32:25 rrsagent, make minutes 19:32:26 I have made the request to generate https://www.w3.org/2024/05/22-a11yedge-minutes.html Lionel_Wolberger 19:33:03 zakim, end meeting 19:33:03 As of this point the attendees have been janina, Lionel_Wolberger, Jason 19:33:05 RRSAgent, please draft minutes 19:33:06 I have made the request to generate https://www.w3.org/2024/05/22-a11yedge-minutes.html Zakim 19:33:11 I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent. Goodbye 19:33:12 Zakim has left #a11yedge