12:57:57 RRSAgent has joined #apa 12:58:02 logging to https://www.w3.org/2026/07/01-apa-irc 12:58:02 RRSAgent, make logs Public 12:58:03 please title this meeting ("meeting: ..."), janina 12:58:23 Meeting: APA Weekly Teleconference 12:58:29 Date: 01 Jul 2026 12:58:34 Chair: Matthew 12:58:38 agenda+ Agenda Review & Announcements 12:58:38 agenda+ [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) 12:58:38 agenda+ New charters review 12:58:38 agenda+ New on TR 12:58:38 agenda+ WebMCP - should it be adopted as W3C work? 12:58:41 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 12:58:43 agenda+ [Issue tracking](https://github.com/w3c/a11y-tracking/issues) 12:58:46 agenda+ CSS Update (Paul) 12:58:48 agenda+ Actions Checkin 12:58:51 agenda+ Other business 12:58:53 agenda+ Be done 13:01:46 janina has left #apa 14:01:22 janina has joined #apa 14:01:24 matatk has joined #apa 14:01:26 agenda? 14:01:32 present+ 14:02:53 Crispy has joined #apa 14:03:01 Present+ 14:03:43 PaulG has joined #apa 14:04:03 Neha has joined #apa 14:04:09 present+ 14:04:10 present+ 14:04:29 present+ 14:04:43 regrets: Eric_Hind, Gottfried_Zimmerman, Jennifer_Strickland, Marcelo_Paiva 14:04:45 present+ 14:05:05 zakim, next item 14:05:05 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 14:05:45 scribe+ 14:06:42 ICCHP coming up later this month: https://icchp.org/welcome-26/ 14:07:05 janina: But no remote participation, papers not yet published either 14:07:24 https://davidaustinm.github.io/prefigure/ 14:07:29 Dr_Keith has joined #apa 14:07:41 present+ 14:07:50 zakim, next item 14:07:50 agendum 2 -- [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) -- taken up [from janina] 14:08:20 Apply for funding! https://www.surveymonkey.com/r/W3C-Apply 14:08:35 rrsagent, make minutes 14:08:37 I have made the request to generate https://www.w3.org/2026/07/01-apa-minutes.html janina 14:09:48 zakim, next item 14:09:48 agendum 3 -- New charters review -- taken up [from janina] 14:10:01 Fazio6 has joined #apa 14:10:08 present+ 14:10:25 +1 TPAC is an awesome experience 14:10:40 A Nerd Utopia 14:11:14 subtopic: ATAG 14:11:15 https://github.com/w3c/strategy/issues/552 14:11:46 Fazio7 has joined #apa 14:12:05 Fazio has joined #apa 14:12:12 present+ 14:12:14 JonCohn has joined #apa 14:12:31 present+ 14:16:40 scribe+ 14:17:04 Group is supportive overall; would like to know the expected date for ATAG-next, but not a blocker. 14:18:37 Zakim, next item 14:18:37 agendum 4 -- New on TR -- taken up [from janina] 14:19:05 Zakim, close this item 14:19:05 agendum 4 closed 14:19:06 I see 7 items remaining on the agenda; the next one is 14:19:06 5. WebMCP - should it be adopted as W3C work? [from janina] 14:19:17 Zakim, next item 14:19:17 agendum 5 -- WebMCP - should it be adopted as W3C work? -- taken up [from janina] 14:19:51 Email for context: https://lists.w3.org/Archives/Public/public-apa/2026Jun/0019.html 14:22:10 via prompt to the user? 14:22:19 Good RQTF discussion today logged here: https://www.w3.org/2026/07/01-rqtf-minutes.html 14:22:33 q+ 14:22:37 q+ 14:24:15 no different than latover dilemma 14:24:24 layover 14:24:26 q? 14:24:30 q+ 14:25:06 +1 to excitement 14:25:37 q+ 14:26:28 matatk: Interested in adapting the interface to the user. This is a huge architectural overhall. Concerned about potential misuse and issues for users with AT. Maybe only for devs? What is the risk to the A11y tree? 14:26:40 Dr_Keith's view: https://lists.w3.org/Archives/Public/public-apa/2026Jun/0020.html 14:26:49 Dr_Keith email was very well worded 14:26:56 q? 14:27:00 ack PaulG 14:27:03 ack PaulG 14:27:56 PaulG: AI adopters possibly to get special access? Thinks we should take this on. 14:28:38 why does it need to be chartered? 14:28:42 matatk: Question is that this spec as is, do we adopt it? 14:29:02 PaulG: What are the options for us? 14:29:24 matatk: Adopt and it requires review, etc. 14:29:28 do all specs need to be chartered specifically? 14:29:38 Not adopt as it is, propose a different way. 14:29:57 If it is chartered it can still end up being deemed inappropriate in the end 14:30:05 They want to atleast investigate 14:30:11 q? 14:30:34 W3C needs excitement 14:30:40 This is exciting 14:30:45 PaulG: Concerned without eyes on it may get abused 14:31:36 Browser vendors may use this or partner with AT companies. It should be ubiquitous, yet private, and secure 14:32:34 All reasons to charter and police it 14:32:41 q? 14:32:53 matatk: Mentioned that there are position statements on this. Google are in favour, Mozilla said nothing to date, Safari object strongly. 14:32:56 ack janina 14:32:58 Ack janina 14:33:11 charter for exploratory review 14:33:39 Inclined to have discussion at least, but where and who. Not enough info for core group to handle this? 14:34:07 TPAC meeting on Wev MCP? 14:34:11 Web 14:34:37 Needs W3C involvement, but in what format? 14:35:10 Do we have a say in what WG takes it up? 14:35:14 matatk They already have the bandwidth and are already looking into it 14:35:34 charter us deep into the cross review 14:36:05 matatk: tremendous pressure to do this. Currently great risk to move this to recommendation. 14:36:35 q? 14:37:01 ack Fazio 14:37:24 janina: If they won't listen to the broader public maybe they aren't the right group to take it forward. 14:38:00 Fazio: Not too concerned with objections, but we should support the exploration 14:38:35 Chartering isn't endorsing, but must be explored 14:38:58 matatk: possible to charter exploring an issue we're not sure how to solve yet 14:39:13 David gave an example of this being done elsewhere 14:40:32 q? 14:40:44 matatk: This isn't an example of exploratory work. They have created the spec, no more research is due to be done. What they propose has too many issues from an A11y and security perspective. We need to clarify what we need to see happen. 14:40:49 David agrees 14:41:10 ack Dr_Keith 14:41:29 I support Dr_Keith's email 14:41:36 q? 14:41:51 Dr_Keith: agrees we should support it but we need to involve our comments as not fit for purpose as it stands 14:42:02 q+ 14:42:14 scribe+ 14:42:42 Crispy: I've gone through the emails; I think Leonie had some good input in the threads; I agree it is interesting but certainly from an accessibility point of view needs work. 14:42:43 q- 14:44:15 PaulG: WEbMCP can be helpful, gave a workflow example, highlights loads of other areas it can help. Get it to help the larger audience. Doesn't want to shelve it. 14:44:51 q? 14:45:08 agenda? 14:45:24 Zakim, take up item 7 14:45:24 agendum 7 -- [Issue tracking](https://github.com/w3c/a11y-tracking/issues) -- taken up [from janina] 14:45:49 subtopic: Open UI ::interest-button 14:45:51 https://github.com/w3c/a11y-tracking/issues/331 14:46:12 relevant bit of explainer: https://open-ui.org/components/interest-invokers.explainer/#option-35---add-an-opt-in-info-button-pseudo-element 14:48:52 regrets+ Chiara_Cerretti 14:52:05 matatk: Interest invokers - Explained the scenario for a pop-up on hover with stats on a person, press on link, go to full page user profile. Similarly, link on Github,gives info on pop-up, saves moving away from current place. Wiki does the same with references. This pattern to not follow a link to a page is quite common, trying to standardise 14:52:05 this. A11y management will all just work, but there are challenges. 1. Desktop with mouse works, on mobile hover might not be available. How to implement it? 2. Immersive platforms like Vision OS and Android XR - Look at link for a while and pop up may appear. Privacy issue on where the users are looking. 14:52:43 One technique - provide button - look at link and button pop asks if interested and user selects the button. 14:53:10 Ways around this. Button maybe provided by the user agent 14:54:12 How should this be styled by default? Opt in or Opt out by a media query? 14:56:34 PaulG: Concerns for User agent controlling that button, etc, and the default. Not enough modality use considered, we need to look at more. 14:57:05 Please comment with use cases/Qs/concerns on https://github.com/w3c/a11y-tracking/issues/331 so we can make an APA comment soon 14:57:57 matatk: Please comment by next week and add use cases if you have any. 14:58:37 We can illustrate to the group what they may not have considered. 14:58:56 zakim, end meeting 14:58:56 As of this point the attendees have been janina, Crispy, Neha, PaulG, Roy_Ruoxi, matatk, Dr_Keith, Fazio, JonCohn 14:58:59 RRSAgent, please draft minutes 14:59:01 I have made the request to generate https://www.w3.org/2026/07/01-apa-minutes.html Zakim 14:59:08 I am happy to have been of service, matatk; please remember to excuse RRSAgent. Goodbye 14:59:08 Zakim has left #apa 14:59:55 quit 15:04:17 janina has left #apa 15:04:37 Neha has left #apa 16:01:41 kizu has joined #apa 16:01:48 masonf has joined #apa 16:03:25 lea has joined #apa