W3C

– DRAFT –
Accessibility at the Edge (A11yEdge) Community Group Teleconference

20 Aug 2025

Attendees

Present
Chris, janina, jason, Lionel_Wolberger
Regrets
-
Chair
Janina
Scribe
Lionel_Wolberger, janina

Meeting minutes

Planning the Release

janina: We have four Wednesdays left including this meeting, prior to September 12th, which is a Friday

janina: Today we should review the final content edits
… next two Wednesdays work on our announcement texts
… then a last Wednesday for finals and leftovers
… handoff to W3 staff for a respec check on the 3rd (the 2nd upcoming Wednesday)

Overlays edit review

https://a11yedge.github.io/capabilities/#overlays

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.
… documented in this document --> change to documented in this publication
… We believe that the wide range of specific web accessibility --> We don't need the 'we believe'
… just capitalize the "T" -- The wide range of specific web accessibility outcomes
… It is essential that vendor's marketing products and services: Add "OF" and move the apostrophe
… It is essential that vendors' marketing of products and services
… COULD ALSO BE It is essential that vendors who market products and services

janina: This sentence can be deleted entirely
… Transparency regarding the extent and manner in which post-source techniques are applied is critical to ensure clarity and alignment with intended outcomes.
… new paragraph:
… 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.
… Forthright representation is essential for building trust.
… Vendors marketing approaches such as those discussed in this document, should transparently articulate what their technologies and approaches can genuinely deliver.
… 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.

https://a11yedge.github.io/capabilities/#manage

Management

https://a11yedge.github.io/capabilities/#manage

Lionel_Wolberger: edit Though to argue any remediation not done....
… replace with Though to argue against any remediation not done at source or not performed by a human

jason: Human remediation of A-I identified checkpoints
… add automation as well
… Human remediation of automation, or A-I identified, checkpoints

Lionel_Wolberger: an an interface made --- remove an an

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.
… remove CLIENT
… remove 'or of CSS'
… in this sentence, A typical limitation allows edits to element-level code, but not the modification of interactive components or of CSS.

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. '
… express it's --- remove apostrophe express its
… delete the central sentence, it makes the same point twice
… 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.
… in this sentence 'Post-source interfaces can facilitate the addition of missing accessibility markup to content'
… delete the tail end, 'to content'
… shorten this sentence This will frequently lead to both inaccessible content and core interactions issues
… delete core interactions issues, just keep inaccessible content
… double comma Sometimes,, t
… authentication or invoicing --- change to authentication or payment processing

janina: Delete this sentence, These experts can provide scalable remediation spanning multiple layers of the site, including dynamic components and interface behaviors.

jason: back to 5.2
… change This capability describes an an interface ... to read, This capability describes an an interface or framework
… any company can build a framework like UserWay and AudioEye have built
… adding framework, means we remove limitations
… and any mention of low code

In dash source

Lionel_Wolberger: clarity & parallelism: Hyphenating in-source clearly pairs with post-source as defined terms, reducing ambiguity. 
… and Disambiguation: It avoids confusion with the verb insource and with the plain prepositional phrase “in the source (code).”
… The draft alternates between in-source and in source when contrasted with post-source -- so watch carefully to avoid blurring function and breaking parallelism.

Post source and Overlay subtletiese

Chris: Can we tease out the relationship of these terms
… which is the umbrella term, and which is a more specific instance

Lionel_Wolberger: I think post-source is the umbrella term

Chris: It resembles to my mind the the overlap and distinctions between terms like dementia and alzheimers
… the terms are blended by the general public, but experts understand their differencees
… in the publicizing of this document, some people will more readily embrace that the document is about overlays, top to bottom
… publication will face these differences in the audience understanding, perception and bias

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

All speakers: Chris, janina, jason, Lionel_Wolberger

Active on IRC: janina, Lionel_Wolberger