18:23:40 <RRSAgent> RRSAgent has joined #a11yedge
18:23:44 <RRSAgent> logging to https://www.w3.org/2025/08/20-a11yedge-irc
18:23:44 <Zakim> RRSAgent, make logs Public
18:23:45 <Zakim> please title this meeting ("meeting: ..."), janina
18:24:09 <janina> Meeting: Accessibility at the Edge (A11yEdge) Community Group Teleconference
18:24:14 <janina> Date: 20 Aug 2025
18:24:18 <janina> Chair: Janina
18:32:03 <Lionel_Wolberger> Lionel_Wolberger has joined #a11yedge
18:32:11 <Lionel_Wolberger> present+
18:32:18 <Lionel_Wolberger> scribe+
18:32:32 <Lionel_Wolberger> rrsagent, make minutes
18:32:33 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-a11yedge-minutes.html Lionel_Wolberger
18:38:16 <janina> present+
18:38:36 <Lionel_Wolberger> Lionel_Wolberger has joined #a11yedge
18:38:44 <Lionel_Wolberger> rrsagent, make minutes
18:38:45 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-a11yedge-minutes.html Lionel_Wolberger
18:38:51 <janina> scribe+
18:39:13 <Lionel_Wolberger> present+ Chris
18:39:35 <Lionel_Wolberger> Topic: Planning the Release
18:39:41 <Lionel_Wolberger> scribe+
18:40:11 <Lionel_Wolberger> janina: We have four Wednesdays left including this meeting, prior to September 12th, which is a Friday
18:40:47 <Lionel_Wolberger> rrsagent, make minutes
18:40:49 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-a11yedge-minutes.html Lionel_Wolberger
18:41:22 <Lionel_Wolberger> janina: Today we should review the final content edits
18:41:53 <Lionel_Wolberger> ... next two Wednesdays work on our announcement texts
18:42:11 <Lionel_Wolberger> ... then a last Wednesday for finals and leftovers
18:42:51 <Lionel_Wolberger> ... handoff to W3 staff for a respec check on the 3rd (the 2nd upcoming Wednesday)
18:44:03 <Lionel_Wolberger> Topic: Overlays edit review
18:44:17 <janina> https://a11yedge.github.io/capabilities/#overlays
18:56:05 <Lionel_Wolberger> Lionel_Wolberger: More recently, the Federal Trade Commission (FTC) issued a consent decree against a vendor, referring to its product as an overlay, and addressing its advertising and claims.
18:57:14 <Lionel_Wolberger> .. documented in this document --> change to documented in this publication
18:58:40 <Lionel_Wolberger> .... We believe that the wide range of specific web accessibility  --> We don't need the 'we believe'
18:59:05 <Lionel_Wolberger> .... just capitalize the "T" -- The wide range of specific web accessibility outcomes
19:00:09 <Lionel_Wolberger> ... It is essential that vendor's marketing products and services: Add "OF" and move the apostrophe
19:00:18 <Lionel_Wolberger> ... It is essential that vendors' marketing of products and services
19:01:21 <Lionel_Wolberger> ... COULD ALSO BE It is essential that vendors who market products and services
19:07:52 <Lionel_Wolberger> janina: This sentence can be deleted entirely
19:07:53 <Lionel_Wolberger> ... Transparency regarding the extent and manner in which post-source techniques are applied is critical to ensure clarity and alignment with intended outcomes.
19:07:57 <Lionel_Wolberger> ... new paragraph:
19:08:35 <Lionel_Wolberger> ... It is essential that vendors who market products and services based on these techniques clearly communicate the scope and limitations of their post-source approach.
19:08:56 <Lionel_Wolberger> ... Forthright representation is essential for building trust.
19:09:24 <Lionel_Wolberger> ... Vendors marketing approaches such as those discussed in this document, should transparently articulate what their technologies and approaches can genuinely deliver.
19:09:28 <Lionel_Wolberger> ... The criteria of the internationally accepted WCAG Success Criteria are cross-referenced throughout this document because they remain valid whether applied in source or post-source through dynamic enhancements.
19:09:37 <Lionel_Wolberger> rrsagent, make minutes
19:09:39 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-a11yedge-minutes.html Lionel_Wolberger
19:16:41 <janina> https://a11yedge.github.io/capabilities/#manage
19:18:08 <Lionel_Wolberger> Topic: Management
19:18:13 <janina> https://a11yedge.github.io/capabilities/#manage
19:21:01 <Lionel_Wolberger> Lionel_Wolberger: edit Though to argue any remediation not done....
19:21:12 <Lionel_Wolberger> ... replace with Though to argue against any remediation not done at source or not performed by a human
19:21:39 <Lionel_Wolberger> present+ jason
19:28:41 <Lionel_Wolberger> jason: Human remediation of A-I identified checkpoints
19:28:47 <Lionel_Wolberger> ... add automation as well
19:29:05 <Lionel_Wolberger> ... Human remediation of automation, or A-I identified, checkpoints
19:30:26 <Lionel_Wolberger> Lionel_Wolberger: an an interface made --- remove an an
19:31:00 <Lionel_Wolberger> janina: This capability describes an an interface made available to authorized users within a client organization, enabling them to develop and deploy accessibility remediating code.
19:31:04 <Lionel_Wolberger> ... remove CLIENT
19:31:59 <Lionel_Wolberger> ... remove 'or of CSS'
19:32:06 <Lionel_Wolberger> ... in this sentence, A typical limitation allows edits to element-level code, but not the modification of interactive components or of CSS.
19:33:28 <Lionel_Wolberger> Lionel_Wolberger: Delete this sentence, 'Note the assumption is that, for whatever reason, the content technology provided by the hosting environment lacks adequate accessibility support. '
19:34:06 <Lionel_Wolberger> ... express it's --- remove apostrophe express its
19:35:20 <Lionel_Wolberger> ... delete the central sentence, it makes the same point twice
19:35:22 <Lionel_Wolberger> ... The original content creator is most likely to understand the contextual nuances needed to most usefully and accurately express those nuances through accessibility capabilities such as alternative text or semantic structure.
19:36:00 <Lionel_Wolberger> ... in this sentence 'Post-source interfaces can facilitate the addition of missing accessibility markup to content'
19:36:08 <Lionel_Wolberger> ... delete the tail end, 'to content'
19:40:09 <Lionel_Wolberger> ... shorten this sentence This will frequently lead to both inaccessible content and core interactions issues
19:40:22 <Lionel_Wolberger> ... delete core interactions issues, just keep inaccessible content
19:40:57 <Lionel_Wolberger> ... double comma Sometimes,, t
19:41:53 <Lionel_Wolberger> ... authentication or invoicing --- change to authentication or payment processing
19:45:35 <Lionel_Wolberger> janina: Delete this sentence, These experts can provide scalable remediation spanning multiple layers of the site, including dynamic components and interface behaviors.
19:46:04 <Lionel_Wolberger> jason: back to 5.2
19:46:19 <Lionel_Wolberger> ... change This capability describes an an interface ... to read, This capability describes an an interface or framework
19:47:21 <Lionel_Wolberger> ... any company can build a framework like UserWay and AudioEye have built
19:48:03 <Lionel_Wolberger> ... adding framework, means we remove limitations
19:48:09 <Lionel_Wolberger> ... and any mention of low code
19:49:32 <Lionel_Wolberger> Topic: In dash source
19:50:02 <Lionel_Wolberger> Lionel_Wolberger: clarity & parallelism: Hyphenating in-source clearly pairs with post-source as defined terms, reducing ambiguity.  
19:50:18 <Lionel_Wolberger> ... 	and Disambiguation: It avoids confusion with the verb insource and with the plain prepositional phrase “in the source (code).”
19:51:25 <Lionel_Wolberger> ... The draft alternates between in-source and in source when contrasted with post-source -- so watch carefully to avoid blurring function and breaking parallelism.
19:53:34 <Lionel_Wolberger> Topic: Post source and Overlay subtletiese
19:53:44 <Lionel_Wolberger> Chris: Can we tease out the relationship of these terms
19:53:55 <Lionel_Wolberger> ... which is the umbrella term, and which is a more specific instance
19:54:32 <Lionel_Wolberger> Lionel_Wolberger: I think post-source is the umbrella term
19:55:26 <Lionel_Wolberger> Chris: It resembles to my mind the the overlap and distinctions between terms like dementia and alzheimers
19:55:49 <Lionel_Wolberger> ... the terms are blended by the general public, but experts understand their differencees
19:56:12 <Lionel_Wolberger> ... in the publicizing of this document, some people will more readily embrace that the document is about overlays, top to bottom
19:56:54 <Lionel_Wolberger> ... publication will face these differences in the audience understanding, perception and bias
19:57:04 <Lionel_Wolberger> zakim, end meeting
19:57:04 <Zakim> As of this point the attendees have been Lionel_Wolberger, janina, Chris, jason
19:57:06 <Zakim> RRSAgent, please draft minutes
19:57:07 <RRSAgent> I have made the request to generate https://www.w3.org/2025/08/20-a11yedge-minutes.html Zakim
19:57:13 <Zakim> I am happy to have been of service, Lionel_Wolberger; please remember to excuse RRSAgent.  Goodbye
19:57:13 <Zakim> Zakim has left #a11yedge