Meeting minutes
Agenda Review & Announcements
No changes on agenda
FAST Update - slides: https://docs.google.com/presentation/d/1bQYDKiwv0Fc9HyA6TNzb6paQkQY9OouyH-SbaS2qtd8/edit#slide=id.gc6f73a04f_0_0
MichaelC: Presentation on Functional Needs (TPAC 2022)
janina: This is intended to become an APA publication
(Presentation will be made available by link)
Gottfried: Balance impairment is important for XR
… This would probably go into the Sensory category
<MichaelC> https://
MichaelC: We have 'use with vestibular issues' under sensory intersections right now. If we need more information about it, feedback is welcome.
Gottfried: I know an expert in this area; could pass on details.
Gottfried: Categorization of users has been done in a European standard (EN 301 549 chp. 4). Maybe not ideal, but it's very widespread so worth consideration.
MichaelC: I think we've looked at this (not claiming full coverage, though). Will need to keep looking at them.
MichaelC: This has been an exercise of collecting from disparate sources, and trying to organize usefully.
Gottfried: What about emotional mental health?
<Zakim> Gottfried, you wanted to ask about persons with balance impairment and to ask about UANs from EN 301 549 chp. 4
MichaelC: This is covered in the COGA feedback, which we're incorporating.
Input for balance impairment: Making Virtual Reality More Accessible for Persons with Balance Impairments | Dr. John Quarles: https://
MichaelC: *Demos material proposed to be added wrt COGA concers on mental health*
Gottfried: I like this approach; would be good to get to a widely accepted categorization. Useful for teaching.
ack
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Nothing new
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
No issue
new on TR http://www.w3.org/TR/tr-status-drafts.html
Trace Context Level 2
<Roy> - spec: https://
<Roy> - tracking: https://
<Roy> This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios.
Roy: Spec defines standard HTTP headers
… for tracing scenarios
… Do not think that there are a11y considerations
matatk: I see they have Security and Privacy considerations, but no a11y considerations. Problably not needed.
janina: In HTTP 1, imposed by IETF, you were not allowed to transform the content. Is this still a concern?
matatk: Not as wide-reaching as HTTP
… Just adds some headers
janina: Not fully convinced. We still have time because it is just a FWD.
matatk: Can keep looking.
janina: Maybe we can write that we have not identified anything special now, but we are not sure and will keep watching.
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
matatk: CfC regarding WebXR, device model
https://
matatk: Does anybody have any specs that they are currently working on?
(no response)
EPUB 3.3 review
matatk: Changes on 3 EPUB specs.
… New approach: keep publishing CRs, review on changes only.
Here's what we've been asked to review: https://
matatk: They provided us with links to the lists of changes since last year (3.2).
… Who can do the review?
Gottfried: Timeframe?
matatk: Not absolutely urgent, but they are expecting an answer from us.
Fredrik: I could do it, but only late Nov or Dec.
matatk: Some experts among us are already involved, but we should have a wider review.
janina: Fredrik and I did this last year - i can do it with him now again - by end Nov.
matatk: If anybody else would like to review soon - just let us know. Otherwise Fredrik and Janina will do this.
ACTION: Fredrik and janina to review https://
<trackbot> Created ACTION-2329 - And janina to review https://
ACTION-2329 due 2022-12-14
<trackbot> Set ACTION-2329 And janina to review https://
ACTION: janina and Frederik to review https://
<trackbot> Created ACTION-2330 - And frederik to review https://
ACTION 2330 due 2022-12-14
<trackbot> Error finding '2330'. You can review and register nicknames at <https://
ACTION-2330 due 2022-12-14
<trackbot> Set ACTION-2330 And frederik to review https://
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
No report on progress
Task Force & Deliverables Updates
Coga
Fazio: Has the documentation tool also things like slack?
janina: There are multiple tool sets that are accessible and used by many people.
… But other persons find them problematic.
… We need to describe the exact problems so to be better working across all a11y needs.
… The first WD is intentionally sceletal. We are looking for comments to get more details.
Fazio: Will relay the message
Fazio: No other updates from Coga
RQTF
<janina> https://
<Roy> CTAUR CFC snapshot: https://
janina: Resolution to ask APA for CfC.
… Roy has prepared a CfC. Will send to the group later today.
… Editorial changes during the CfC are always allowed.
… Due date is end of Dec because RQTF has a break now.
Fredrik: How to pronounce CTAUR
janina: "Seatower"
… Was a big discussion...
janina: Another major area for RQTF: Digital wallets.
… Interesting conversations already ongoing.
… What kinds of data can be transmitted?
Spoken presentation
janina: Working on a request on W3C based on TPAC conversations.
Maturity model
Fazio: No news
Other Business
matatk: Next week on the agenda: CSS
… We are looking forward to increasing our relationship with CSS
janina: We may need to mitigate between CSS and spoken presentation
PaulG: Spoken pronunciation TF might need to change.
Gottfried: Would be helpful if people could sign in to ZOOM under the same name as in IRC, or at least with the same starting letters. Would be much easier for scribes.