12:50:24 RRSAgent has joined #apa 12:50:28 logging to https://www.w3.org/2026/06/03-apa-irc 12:50:28 RRSAgent, make logs Public 12:50:29 please title this meeting ("meeting: ..."), janina 12:50:42 Meeting: APA Weekly Teleconference 12:50:49 Date: 03 Jun 2026 12:50:54 Chair: Matthew 12:50:59 agenda+ Agenda Review & Announcements 12:50:59 agenda+ [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) 12:50:59 agenda+ New charters review 12:50:59 agenda+ New on TR 12:51:01 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 12:51:04 agenda+ [Issue tracking](https://github.com/w3c/a11y-tracking/issues) 12:51:06 agenda+ CSS Update (Paul) 12:51:09 agenda+ Other business 12:51:11 agenda+ Be done 12:51:34 /join #rqtf 13:48:50 PaulG has joined #apa 14:00:35 Dr_Keith has joined #apa 14:00:44 present+ 14:01:02 present+ 14:01:17 matatk has joined #apa 14:01:23 present+ 14:01:27 rrsagent, make minutes 14:01:29 I have made the request to generate https://www.w3.org/2026/06/03-apa-minutes.html matatk 14:01:36 present+ 14:04:15 tsaulter has joined #apa 14:04:23 present+ 14:04:48 zakim, next item 14:04:48 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 14:04:56 scribe+ 14:05:03 Neha has joined #apa 14:05:06 subtopic: WAI Coordination 14:06:23 matatk: Notes restart of WAI Coordination calls 14:06:45 https://www.w3.org/WAI/update/ 14:06:54 matatk: Addressing issues that cut across WAI groups and common interests 14:07:06 matatk: Above link shows WAI activities 14:07:22 present+ 14:08:42 matatk: Notes a reprise of Authoring Tools Working Group is pending; proposed charter coming soon 14:09:20 matatk: Desire is to update with something normative, i.e. ATAG++ 14:09:40 matatk: Will look at incorporating AI 14:09:57 q? 14:10:56 matatk: Please inform APA Chairs if something that should be a topic for WAI coordination 14:11:46 matatk: Notes WHAT-WG has regular meetings. Should some of us attend? 14:12:17 q? 14:16:20 janina: I'll be attending IETF late July 14:16:28 janina: More to follow on that 14:16:58 q? 14:17:06 zakim, next item 14:17:06 agendum 2 -- [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) -- taken up [from janina] 14:17:40 matatk: Deadline looming to name who we want cross-group mtg with at TPAC 14:17:48 matatk: Due 17 June 14:18:24 matatk: Working on enhancing my scheduling tool from last year to be even more functional for us 14:19:27 matatk: Suggest reminding TF of the requested 17 June deadline 14:19:34 matatk: We should discuss next week here 14:19:39 q? 14:19:50 zakim, next item 14:19:50 agendum 3 -- New charters review -- taken up [from janina] 14:20:42 subtopic: Browser Tools and Testing 14:20:45 scribe+ 14:20:55 Roy_Ruoxi: They are planning to drop AT-Driver 14:21:02 Roy_Ruoxi: Have let ARIA know 14:21:12 Roy_Ruoxi: Notes effort (or accidental?) drop of A11y Driver 14:21:35 matatk: Definitely a concern; project seemed to be going well 14:21:58 Roy's comment: https://github.com/w3c/strategy/issues/558#issuecomment-4602323737 14:23:11 matatk: Notes David Burns pointed to another approach option; so discussion progressing over this 14:23:41 matatk: Don't think it's dropped officially yet or because it's flawed. Rather the usual time/resources 14:24:19 q? 14:24:46 agenda? 14:24:54 zakim, close this item 14:24:54 agendum 3 closed 14:24:55 I see 6 items remaining on the agenda; the next one is 14:24:55 4. New on TR [from janina] 14:25:01 zakim, drop item 4 14:25:01 agendum 4, New on TR, dropped 14:25:05 agenda? 14:25:40 zakim, next item 14:25:40 agendum 5 -- [Spec review requests](https://github.com/w3c/a11y-request/issues) -- taken up [from janina] 14:26:07 subtopic: Digital Credentials 14:26:11 due 2026-07-14 14:26:20 https://github.com/w3c/a11y-tracking/issues/325 14:26:52 matatk: Is an API to facilitate presentation and verification of credentials 14:27:14 matatk: Could be wide ranging application 14:27:21 matatk: A concert ticket ... 14:27:32 matatk: A governmentally issued ID 14:27:48 matatk: Would integrate and store in a digital wallet 14:28:28 matatk: So api provides for some mediation and interaction 14:28:52 matatk: May replace holding a passport up to the camera 14:29:22 matatk: Could be age verification 14:29:26 q+ 14:32:05 matatk: This not the selective disclosure of of verifiable credentials approach 14:33:05 matatk: Zero knowledge proof on the horizon -- would support selective 14:33:35 matatk: There are other systems 14:34:16 matatk: It's a complex area over all; this API is request and presentation of credentials 14:35:35 matatk: Work has been controversial; laws very; misuse a concern; but lots of legitimate use that could be empowering 14:36:09 matatk: W3C has chosen to be involved rather than not while work continued elsewhere 14:36:27 matatk: We need to focus on a11y; other groups will address other concerns 14:36:49 matatk: Some of what we might ask would be out of scope for our comment 14:37:27 matatk: We can still encourage use of more supportive approaches 14:37:58 matatk: the Accessibility Considerations section does include some normative provisions 14:38:11 matatk: We need to look for what might be missing 14:38:11 q? 14:38:14 q? 14:38:18 ack ja 14:38:53 q? 14:39:26 matatk: Status is beyond FPWD; is wanting CR 14:39:48 matatk: It's a formal review request 14:40:08 PaulG: Is the credential or the mechanism for accessing/mediating? 14:40:16 matatk: The latter -- the API 14:40:51 matatk: Certain ISO formats have been chosen by gov entities; so choices already made 14:41:50 paul: Is it challenge and wallet? 14:42:04 matatk: yes, both sides of the communication 14:44:00 matatk: My guess that this relies on browser UI; so browser for wallet management 14:45:48 PaulG: concerned how we manage for users who may have multiple wallets on multiple devices; how do you know what's what? 14:46:01 PaulG: potential for frustration is high 14:46:20 PaulG: You need confidence request is from a trusted source 14:46:40 q+ 14:47:36 PaulG: may have passwords in multiple managers; this can get complicated 14:48:01 PaulG: User needs to know who's asking; and we need confidence our end to end concerns are covered somewhere 14:49:28 janina: We need to know who's supporting what. 14:49:40 janina: It's often not clear who's asking for a password, when you have n windwos open. 14:50:15 janina: Password managers not always reliable; old credentials don't die easily 14:50:58 janina: who's asking is important; if there's any challenge-response going on it's vital we can trust it 14:51:47 PaulG: agrees; who's asking and do we trust their request? How to get more detail because we're concerned over spoofing 14:53:14 janina: Also user initiated expire and delete 14:53:26 matatk: boundaries are unclear and important they be clarified 14:54:09 matatk: I'll distill into our tracking thread from these notes as we figure out next steps 14:54:23 matatk: Would be good for us to file issues and do so early 14:55:51 janina: similar to the notification with just an OK option; but no good access to content or Esc to dismiss 14:55:57 PaulG: What about COGA docs? 14:55:59 matatk: yes 14:56:28 matatk: This will come back for us to continue 14:56:38 matatk: Thanks for a good conversation 14:56:49 zakim, end meeting 14:56:49 As of this point the attendees have been Dr_Keith, PaulG, matatk, janina, tsaulter, Neha 14:56:51 RRSAgent, please draft minutes 14:56:52 I have made the request to generate https://www.w3.org/2026/06/03-apa-minutes.html Zakim 14:56:58 I am happy to have been of service, janina; please remember to excuse RRSAgent. Goodbye 14:56:59 Zakim has left #apa 14:57:00 rrsagent, bye 14:57:00 I see no action items