Meeting minutes
XR Accessibility User Requirements: issues.
jgw: Still believe our doc is close to final, but there are still a series of issues we've been clearing
jo: Believe we've been making our text clearer
jo: Also awaiting COGA responses; they're on a two week time out
jgw: Now expecting we can finish editorial work by next call
jgw: Plan is final RQTF review following next mtg, then apa CfC the week following
jgw: Clarifies editorial are in branch; but substantive issues logged as separate github issues
jo: Good, I've dealt with github
jo: Broadly very happy with the edits; believe they make things clearer
jgw: Questions? Comments?
[crickets]
WebXR Layers API level 1 review.
jgw: On our agenda as part of horizontal APA review process ...
<Joshue108> https://
<Joshue108> https://
jo: Concern is that may be a11y implications to rendering resolution adjustments
jo: Concerned we may need to prevelege captions/ content?
<jasonjgw> Janina: This spec provides a mechanism whereby resolution may be lowered (e.g., bandwidth constraints). We want to privilege accessibility-critical rendering over non-critical rendering.
jgw: Sounds like something we should raise
<jasonjgw> Janina can move this forward as a resolution within the APA Working Group. Janina reviews the process: APA identifies issues that raise accessibility concerns in W3C specifications. APA then engages with the relevant Working Group to resolve those concerns before the technical specification proceeds to W3C Recommendation.
<jasonjgw> All participants in APA can take part in the decision-making process regarding such comments. Janina considers it would be valuable to have research identifying the difficulties that arise when resolution drops below a specified threshold.
<jasonjgw> This would assist in documenting why the accessibility-specific parts of the rendering need to remain at an adequate resolution.
<Joshue108> JW: That is reasonable
<Joshue108> Anyone else aware of it?
<jasonjgw> Janina notes that captioning in immersive environments consumes a small part of the bandwidth also.
Action: Josh to ping Immersive Captions group for input on the importance of high resolution for captions
<trackbot> Created ACTION-2297 - Ping immersive captions group for input on the importance of high resolution for captions [on Joshue O Connor - due 2021-07-21].
<jasonjgw> Janina: clarification of what happens when resolution degrades too much is useful to justify treating accessibility-critical components specially.
<jasonjgw> Janina agrees that, as it's likely to be a separate stream, privileging it shouldn't be difficult.
jgw: Sounds like we have a good path forward
<jasonjgw> Janina: it hasn't reached the later stages of the process yet.
<jasonjgw> Janina: notes there is a new dashboard tracking APA Working Group specification reviews.
jgw: Proposes to return to topic next week
W3C Automotive activity and accessibility.
ted: Introduces himself ...
ted: former W3C staff, working on incorporating a11y needs into automotive/transportation
jgw: So, for the r&d discussions, we're the spot for a11y! Are you thinking of anything specific you wanted to highlight for our cdiscussion?
jgw: Invites topic intro ...
ted: Focus more on service and data models
ted: notes vehicles today are mini networks that produce data and respond to data
ted: lots of interest from all kinds of directions, traffic management, fleet management, insurance, etc
ted: much of this is behind the scenes and has no UI
ted: But some people need adaptive controls; and phps standards could facilitate that
ted: thinking to support any device the passenger/driver brings
ted: so far a best practices doc
<jasonjgw> Janina: notes the various activities that take place in a vehicle - driving, entertainment, communication, etc. Janina inquires whether there is a good classification/delineation of activities in the data and control functions.
ted: no media interfaces but hoping to work with the groups that do that
ted: industry seems to be moving toward android automotive
janina: underscores mono culture
jgw: Notes our NAUR doc
<Joshue108> JW: We are also looking at Natural Language interfaces etc
jgw: other issues as industry moves to partially or fully autonomous
<Joshue108> There are issues with partly or autonomous vehicles
jgw: notes we've had some discussion in the past, but don't believe we've documented in a single doc
jgw: Phps we could consider an AUR
jgw: Invites comments ...
ted: Notes how VW is taking a11y very seriously and working on incorporating a11y into vehicle design
ted: are other similar ... we can give input as may be desired
<Joshue108> JW: What are next steps?
<Joshue108> JS: This is place to take it up
<jasonjgw> Janina: wishes to take it up in RQTF.
<Joshue108> JW: Thats clear
<Joshue108> We have a doc close to publication on XR and Natural Language interfaces, also Media Sync
jgw: jgw: Discusses how RQTF might take this up ...
<Joshue108> We could start another one on automotive and then start requirement gathering exercise
jo: asks ted if there are particular aspects where our help would be most useful?
ted: points to the wiki that's noted above and intended to become a best practices dos
<Joshue108> JW: Looks at current docs and their relevance
<Joshue108> Realtime overlays?
<jasonjgw> Janina: notes that augmented reality (real-time overlays) may be relevant.
<jasonjgw> Janina: enhancing resolution as light conditions change - this is somewht related to XR.
<jasonjgw> Janina: we should consider our RTC document with a view to automotive applications.
<jasonjgw> Similarly for our Remote Meetings work.
jo: So do we add that to Ted's best practices? Or upversion our doc?
<Joshue108> JW: This does overlap
jgw: Expect some overlap with our existing and forthcoming docs
<Joshue108> We have discussed in the past the issues that arise with vehicles
jgw: maybe discussions first, then decisions on where they fit
jgw: suggests next week?
ted: can do
Natural Language Interface Accessibility User Requirements.
jgw: Notes a number of open issues and a pr on github
jgw: proposes to revisit naur once we move xaur to APA
<Joshue108> JS: Am I a blocker here?
<Joshue108> JW: John raised issues, Josh to review
<Joshue108> Some decisions need to be made.
<Joshue108> JS: Sounds fair
<jasonjgw> Janina: inquires into what stands in the way of the pull requests.
j[discussion on whether anyone is blocking progress and what should be next]
Synchronization Accessibility User Requirements.
jgw: Notes Steve has been making contributions with additional content and references
jgw: He continues to review the litt
<jasonjgw> Janina is hopeful of a first public working draft in September/October.
<jasonjgw> Janina: suggests we review the table of contents to look for topics that may be missing.
<jasonjgw> Janina: then subject-matter experts can write generic guidance - even in the absence of documented research.
Miscellaneous topics.
<Joshue108> JW: Prep for TPAC
<Joshue108> JS: Thanks for detailed response
https://
<Joshue108> And noting who we want to talk to
<jasonjgw> Janina: notes Jason's response regarding TPAC agenda yesterday.
<jasonjgw> Janina notes the wiki page in which we're tring to bring together whom we wish to meet with and on what topics.
<jasonjgw> Janina notes that it takes time to organize meetings, and time slots are limited. We therefore try to organize early and to start the scheduling conversations early.
<jasonjgw> Contacts with other working gorups need to start soon. We're already within 100 days of TPAC.
<jasonjgw> Janina would like to keep this as an agendum - preferably relatively early as a priority.
<jasonjgw> Janina can take the next steps for now, but believes this should be a topic for the next few weeks at RQTf.
jgw: Suggests TPAC to be 2nd agendum next week