12:27:57 RRSAgent has joined #apa 12:28:01 logging to https://www.w3.org/2025/06/18-apa-irc 12:28:01 RRSAgent, make logs Public 12:28:02 please title this meeting ("meeting: ..."), janina 12:28:25 Meeting: APA Weekly Teleconference 12:28:31 Date: 18 Jun 2025 12:28:37 Chair: Janina 12:28:43 agenda+ Agenda Review & Announcements 12:28:45 agenda+ TPAC 2025 12:28:45 agenda+ New on TR 12:28:45 agenda+ Charter review requests 12:28:45 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 12:28:46 agenda+ [Comment review requests](https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review) 12:28:49 agenda+ [CSS Update (Paul)](https://github.com/w3c/css-a11y/issues) 12:28:51 agenda+ Actions check-in 12:28:54 agenda+ Other business 12:28:56 agenda+ Be done 12:29:02 agenda? 12:32:04 regrets: Alisa_Smith, Gottfried_Zimmerman 13:06:17 kirkwood has joined #APA 13:26:50 agenda? 13:27:39 regrets+ Niklas_Egger 13:30:23 matatk has joined #apa 13:30:24 agenda? 13:30:35 present+ 13:47:53 PaulG has joined #apa 13:53:17 regrets+ Alisa 13:53:21 regrets+ Gottfried 13:53:31 regrets+ Niklas 13:53:36 rrsagent, make minutes 13:53:38 I have made the request to generate https://www.w3.org/2025/06/18-apa-minutes.html matatk 13:54:15 regrets- Niklas 13:54:19 regrets- Gottfried 13:54:23 regrets- Alisa 13:54:25 rrsagent, make minutes 13:54:26 I have made the request to generate https://www.w3.org/2025/06/18-apa-minutes.html matatk 13:55:11 present+ 13:55:47 present+ 13:59:09 Dr_Keith has joined #apa 13:59:16 present+ 14:01:55 JenStrickland has joined #apa 14:02:03 present+ 14:02:54 present+ 14:02:57 rrsagent, make minutes 14:02:58 I have made the request to generate https://www.w3.org/2025/06/18-apa-minutes.html matatk 14:03:33 zakim, pick a victim 14:03:33 Not knowing who is chairing or who scribed recently, I propose matatk 14:03:47 zakim, pick a victim 14:03:47 Not knowing who is chairing or who scribed recently, I propose PaulG 14:04:27 zakim, next item 14:04:27 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 14:04:59 Fredrik has joined #apa 14:05:07 present+ 14:05:50 JenStrickland: There was a review of the HTML CSS inert attribute work, I think it's worth looking at. Tagged PaulG so maybe he could look at it before we do. There are some layers of complexity that we should discuss. Some smart people within CSS are raising concerns. 14:07:49 Neha has joined #apa 14:08:27 *we add it to the agenda for next week* 14:08:36 zakim, next item 14:08:37 agendum 2 -- TPAC 2025 -- taken up [from janina] 14:09:00 q+ 14:09:05 janina: As you heard last week, we have been busy and filing requests for meetings with other groups. 14:09:28 ... Are there any additional things we need to know? W3C requires them by Friday. As usual, we have a list of issues and groups we want to meet at TPAC. 14:09:33 ack Roy_Ruoxi 14:09:56 Roy_Ruoxi: I have created a placeholder for APA WG. If we got a resolution we can update that. 14:10:01 q+ 14:10:34 https://github.com/w3c/tpac2025-meetings/issues/30 14:11:15 ack ma 14:13:31 zakim, next item 14:13:31 agendum 3 -- New on TR -- taken up [from janina] 14:13:43 Roy_Ruoxi: Nothing new this week. 14:13:50 zakim, close this item 14:13:50 agendum 3 closed 14:13:51 I see 7 items remaining on the agenda; the next one is 14:13:51 4. Charter review requests [from janina] 14:13:53 zakim, next item 14:13:53 agendum 4 -- Charter review requests -- taken up [from janina] 14:14:19 subtopic: [wg/social] Social Web Working Group new charter 14:14:19 https://github.com/w3c/strategy/issues/435 14:15:29 janina: No concerns; can sign off 14:15:44 subtopic: [wg/apa] Accessible Platform Architectures Group Charter 14:15:44 https://github.com/w3c/strategy/issues/498 14:16:01 q+ 14:16:14 https://github.com/w3c/strategy/issues/498#issuecomment-2975648043 14:21:02 Roy_Ruoxi: Comment raises several process questions. 14:21:10 janina: Can we address in next planning call? 14:21:13 Roy_Ruoxi: OK 14:21:15 zakim, next item 14:21:15 I see a speaker queue remaining and respectfully decline to close this agendum, matatk 14:21:18 ack Roy_Ruoxi 14:21:19 zakim, next item 14:21:20 agendum 5 -- [Spec review requests](https://github.com/w3c/a11y-request/issues) -- taken up [from janina] 14:21:56 subtopic: Audio Session 14:21:56 https://github.com/w3c/a11y-request/issues/108 14:21:56 Due: 2025-04-24 14:23:06 chiace has joined #apa 14:23:13 +present 14:23:19 present+ 14:24:14 present+ 14:25:42 matatk: Great positive answer (and take up of offer of ACs section) from Marcos - but I am still unclear as to where in the spec it actually makes it clear that hints are being passed to the OS - should we ask them to make it clearer? 14:25:52 janina: It's an early stage document, so yes. 14:27:36 JenStrickland: Agree. Important to raise awareness of accessibility amongst designers and developers. 14:27:40 q? 14:28:27 matatk I'm happy to review anything for co-authoring the accessibility considerations. 14:28:55 subtopic: Web Neural Network API 14:28:55 https://github.com/w3c/a11y-request/issues/105 14:28:55 Due: 2025-06-20 14:29:13 APA reviewers' thread: https://github.com/w3c/apa/issues/350 14:31:35 matatk: Chiara has done additional research on these. We agreed on most of them but didn't have suggestions on some. 14:32:25 Chiara: 2.2.5 Background Blur - latency can cause issues. Added a requirement to have user-controllable background blur. The toggle should be keyboard operable. Consider latency - 150ms seems to be an important threshold. 14:33:10 ... 6.2: At the moment the author only can provide power/performance hints. Allowing option for the UA to override them, controlled by the user, would help. Users from different socioeconomic backgrounds particularly affected. 14:33:42 ... 7.1 to 7.3 no change needed, but maybe helpful to clarify that they're targeted at implementer, not accessibility specific. 14:34:02 ... Example 9 uses an ASCII diagram. SVG may be more accessible. 14:34:39 ... Last point: we need an ACs section. Let's introduce one to summarize the accessibility concerns. 14:34:56 ... including confidence, and other issues raised above - and reference appropriate docs. 14:35:09 q? 14:35:11 ... What do you think? 14:35:53 Dr_Keith: +1 Chiara. If we are going to have ACs sections for all documents going forward, do we have a specific structure we'd like folks to use moving forward? 14:35:57 q+ 14:36:11 Dr_Keith: Or do we do it case-by-case? 14:36:31 janina: We have in the past considered a template; still under advisement for us to do; easier if you have a starting point, but it doesn't exist yet. 14:36:45 Dr_Keith: Is that something we could do now? 14:37:20 janina: We'd be more effective if we had it. 14:37:45 q+ 14:37:47 janina: We shouldn't let it get in the way of a specific review; that's where we've tripped up - figuring out the specific parts vs generic ones. 14:38:20 q? 14:38:35 Chiara: I think the main point of ACs section is having a consistent structure across the documents; maybe we can have simple overview with key points; user control, performance impacts; fallbacks; AT; privacy; in this case. 14:39:00 ... I'm new so looking for input - maybe investigate the key documentation you produce and refine them into a structure. 14:39:32 matak: I don't think 7.1-7.3 isn't really needed since there are no changes needed 14:39:49 ...dev docs usually end up on MDN 14:40:45 ...as to a stock accessibility section: anything that can help us review is helpful, but maybe what we need more is a list of things for the reviewers to think about to ensure that they include the relevant sections 14:41:14 ...the compute pressure API had some really good examples of this 14:41:53 ...it's just so variable across technology and audience it's hard to prescribe a template across all documents 14:43:21 PaulG: Going back to the document itself. One of the things we can do is help other groups with awareness of ATs. They have noise suppression and speech recognition. In between those is audio description. It could be added here as a use case. It's often something that's missing,a s it takes a human to identify what the sound is, and put it into 14:43:21 text. 14:43:41 ... There's another technology there; VTT. Here's an opportunity for us to add use cases they may be unware of. 14:43:47 q- 14:44:52 chiace has joined #apa 14:45:58 q? 14:47:00 ack me 14:47:01 ack ma 14:47:08 janina: We have consensus 14:47:28 zakim, next item 14:47:28 agendum 6 -- [Comment review requests](https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review) -- taken up [from janina] 14:47:59 subtopic: Add a way to indicate the semantics of ruby annotations 14:47:59 source: w3c/html-ruby#24 14:47:59 tracking: https://github.com/w3c/a11y-review/issues/234 14:50:00 matak: Ruby elements seem like a good approach for symbols but it's not being used what it's meant to be used for which is why i18n isn't in favor of this approach 14:50:27 ...the proposal adds a type attribute to ruby that would distinguish this new use case 14:50:27 q? 14:51:03 ...the ADAPT task force would be in favor. If anyone wants to look into it, comment on the tracking issue in the a11y-review repository 14:51:40 ...if you comment on the actual issue (linked from the review issue), it would be from you, not APA 14:51:55 chair: me 14:52:00 scribe: me 14:52:08 scribe+ 14:52:14 (yeah that) 14:52:57 https://drafts.csswg.org/pointer-animations-1/ 14:53:15 subtopic: Pointer animations 14:53:20 https://drafts.csswg.org/pointer-animations-1/ 14:53:34 PaulG: This set off alarm bells for me. Needs strongly-worded considerations. 14:54:12 PaulG: What about eye gaze etc? This will be a problem for a lot of people. I commented that this *must* have an ACs section, and they may need help with writing that. 14:54:27 ... If anyone's interested in the overlap between animation and something that messes withthe pointer's visibility, let me know! I may not have bandwidth for it. 14:55:51 janina: We should put CSS higher up next time! 14:55:56 chair: Janina 14:56:04 rrsagent, make minutes 14:56:05 I have made the request to generate https://www.w3.org/2025/06/18-apa-minutes.html matatk 14:56:17 zakim, end meeting 14:56:17 As of this point the attendees have been matatk, PaulG, janina, Dr_Keith, JenStrickland, Fredrik, present, chiace, Neha 14:56:19 RRSAgent, please draft minutes 14:56:21 I have made the request to generate https://www.w3.org/2025/06/18-apa-minutes.html Zakim 14:56:27 I am happy to have been of service, matatk; please remember to excuse RRSAgent. Goodbye 14:56:27 Zakim has left #apa 15:57:40 kirkwood has joined #APA 16:26:56 kirkwood has joined #APA 16:57:48 janina has left #apa 17:37:35 kirkwood has joined #APA 19:17:52 kirkwood has joined #APA 19:20:15 kirkwood has joined #APA 22:17:48 kirkwood has joined #APA 23:01:39 kirkwood has joined #APA