18:14:11 <RRSAgent> RRSAgent has joined #a11yedge
18:14:15 <RRSAgent> logging to https://www.w3.org/2025/09/03-a11yedge-irc
18:14:15 <Zakim> RRSAgent, make logs Public
18:14:16 <Zakim> please title this meeting ("meeting: ..."), janina
18:14:43 <janina> Meeting: Accessibility at the Edge (A11yEdge) Community Group Teleconference
18:14:48 <janina> Chair: Janina
18:14:56 <janina> Date: 03 Sep 2025
18:24:22 <janina> ~.
18:24:50 <janina> 
18:25:06 <janina> janina has left #a11yedge
18:25:12 <janina> janina has joined #a11yedge
18:25:27 <janina> zakim, who's here?
18:25:27 <Zakim> Present: (no one)
18:25:29 <Zakim> On IRC I see janina, RRSAgent, Zakim
18:26:02 <janina> Meeting: Accessibility at the Edge (A11yEdge) Community Group Teleconference
18:26:19 <janina> Date: 03 Sep 2025
18:26:25 <janina> Chair: Janina
18:26:48 <janina> ?
18:35:25 <janina> janina has left #a11yedge
18:35:36 <janina> janina has joined #a11yedge
18:35:39 <janina> present+
18:36:39 <Lionel_Wolberger> Lionel_Wolberger has joined #a11yedge
18:36:52 <Lionel_Wolberger> present+
18:36:55 <Lionel_Wolberger> scribe+
18:39:40 <Lionel_Wolberger> present+ chris
18:39:44 <Lionel_Wolberger> present+ jason
18:39:50 <janina> zakim, who's here?
18:39:50 <Zakim> Present: janina, Lionel_Wolberger, chris, jason
18:39:52 <Zakim> On IRC I see Lionel_Wolberger, janina, RRSAgent, Zakim
18:40:12 <Lionel_Wolberger> Topic: Timelines
18:47:44 <Lionel_Wolberger> jason: What date is the document done? We will always find more tweaks
18:48:23 <Lionel_Wolberger> Lionel_Wolberger: If we want to discuss it at a TPAC breakout, that will be November 10th-ish
18:52:39 <Lionel_Wolberger> jason: I feel we need another session with Mike, then we can close
18:53:01 <Lionel_Wolberger> Lionel_Wolberger: 1 or 2 more sessions like that, then we can close
18:53:27 <Lionel_Wolberger> ... we were targeting 12 September
18:54:26 <Lionel_Wolberger> janina: A month in advance of TPAC is enough time
18:55:26 <Lionel_Wolberger> ... the Glossary is a heavy lift and still needs to be done
18:58:24 <Lionel_Wolberger> Chris: AI should save time for us in generating the glossary,.it can suggest entries
18:58:49 <Lionel_Wolberger> janina: W3C has strict approaches to Glossary, and requires a specific syntax
18:59:09 <Lionel_Wolberger> ... then the appropriate respec markup in the document
19:18:07 <Lionel_Wolberger> Lionel_Wolberger: I prepared a document to draft the announcement letters and will share it when ready
19:18:10 <Lionel_Wolberger> Topic: Glossary
19:18:27 <Lionel_Wolberger> janina: The Terms list was helpful in the Captcha report, https://www.w3.org/TR/turingtest/#terms
19:18:36 <Lionel_Wolberger> ... that was a good example of terms that needed definition
19:19:53 <janina> execution of code injected real-time by the user agent or in the content delivery pipeline. See also <a href="#is">In-Source</a>
19:20:23 <janina> sz w3c
19:20:34 <janina> 
19:20:58 <janina> janina has left #a11yedge
19:21:04 <janina> janina has joined #a11yedge
19:21:10 <janina> execution of code injected real-time by the user agent or in the content delivery pipeline. See also <a href="#is">In-Source</a>
19:21:28 <janina> User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
19:21:39 <janina> janina has left #a11yedge
19:21:45 <janina> janina has joined #a11yedge
19:21:47 <janina> User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
19:22:29 <Lionel_Wolberger> Lionel_Wolberger: The terms that stand out needed definition:
19:22:39 <Lionel_Wolberger> ... post-source and in-source
19:23:28 <Lionel_Wolberger> janina: I need to markup one term, to verify the respec markup needed and how it will function
19:25:36 <Lionel_Wolberger> ... Post-source: execution of code injected real-time by the user agent or in the content delivery pipeline. See also <a href="#is">In-Source</a>
19:25:53 <Lionel_Wolberger> ... In-source: User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
20:24:22 <Lionel_Wolberger> Lionel_Wolberger: Source. The authored, version-controlled codebase intended for publishing.
20:24:43 <Lionel_Wolberger> ... In-Source: Accessibility improvements authored directly in the source.
20:25:36 <Lionel_Wolberger> ... Post-Source: Accessibility improvements are applied after the source is published, by JS code gathered from sources other than the content publisher
20:26:03 <Lionel_Wolberger> ... Source. The authored, version-controlled codebase intended for publishing by the content manager
20:26:51 <Lionel_Wolberger> CHris: We need to talk about performance as well
20:27:04 <Lionel_Wolberger> janina: There is a W3C Sustainability Task Force
20:27:48 <Lionel_Wolberger> Lionel_Wolberger: We need to address, that HTML is preferred as properly coded HTML inherits decades of fore thought
20:28:06 <Lionel_Wolberger> ... that ensures that the huge diversity of downstream userscan enjoy an accessible experience
20:28:36 <Lionel_Wolberger> s/userscan/users can
20:28:42 <Lionel_Wolberger> rrsagent, make minutes
20:28:44 <RRSAgent> I have made the request to generate https://www.w3.org/2025/09/03-a11yedge-minutes.html Lionel_Wolberger
20:32:35 <Lionel_Wolberger> Lionel_Wolberger: “In-source” means the accessibility fix or enhancement is built into the original codebase. It is part of the development process—documented, testable, and reviewed like any other feature or bug fix. It is shipped as part of the published experience.
20:33:37 <Lionel_Wolberger> ... Source includes HTML, CSS, JavaScript, and other assets maintained by the content owner or publisher. “Source” typically lives in a repository and reflects the canonical intent of the site or app, shaped by teams with design, development, and QA oversight.
20:33:49 <Lionel_Wolberger> ... “Post-source” changes are not authored in the canonical codebase. Instead, they are layered on top of the delivered content—typically via external scripts, services, or browser extensions. These changes occur dynamically in the user agent, often without full developer involvement or visibility.
20:42:25 <Lionel_Wolberger> janina: We are unpacking the black box of the URL
20:43:02 <Lionel_Wolberger> ... the URL provides HTML, CSS, and JS which the user-agent, in runtime, constucts a DOM and accessibility tree (AT)
20:43:48 <Lionel_Wolberger> ... we are unpacking that black box into Source, Source-authorized post-source, and User-authorized post-source
20:44:16 <Lionel_Wolberger> ... by definition, the user cannot add source-authorized, or source, changes
20:44:44 <Lionel_Wolberger> Lionel_Wolberger: That's why we may not need in hyphen source
20:45:22 <Lionel_Wolberger> rrsagent, make minutes
20:45:23 <RRSAgent> I have made the request to generate https://www.w3.org/2025/09/03-a11yedge-minutes.html Lionel_Wolberger
20:45:41 <Lionel_Wolberger> zakim, end meeting
20:45:41 <Zakim> As of this point the attendees have been janina, Lionel_Wolberger, chris, jason
20:45:43 <Zakim> RRSAgent, please draft minutes
20:45:45 <RRSAgent> I have made the request to generate https://www.w3.org/2025/09/03-a11yedge-minutes.html Zakim
20:45:50 <Zakim> I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent.  Goodbye
20:45:51 <Zakim> Zakim has left #a11yedge