12:32:42 RRSAgent has joined #rqtf 12:32:42 logging to https://www.w3.org/2021/07/14-rqtf-irc 12:32:44 RRSAgent, make logs public 12:32:44 Zakim has joined #rqtf 12:32:46 Meeting: Accessible Platform Architectures Working Group Teleconference 12:32:46 Date: 14 July 2021 12:32:49 agenda+ XR Accessibility User Requirements: issues. 12:32:49 agenda+ WebXR Layers API level 1 review. 12:33:09 agenda+ W3C Automotive activity and accessibility. 12:33:32 agenda+ Natural Language Interface Accessibility User Requirements. 12:33:32 agenda+ Synchronization Accessibility User Requirements. 12:33:32 agenda+ Miscellaneous topics. 12:33:49 zakim, list agenda 12:33:49 I see 6 items remaining on the agenda: 12:33:50 1. XR Accessibility User Requirements: issues. [from jasonjgw] 12:33:50 2. WebXR Layers API level 1 review. [from jasonjgw] 12:33:50 3. W3C Automotive activity and accessibility. [from jasonjgw] 12:33:50 4. Natural Language Interface Accessibility User Requirements. [from jasonjgw] 12:33:50 5. Synchronization Accessibility User Requirements. [from jasonjgw] 12:33:51 6. Miscellaneous topics. [from jasonjgw] 12:34:10 chair: jasonjgw 12:34:12 present+ 12:48:23 janina has joined #rqtf 12:59:56 present+ 12:59:58 present+ 13:00:00 scribe: janina 13:01:20 zakim, next item 13:01:20 agendum 1 -- XR Accessibility User Requirements: issues. -- taken up [from jasonjgw] 13:01:37 regrets: Scott, Judy, Steve 13:01:43 present+ 13:02:32 jgw: Still believe our doc is close to final, but there are still a series of issues we've been clearing 13:04:05 jo: Believe we've been making our text clearer 13:04:37 jo: Also awaiting COGA responses; they're on a two week time out 13:05:53 jgw: Now expecting we can finish editorial work by next call 13:06:33 jgw: Plan is final RQTF review following next mtg, then apa CfC the week following 13:07:19 jgw: Clarifies editorial are in branch; but substantive issues logged as separate github issues 13:07:26 jo: Good, I've dealt with github 13:08:02 jo: Broadly very happy with the edits; believe they make things clearer 13:08:23 becky has joined #rqtf 13:08:43 jgw: Questions? Comments? 13:08:48 [crickets] 13:08:52 zakim, next item 13:08:53 agendum 2 -- WebXR Layers API level 1 review. -- taken up [from jasonjgw] 13:09:28 jgw: On our agenda as part of horizontal APA review process ... 13:09:34 https://www.w3.org/TR/webxrlayers-1/ 13:10:07 https://lists.w3.org/Archives/Public/public-apa/2021May/0040.html 13:10:58 jo: Concern is that may be a11y implications to rendering resolution adjustments 13:11:21 jo: Concerned we may need to prevelege captions/ content? 13:12:33 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. 13:13:33 jgw: Sounds like something we should raise 13:14:52 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. 13:16:12 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. 13:16:32 This would assist in documenting why the accessibility-specific parts of the rendering need to remain at an adequate resolution. 13:16:53 JW: That is reasonable 13:16:56 present+ 13:17:05 Anyone else aware of it? 13:18:03 Janina notes that captioning in immersive environments consumes a small part of the bandwidth also. 13:18:51 ACTION: Josh to ping Immersive Captions group for input on the importance of high resolution for captions 13:18:51 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]. 13:18:53 Janina: clarification of what happens when resolution degrades too much is useful to justify treating accessibility-critical components specially. 13:19:45 Janina agrees taht, as it's likely to be a separate stream, privileging it shouldn't be difficult. 13:19:59 s/taht/that 13:20:06 jgw: Sounds like we have a good path forward 13:20:49 Janina: it hasn't reached the later stages of the process yet. 13:22:12 Janina: notes there is a new dashboard tracking APA Working Group specification reviews. 13:22:39 jgw: Proposes to return to topic next week 13:22:47 zakim, next item 13:22:47 agendum 3 -- W3C Automotive activity and accessibility. -- taken up [from jasonjgw] 13:23:53 ted: Introduces himself ... 13:24:27 ted: former W3C staff, working on incorporating a11y needs into automotive/transportation 13:25:38 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? 13:25:46 jgw: Invites topic intro ... 13:26:07 ted: Focus more on service and data models 13:26:34 ted: notes vehicles today are mini networks that produce data and respond to data 13:26:56 ted: lots of interest from all kinds of directions, traffic management, fleet management, insurance, etc 13:27:05 ted: much of this is behind the scenes and has no UI 13:27:31 ted: But some people need adaptive controls; and phps standards could facilitate that 13:28:09 ted: thinking to support any device the passenger/driver brings 13:28:21 ted: so far a best practices doc 13:30:00 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. 13:30:34 ted: no media interfaces but hoping to work with the groups that do that 13:30:55 ted: industry seems to be moving toward android automotive 13:32:23 janina: underscores mono culture 13:32:42 jgw: Notes our NAUR doc 13:32:43 JW: We are also looking at Natural Language interfaces etc 13:33:00 jgw: other issues as industry moves to partially or fully autonomous 13:33:00 There are issues with partly or autonomous vehicles 13:33:21 jgw: notes we've had some discussion in the past, but don't believe we've documented in a single doc 13:34:17 jgw: Phps we could consider an AUR 13:34:27 jgw: Invites comments ... 13:35:37 ted: Notes how VW is taking a11y very seriously and working on incorporating a11y into vehicle design 13:36:44 ted: are other similar ... we can give input as may be desired 13:36:56 q+ 13:37:06 JW: What are next steps? 13:37:19 JS: This is place to take it up 13:37:20 Janina: wishes to take it up in RQTF. 13:37:28 JW: Thats clear 13:37:52 We have a doc close to publication on XR and Natural Language interfaces, also Media Sync 13:38:12 jgw: jgw: Discusses how RQTF might take this up ... 13:38:13 We could start another one on automotive and then start requirement gathering exercise 13:38:27 ack me 13:38:37 q? 13:39:21 jo: asks ted if there are particular aspects where our help would be most useful? 13:40:04 ted: points to the wiki that's noted above and intended to become a best practices dos 13:41:02 JW: Looks at current docs and their relevance 13:41:10 Realtime overlays? 13:41:31 Janina: notes that augmented reality (real-time overlays) may be relevant. 13:41:53 Janina: enhancing resolution as light conditions change - this is somewht related to XR. 13:42:12 Janina: we should consider our RTC document with a view to automotive applications. 13:42:26 Similarly for our Remote Meetings work. 13:43:38 jo: So do we add that to Ted's best practices? Or upversion our doc? 13:43:48 JW: This does overlap 13:43:58 jgw: Expect some overlap with our existing and forthcoming docs 13:44:02 We have discussed in the past the issues that arise with vehicles 13:44:25 jgw: maybe discussions first, then decisions on where they fit 13:44:50 jgw: suggests next week? 13:44:52 ted: can do 13:47:40 zakim, next item 13:47:40 agendum 4 -- Natural Language Interface Accessibility User Requirements. -- taken up [from jasonjgw] 13:48:20 jgw: Notes a number of open issues and a pr on github 13:48:36 jgw: proposes to revisit naur once we move xaur to APA 13:49:54 JS: Am I a blocker here? 13:50:02 JW: John raised issues, Josh to review 13:50:11 Some decisions need to be made. 13:50:19 JS: Sounds fair 13:50:35 Janina: inquires into what stands in the way of the pull requests. 13:52:07 j[discussion on whether anyone is blocking progress and what should be next] 13:52:57 zakim, next item 13:52:57 agendum 5 -- Synchronization Accessibility User Requirements. -- taken up [from jasonjgw] 13:53:30 jgw: Notes Steve has been making contributions with additional content and references 13:53:37 jgw: He continues to review the litt 13:54:05 Janina is hopeful of a first public working draft in September/October. 13:54:52 Janina: suggests we review the table of contents to look for topics that may be missing. 13:55:18 Janina: then subject-matter experts can write generic guidance - even in the absence of documented research. 13:55:40 zakim, next item 13:55:40 agendum 6 -- Miscellaneous topics. -- taken up [from jasonjgw] 13:56:25 JW: Prep for TPAC 13:56:32 JS: Thanks for detailed response 13:56:44 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021 13:56:44 And noting who we want to talk to 13:56:48 Janina: notes Jason's response regarding TPAC agenda yesterday. 13:57:13 Janina notes the wiki page in which we're tring to bring together whom we wish to meet with and on what topics. 13:57:47 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. 13:58:18 Contacts with other working gorups need to start soon. We're already within 100 days of TPAC. 13:58:40 Janina would like to keep this as an agendum - preferably relatively early as a priority. 13:59:01 Janina can take the next steps for now, but believes this should be a topic for the next few weeks at RQTf. 14:00:03 jgw: Suggests TPAC to be 2nd agendum next week 14:00:48 zakim,rrsagent, make minutes 14:00:48 I don't understand 'rrsagent, make minutes', jasonjgw 14:01:01 rrsagent, make minutes 14:01:01 I have made the request to generate https://www.w3.org/2021/07/14-rqtf-minutes.html jasonjgw 14:01:09 janina has left #rqtf 14:01:18 zakim, bye 14:01:18 leaving. As of this point the attendees have been jasonjgw, janina, Joshue 14:01:18 Zakim has left #rqtf 14:01:27 rrsagent, make minutes 14:01:27 I have made the request to generate https://www.w3.org/2021/07/14-rqtf-minutes.html jasonjgw 15:53:15 becky has joined #rqtf