12:30:40 RRSAgent has joined #apa 12:30:45 logging to https://www.w3.org/2026/08/05-apa-irc 12:30:45 RRSAgent, make logs Public 12:30:46 please title this meeting ("meeting: ..."), janina 12:30:46 Chair: Janina 12:30:52 Date 05 Aug 2026 12:32:53 agenda+ Agenda Review & Announcements 12:32:53 agenda+ [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) 12:32:53 agenda+ New charters review 12:32:53 agenda+ New on TR 12:32:53 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 12:32:56 agenda+ [Issue tracking](https://github.com/w3c/a11y-tracking/issues) 12:32:58 agenda+ CSS Update (Paul) 12:33:01 agenda+ Actions Checkin 12:33:03 agenda+ Other business 12:33:06 agenda+ Be done 13:54:06 JonCohn has joined #apa 13:54:20 present+ 13:55:44 open the zoom link 13:59:29 PaulG has joined #apa 14:01:41 gpellegrino has joined #apa 14:02:01 present+ 14:02:26 matatk has joined #apa 14:02:47 present+ 14:03:46 present+ 14:03:48 present+ 14:04:24 present+ 14:05:10 agenda? 14:05:51 Vanessa has joined #apa 14:06:08 present+ 14:06:14 present+ 14:06:25 rrsagent, make minutes 14:06:26 I have made the request to generate https://www.w3.org/2026/08/05-apa-minutes.html matatk 14:06:56 zakim, next item 14:06:56 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 14:08:39 zakim, who's here? 14:08:39 Present: JonCohn, gpellegrino, janina, PaulG, matatk, Roy_Ruoxi, Vanessa 14:08:41 On IRC I see Vanessa, matatk, gpellegrino, PaulG, RRSAgent, Zakim, lea, kizu, janina, Roy_Ruoxi, gb, alastairc, astearns, Rachael, chrishtr, slightlyoff, jyasskin, vmpstr, alice, 14:08:41 ... nicolo-ribaudo 14:08:56 Neha has joined #apa 14:09:06 present+ 14:14:26 scribe+ 14:14:39 zakiom, next item 14:14:44 zakim, next item 14:14:44 agendum 2 -- [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) -- taken up [from janina] 14:14:59 q+ 14:16:20 re: accessibility and privacy, some features which were proposed and could have benefit were not taken up because the fear of privacy risks 14:16:40 matatk: are there any features that are vital enough to accept the privacy risks? 14:17:24 ... we want to hear about those features so we can organize their architectures into any themes that might be present to help build them in a way that better respects privacy concerns 14:17:28 kirkwood__ has joined #APA 14:17:42 ... I will make the breakout proposals 14:18:10 ... there are 9 proposed and we expect an influx of accessibility-related ones 14:18:43 ...last week we talked about accessibility and society mini-workshop and I need to figure out the process for suggesting a lightning talk to them 14:19:26 janina: we'll get our proposals in early but details will continue to flow until late 14:19:33 zakim, next item 14:19:33 I see a speaker queue remaining and respectfully decline to close this agendum, PaulG 14:19:37 ack me 14:19:38 q? 14:19:40 zakim, next item 14:19:40 agendum 3 -- New charters review -- taken up [from janina] 14:20:02 matatk: web apps security charter 14:20:13 subtopic: Web App Sec WG 14:20:15 https://github.com/w3c/strategy/issues/551 14:21:16 review history -> https://www.w3.org/2026/07/15-apa-minutes.html#a019 14:22:42 matatk: we haven't reviewed this group's work very often. However, there's a tie-in to TAG work and well-known URLs, this group has 2: password and passkey 14:24:05 ...there was a lot of discussion in the last TPAC about migrating between devices, credentials, and use cases about the tech and security of that. And we have guidance about the accessibility of the authentication portion of those cases. 14:24:50 q? 14:25:53 janina: I think we're signing off without objection 14:26:01 zakim, next item 14:26:01 agendum 4 -- New on TR -- taken up [from janina] 14:26:26 subtopic: CSS Linked Parameters Module Level 1 14:26:36 https://github.com/w3c/a11y-longitudinal-tracking/issues/54 14:26:44 https://www.w3.org/TR/css-link-params-1/ 14:26:58 kirkwood has joined #APA 14:27:35 PaulG: It's a cool spec that will allow parameters from CSS to be injected and flow into SVGs. It can even penetrate an tag that is hosting an SVG. 14:27:54 PaulG: So you can do stuff like alter colours, sizes, etc. If you work on design systems you'll love this. 14:27:56 scribe+ 14:27:58 RRSAgent, make minutes 14:27:59 I have made the request to generate https://www.w3.org/2026/08/05-apa-minutes.html Roy_Ruoxi 14:28:49 PaulG: My take is this is going to extend capabilities we already have. You wont' need to have as many assets; you'll have one that CSS can modify. 14:28:58 q+ 14:29:39 ack ma 14:29:53 PaulG: The only thing I'd be looking out for is if they want use cases - that could inspire devs to pick it up and use it. Maybe symbols as you say janina, and or high contrast and symbols. Worth making a demo. 14:31:22 ack me 14:31:31 matatk: +1 to what PaulG said, adding use cases is a specialty of ours. I believe TAG is reviewing this. This is clearly something that may not specifically add end-user stuff but it makes building so much easier that it could help accomodate more use cases. 14:31:34 zakim, next item 14:31:34 agendum 5 -- [Spec review requests](https://github.com/w3c/a11y-request/issues) -- taken up [from janina] 14:32:03 subtopic: EPUB Accessibility 1.2 Explainer 14:32:09 https://www.w3.org/TR/epub-a11y-explain-12/ 14:32:22 q+ 14:32:34 https://www.w3.org/TR/epub-a11y-12/ 14:32:46 q+ 14:32:51 q? 14:32:51 ack me 14:32:57 ack ma 14:33:25 matatk: I'm reminded that we have the proposal for .. 14:33:30 https://github.com/w3c/a11y-tracking/issues/311 14:34:13 ... we did just review some epub items and there were a couple of key issues being addressed--fixed layout 14:34:17 ack gpellegrino 14:34:24 ack gr 14:35:19 https://www.w3.org/TR/epub-a11y-12/#change-log 14:35:23 gpellegrino: epub a11y 1.2 is CR defines what it means to have accessible epubs. Essentially, following wcag and have page numbers and time text media 14:35:31 q+ to add other specs in to this topic before we move on (feel free to jump ahead in the queue if you want to talk about this topic) 14:36:37 ... the explainer was requested by the community to help people understand wcag's relationship to epub. For example, authentication isn't something I've never seen. 14:36:56 ... others like multiple ways may be tricky to implement 14:37:10 q? 14:37:52 ack ma 14:37:52 matatk, you wanted to add other specs in to this topic before we move on (feel free to jump ahead in the queue if you want to talk about this topic) 14:39:09 - 2026-07-14: [Digital Credentials](https://github.com/w3c/a11y-tracking/issues/325) 14:39:09 - 2026-07-29: [Attribution Level 1](https://github.com/w3c/a11y-tracking/issues/334) 14:39:09 - 2026-07-31: [CSS Image Animation Module Level 1](https://github.com/w3c/a11y-tracking/issues/333)- 2026-07-14: [Digital Credentials](https://github.com/w3c/a11y-tracking/issues/325) 14:39:09 - 2026-07-29: [Attribution Level 1](https://github.com/w3c/a11y-tracking/issues/334) 14:39:11 - 2026-07-31: [CSS Image Animation Module Level 1](https://github.com/w3c/a11y-tracking/issues/333) 14:40:46 zakim, next item 14:40:46 agendum 6 -- [Issue tracking](https://github.com/w3c/a11y-tracking/issues) -- taken up [from janina] 14:41:19 matatk: there need to be 2 MCP comments that we get into shape 14:41:41 ... one of the questions is about the axtree use by MCP and we aligned with others saying "no" 14:42:19 ... we still need to post the comment but the other question was relating to the accessibility considerations which is a section to be drafted as a general "what do we think" comment. 14:42:56 subtopic: WebMCP: accTree topic 14:42:57 https://github.com/w3c/a11y-tracking/issues/317 14:43:51 draft comment: https://github.com/w3c/a11y-tracking/issues/317#issuecomment-4914862049 14:44:00 matatk: I think PaulG comments need to be raised in the general comment. This issue will reflect the initial concern about axtree redundancy. 14:44:47 q+ 14:46:53 ack me 14:47:39 matatk: we're worried about abuse of the axtree. Authors stuffing keywords meant for agents. 14:48:32 ... making MCP additive fits well. I can add that. But I don't want authors to fiddle with aria just to signal agents. 14:49:32 janina: semantics are useful and if some values need to be stuffed, just make your own tree. Don't get in the way of the accessibility by trying to overfit the existing structure for a different purpose. 14:49:45 matatk: I'll make those edits in the next couple of days. 14:49:59 q? 14:50:48 subtopic: WebMCP overall proposed APA comment 14:50:49 https://github.com/w3c/a11y-tracking/issues/318#issuecomment-5192566424 14:51:54 matatk: largely it says we're excited for the possibilities of this technology. However, we're concerned about the API in its current form. 14:53:54 ... the declarative version of the API looks like a better starting point and we'd like to see that experimentation. We don't want it to cause interference with the axtree. We'd like to see the form submission behavior to allow review by the user. 14:54:35 ... please review that comment and put your feedback on the thread. 14:56:44 https://heydonworks.com/article/poisoning-well/ we need to pay some attention to how this sentiment might influence experimentation 14:58:44 zakim, end meeting 14:58:44 As of this point the attendees have been JonCohn, gpellegrino, janina, PaulG, matatk, Roy_Ruoxi, Vanessa, Neha 14:58:46 RRSAgent, please draft minutes 14:58:48 I have made the request to generate https://www.w3.org/2026/08/05-apa-minutes.html Zakim 14:58:54 I am happy to have been of service, PaulG; please remember to excuse RRSAgent. Goodbye 14:58:54 Zakim has left #apa 15:01:27 rrsagent, bye 15:01:27 I see no action items