Meeting minutes
<Bev_C> Bev is here
janina: Time zone changes coming up, USA and the Americas will be one hour earlier than EU/EMEA for a few weeks
Welcome & Intros (as needed)
Continued Capabilities Discussion
<Bev_C> Janina presented at World Information Architecture Day New York 2024 (WIAD NY 24) on A11y Edge and related W3C A11y Standards
<Bev_C> WIAD attendees were from W3C A11y Edge, and Information Architecture Community Group (IACG) and the World Information Architecture Association (WIAA) and about 12 other organizations including Universities
Lionel_Wolberger: The Community Group has a good, exhaustive list of all possible accessibility edge remediation capabilities
janina: This report card can allow checking off which capabilities are in a particular technology
Bev_C: Is this personas, classes and types of users?
Lionel_Wolberger: No, it's an itemization of functionality or capability
Jason: The types of items that you may want to control / remediate
… you may want to control preferences, remediate a keyboard trap
… there are things you need to do -- make it semantic, useable, operable, understandable, more or less conform with WCAG
… there are things you want to do , for users to self-service themselves, personalize
… the first document is pretty good in its list of these things
… the second document, could be a report
… the CG can also give guidance on what should be done, not only what can be done
Bev_C: The idea of relying parties could be helpful. Or remediating parties.
… +1 to Jason's pointing out: 'Need to's and might want to do's'
janina: Note, I added 'automatability'
Jason: There's an entire lifecycle regarding automation: (a) detect it (b) remediate it (c) verify the remediation
janina: We are not limited to remediations
Jason: In 'presentation' is a lot of 'what you can do', above and beyond 'what you have to do'
janina: WCAG-aligned capabilities would be, the things you 'have to do'
<Bev_C> Text Services (Semantics + Semiotics)
<janina> ~
Lionel_Wolberger: After much discussion, we now want our H1s to be:
… 1- Content , 2- Presentation, 3- Functionality, 4- Management
… 1- Content (mostly the Words/Content, Moderating?) Text Services (Semantics/Semiotics) (the content marked up by HTML) Static and Dynamic
… 2- Presentation (mostly CSS)
… 3- Functionality (mostly JS)
… 4- Management (mostly Administrative, management, work flows) Analytics, Governance
janina: We are comfortable with a second document that is a report card template referencing the explanatory report
… by mneans of which a service provider of edge services can declare what they might offer
Bev_C: I'm hearing that remediation is an injection into any level / layer of the system, is that what y'all are thinking?
… Explanatory report card template, a service provider can declare what they offer
<Bev_C> Exit