W3C

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

13 May 2026

Attendees

Present
janina, Jason, Lionel_Wolberger, mike
Regrets
-
Chair
Janina
Scribe
Lionel_Wolberger, janina

Meeting minutes

ICCHP Papers

janina: Gave an executive summary of her paper, Beyond the Source
… go back to considering accessibility across the whole pipeline, not just at source

jason: One of the axioms we have inherited, is that screen reader use should not be revealed to a website
… But an end-user announcing to a site, these are the personalizations that I need, could be useful

janina: THe post-source report does include that desire as an aspirational goal
… I agree, this is an issue we should address

jason: We treat mobile output differently, the user says "I need this viewport" and the site provides it
… the axiom is, everything should be supported equally from one source code
… perhaps we can pick this statement apart

janina: We see this issue in gaming, and some new approaches are being discussed, and not "one size fits all" accessibility

jason: That is a specific use case which may allow for this discussion

Lionel_Wolberger: Will be presenting current state of post-source in user agents

jason: Evil people did not introduce the API DOM. The browsers introduced that API because it enabled helpful interventions
… the paper does not mention that

Lionel_Wolberger: The paper is intended to drive home what browsers can do

jason: the browser allows JS to rewrite the DOM, at the DOM level
… some people saw some quick and easy stuff at the DOM level and made overly broad claims based on that
… but that did not rule out that this approach, put there by the browser manufacturer, for good reason

mike: It might be interesting to see why browser manufacturers built that in, in 2015

jason: I would guess it was not done for accessibility, it was likely done for business reasons

jason: A quick look at LLMs says: the DOM was opened up to allow dynamic web apps and experiences

mike: I am thinking back to Microsoft and Netscape browser-makers arguing, and I am frustrated
… if you had a choice, with limited resources (a) fix everything at source or (b) at DOM level, which would you choose?

jason: Lionel's Browser Table paper, should connect what the browsers do

mike: This conference is very scientific, primarily for researchers

Lionel_Wolberger: Let's meet again in two weeks.

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

Diagnostics

All speakers: janina, jason, Lionel_Wolberger, mike

Active on IRC: janina, Lionel_Wolberger, mike