Meeting minutes
<janina> ~.
<janina>
<janina> ?
Timelines
jason: What date is the document done? We will always find more tweaks
Lionel_Wolberger: If we want to discuss it at a TPAC breakout, that will be November 10th-ish
jason: I feel we need another session with Mike, then we can close
Lionel_Wolberger: 1 or 2 more sessions like that, then we can close
… we were targeting 12 September
janina: A month in advance of TPAC is enough time
… the Glossary is a heavy lift and still needs to be done
Chris: AI should save time for us in generating the glossary,.it can suggest entries
janina: W3C has strict approaches to Glossary, and requires a specific syntax
… then the appropriate respec markup in the document
Lionel_Wolberger: I prepared a document to draft the announcement letters and will share it when ready
Glossary
janina: The Terms list was helpful in the Captcha report, https://
… that was a good example of terms that needed definition
<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>
<janina> sz w3c
<janina>
<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>
<janina> User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
<janina> User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
Lionel_Wolberger: The terms that stand out needed definition:
… post-source and in-source
janina: I need to markup one term, to verify the respec markup needed and how it will function
… 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>
… In-source: User agent execution of code present in published content. See also <a href="#ps">Post-Source</a>
Lionel_Wolberger: Source. The authored, version-controlled codebase intended for publishing.
… In-Source: Accessibility improvements authored directly in the source.
… Post-Source: Accessibility improvements are applied after the source is published, by JS code gathered from sources other than the content publisher
… Source. The authored, version-controlled codebase intended for publishing by the content manager
CHris: We need to talk about performance as well
janina: There is a W3C Sustainability Task Force
Lionel_Wolberger: We need to address, that HTML is preferred as properly coded HTML inherits decades of fore thought
… that ensures that the huge diversity of downstream users can enjoy an accessible experience
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.
… 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.
… “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.
janina: We are unpacking the black box of the URL
… the URL provides HTML, CSS, and JS which the user-agent, in runtime, constucts a DOM and accessibility tree (AT)
… we are unpacking that black box into Source, Source-authorized post-source, and User-authorized post-source
… by definition, the user cannot add source-authorized, or source, changes
Lionel_Wolberger: That's why we may not need in hyphen source