W3C

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

17 December 2025

Attendees

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

Meeting minutes

<janina> Date 17 Dec 2025

<MIke9> MikeP - Present+

Getting readers and feedback

Lionel_Wolberger: I asked 3 people for feedback

Lionel_Wolberger: I asked 3 people for feedback

janina: We had agreed to wait until after the holiday

MIke: I will reach out to the people I discussed
… Janina and I will do a session at CSUN on this report

janina: We do have the paragraph that we curated
… on the blog https://www.w3.org/community/a11yedge/
… The W3C Accessibility at the Edge Community Group announces publication of its Final Report addressing the trade-offs and benefits of applying dynamic accessibility remediations to web content.
… Today’s typical web page is a complex blend of multiple original sources, yielding experiences that work well for some users but fail for others, leaving many websites and online applications inaccessible to people with disabilities.
… In development since Fall 2022, the report titled: Accessibility Capabilities: Post-Source Code and Content features cross-references to WCAG throughout, because WCAG remains the valid yardstick whether applied in-source or post-source.

Capabilities where Post Source Shines

janina: On my list of action items (after the holiday) go through the capabilities and pick out those where, we argue, post-source is superior
… the low vision capabilities like 3.1.1 Cursor Size are prime examples where post source shines
… each Capability has a unique URI

Lionel_Wolberger: You can copy it from the contents, e.g., https://www.w3.org/community/reports/a11yedge/CG-FINAL-a11yedge-capabilities-20251104/#cursorsize

janina: This would be a useful list to have, apart from the document itself

Cognitive Disability and Neurodiversity

Lionel_Wolberger: I was discussing with COGA post-source and cognitive disability
… They said, requiring acceptance criteria makes it hard to incorporate COGA assertions into WCAG
… and they would prefer assertions

janina: Our report is a set of assertions
… summation benefits in post-source

Live Remediation Session

Chris: I attended a webinar where Amber Hinds and a rep from Woo Commerce did remediation together
… They had a vigorous discussion about the many ways remediation could be done
… I noted that there were many ways to remediate, sometimes disagreement on how to remediate

Lionel_Wolberger: There is variance in the assessments of WCAG experts

Chris: Offering more avenues to remediate, such as via post source, seems a good idea

janina: But the person remediating needs to have a sufficient level of expertise
… just like in navigation, there are usually a variety of routes
… but which route is optimal requires a depth of decision-making
… but all routes reach the same destination

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Maybe present: MIke

All speakers: Chris, janina, Lionel_Wolberger, MIke

Active on IRC: janina, Lionel_Wolberger, MIke9