W3C

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

30 Oct 2024

Attendees

Present
Chris, janina, Jason, Lionel_Wolberger, Mike, Mike6
Regrets
-
Chair
Janina
Scribe
janina

Meeting minutes

<Mike6> i'm here

<Lionel_Wolberger> Mike6: Regrets for next week 6 Nov, but rest of November should be ok

<Lionel_Wolberger> janina: Rest of November ok for me as well

<Lionel_Wolberger> Chris: No conflict day before Thanksgiving

<Lionel_Wolberger> janina: That make us clear until the last two weeks of the year which we will likely take off.

<Lionel_Wolberger> ... likely meet up to and including Dec 18, then resume 8 Jan

Welcome and Introductions (As needed)

Capabilities Review https://a11yedge.github.io/capabilities/

<Lionel_Wolberger> Lionel_Wolberger: Reading the document

<Lionel_Wolberger> ... heading 1.5 should be 2.0

<Lionel_Wolberger> ... correction: 1.4

<Lionel_Wolberger> ... we are looking at the "heading 2's" in the intro section

<Lionel_Wolberger> Mike6: We likely do not want the word 'edge' in the section

<Lionel_Wolberger> Lionel_Wolberger: I agree, the heading could be better as 'defining scope'

<Lionel_Wolberger> Mike6: Edge is just vernacular

<Lionel_Wolberger> janina: People expect scope at the opening of a w3c document

<Lionel_Wolberger> Lionel_Wolberger: Sharing the diagram in https://www.w3.org/community/a11yedge/2023/05/18/interest-in-our-work-is-growing/

<Lionel_Wolberger> ... top would be labeled "source" or "source content"

<Lionel_Wolberger> ... the right cloud Post-Source Service

<Lionel_Wolberger> ... at the bottom, user

<Lionel_Wolberger> janina: Regarding the diagram, i think singular "user" is more powerful than "users"

<Lionel_Wolberger> Lionel_Wolberger: The group brainstormed about the proposed diagram

<Lionel_Wolberger> ... decided: The top and bottom should reflect the highly accepted server/client pattern, so we added those labels

<Lionel_Wolberger> .... decided: the bottom should say, in as few words a spossible, that we acknowledge that the user's side is a diverse place c potentially composed

<Lionel_Wolberger> ... of many tools such as browser, browser extension, aassistive technology, devices, screens, etc

<Lionel_Wolberger> Chris: For 'Post source services', is services the right word? Enhancements, improvements is more illustriative

<Lionel_Wolberger> jason: I value the discussion clarifying what exactly are these post-source services. Enhacement, improvement

<Lionel_Wolberger> ... remediation is also appropriate

<Lionel_Wolberger> ... but services is an apt generic label for the diagram, and then the text can go into more detail on the nature of those services

<Lionel_Wolberger> chris: usability is also a relevant word

<Lionel_Wolberger> Jason: Changes instead of services

<Lionel_Wolberger> janina: Adaptations is a more

<Lionel_Wolberger> ... used word in the accessibility field

<Lionel_Wolberger> jason: I can write a statement for "scope" and "automatability"

<Lionel_Wolberger> Lionel_Wolberger: I will send the diagram to Janina for inclusion

<Lionel_Wolberger> ... with a caption

Minutes manually created (not a transcript), formatted by scribe.perl version 238 (Fri Oct 18 20:51:13 2024 UTC).

Diagnostics

Active on IRC: janina, Lionel_Wolberger, Mike6