19:10:47 RRSAgent has joined #aria-at 19:10:52 logging to https://www.w3.org/2025/10/20-aria-at-irc 19:10:52 RRSAgent, make logs Public 19:10:53 please title this meeting ("meeting: ..."), ChrisCuellar 19:10:58 meeting: ARIA-AT AT Driver Subgroup Monthly Teleconference 19:11:10 present+ 19:11:12 scribe+ 19:11:16 present+ jugglinmike 19:11:33 present+ Matt_King 19:11:50 present+ Michael_Fairchild 19:12:27 topic: review agenda 19:13:05 jugglinmike: Our next meeting is set for TPAC week, so we should push back to at least Nov 17. 19:13:16 ... I'll figure out what to do about that offline. 19:14:06 ... The next BTT meeting might happen on Wednesday, November 12, 2025. They won't be at TPAC, so it's possible that will meet on that date regardless of TPAC conflicts. 19:15:14 topic: Update on Edge support in ARIA-AT 19:16:04 jugglinmike: Bocoup has been progress there in landing Edge support. We've landed support in the harness. We have a PR open to get this into Github actions as well. 19:16:43 scribe+ jugglinmike 19:16:55 ChrisCuellar: We want to get the UI work on Edge support done ASAP 19:17:12 ChrisCuellar: Bocoup is a running a little light this week in terms of staff 19:17:22 ChrisCuellar: But we hope to get the change in by next week 19:17:32 Matt_King: why do we need UI work to add a browser? 19:17:45 ChrisCuellar: I don't recall the specifics, but I do know that Corey at Bocoup is assigned to do that work 19:18:04 scribe+ ChrisCuellar 19:18:07 Matt_King: Well, "report by attribute" is a way higher priority for ARIA-AT App 19:19:10 Matt_King: That's good news. Vispero will be happy to get Edge support. If we can get our verdict assignment to be browser-agnostic, that might speed up report publishing as well. I'll be curious to see how the reports differ on Edge from Chrome. 19:20:25 jugglinmike: As a web developer, I'll be curious to see more generally which AT's pair better with which browsers. 19:20:37 topic: Updates to AT Driver specification 19:22:14 jugglinmike: Some time ago, we had feedback from Vispero to make the spec easier to read with JSON examples of commands, like creating a new session, or getting/updating a setting. I landed that last week. That was great feedback and it sets precedent for how to write future normative text in the spec. 19:23:42 ... I have not received any input yet on the issue I posted about screen reader speech interruptions. 19:24:43 ... We're trying to learn what's realistic to expect in terms of specifying how AT's should behave when handling speech interruptions. 19:25:15 ... I'll make it a priority to poke people on that at TPAC. 19:25:24 topic: Feedback on proposal to engage with Apple on AT Driver 19:26:00 jugglinmike: A few months ago, we shared some thoughts on opportunities to collaborate with Apple's accessibility team to advance AT Driver. 19:26:41 ... This is sort of fell off the radar. I just wanted to make sure there wasn't anything else actionable here before TPAC. 19:29:16 Matt_King: We definitely have limited bandwidth right now and I'm not sure we can add anything new to our plate at the moment. 20:02:10 Zakim, end the meeting 20:02:10 As of this point the attendees have been ChrisCuellar, jugglinmike, Matt_King, Michael_Fairchild 20:02:12 RRSAgent, please draft minutes 20:02:13 I have made the request to generate https://www.w3.org/2025/10/20-aria-at-minutes.html Zakim 20:02:20 I am happy to have been of service, ChrisCuellar; please remember to excuse RRSAgent. Goodbye 20:02:20 Zakim has left #aria-at 20:03:22 ChrisCuellar has joined #aria-at 20:09:21 RRSagent, leave 20:09:21 I see no action items