17:00:11 RRSAgent has joined #aria-at 17:00:15 logging to https://www.w3.org/2024/06/05-aria-at-irc 17:00:22 rrsagent, make log public 17:01:16 Zakim, start the meeting 17:01:16 RRSAgent, make logs Public 17:01:18 please title this meeting ("meeting: ..."), jugglinmike 17:01:37 meeting: ARIA and Assistive Technologies Community Group Weekly Teleconference 17:01:51 present+ jugglinmike 17:01:57 present+ hadi 17:02:03 present+ IsaDC 17:02:07 present+ howard-e 17:03:07 Matt_King has joined #aria-at 17:03:16 mmoss has joined #aria-at 17:04:58 howard-e has joined #aria-at 17:05:02 present+ 17:05:19 present+ Matt_King 17:05:27 present+ 17:05:27 present+ mmoss 17:05:32 scribe+ jugglinmike 17:06:31 Topic: Review agenda and next meeting dates 17:06:34 https://github.com/w3c/aria-at/wiki/June-5,-2024-Agenda 17:06:42 Matt_King: Requests for changes to agenda? 17:06:48 Matt_King: Hearing none, we'll keep it as-is 17:06:56 Matt_King: Next AT Driver Subgroup meeting: Monday June 10 17:07:03 Matt_King: Next community group meeting: Thursday June 13 17:07:15 Topic: Current status 17:07:22 Matt_King: Goal: 6 recommended plans by June 30 17:07:33 Matt_King: We're at risk in that goal, though we're making good progress 17:07:40 Matt_King: 5 plans in candidate review 17:07:55 Matt_King: three are in good shape--alert, command button, link: Approved by Vispero 17:08:14 Matt_King: As for the other two, toggle button and radio group, review is in-progress 17:08:33 Matt_King: Slider and menu button are in the queue; they'll be coming up later on 17:08:45 Topic: NVDA Bot issues 17:08:53 Matt_King: I think everything here is resolved, but I just wanted to verify 17:10:48 Matt_King: https://github.com/w3c/aria-at/issues/1070 seems to be resolved 17:12:00 IsaDC: I haven't had an opportunity to run anything with the NVDA bot since it was updated to the latest release of NVDA back in early May 17:12:19 IsaDC: That's because we manually corrected the problems which resulted from the use of the old versions 17:12:48 Matt_King: Okay, in that case, I'll close the issue related to the version of NVDA being used by the NVDA bot 17:12:59 Topic: Check in on dialog testing 17:13:14 Subtopic: Feedback: "Bump into the top edge of a modal dialog" (Modal Dialog Example, Test 8, V24.05.09) · Issue #1079 · w3c/aria-at 17:13:20 github: https://github.com/w3c/aria-at/issues/1079 17:13:29 Matt_King: IsaDC and I have been discussing this offline 17:13:50 Matt_King: I've been writing a comment regarding some of my thoughts, but I didn't have time to post that comment prior to this meeting 17:14:22 IsaDC: We're going to change the previous test--not only the nested dialog, but also bumping to the top of a "main" dialog? 17:14:31 Matt_King: Yeah, we want to change both the top and the bottom. 17:14:52 Matt_King: ...but rather than taking up meeting time, I'll add the comment and we can proceed from there 17:15:24 Subtopic: Conflicting JAWS results: "Close a modal dialog" Test 2 in V24.05.09 · Issue #1078 · w3c/aria-at 17:15:32 github: https://github.com/w3c/aria-at/issues/1078 17:15:43 Matt_King: It appears Hadi had an unusual experience with JAWS 17:16:12 Hadi: Yes! I tested three times, I closed the entire browser and restarted it. Nothing seems to change the outcome 17:16:28 Hadi: IsaDC didn't witness the same behavior as I did. 17:16:37 IsaDC: That's right; JAWS passed all the tests for me 17:16:53 Matt_King: I think we should compare the versions of JAWS and Chrome that Hadi and IsaDC are using 17:17:46 Matt_King: My browser just got updated; it's now at version 124. 17:18:04 Hadi: I don't have access to my testing machine, now, but I believe Chrome was at 125 for me 17:18:20 Matt_King: Ah, yes, Chrome is at 125 for me, too. 17:18:31 IsaDC: Hadi and I are both using Windows 11 17:19:25 IsaDC: On the 13th of May, we received an update for JAWS. Hadi and I both used the previous version. 17:19:54 Matt_King: When you used default settings, do you use "insert", "space", followed by "Z"? 17:19:56 Hadi: Yes 17:20:37 Hadi: I also try to reduce the risk of other factors impacting the results: I close other processes and make the browser window full screen 17:20:48 Hadi: The only thing I change is to increase the speaking speed 17:21:03 Matt_King: I just ran the test again, and I still get the same result as IsaDC 17:21:37 Hadi: I will be glad to test it again when I am in my home office. I'll let you know via e-mail whether the problem persisted 17:27:46 Hadi: Matt_King you can change my results for now. I'll test tonight, and I'll let you know what I find this time 17:28:10 Subtopic: Conflicting VoiceOver test results: "Close a modal dialog" (Modal Dialog Example, Test 6, V24.05.09) · Issue #1071 · w3c/aria-at 17:28:19 github: https://github.com/w3c/aria-at/issues/1071 17:28:28 Matt_King: I think we may be ready to close this 17:28:48 Matt_King: There was a discussion about whether or not it should say "main" 17:28:53 Matt_King: We discussed this last time 17:29:01 IsaDC: That's right, and I modified my results 17:29:39 Matt_King: Great; I'll close the issue 17:29:51 Subtopic: Conflicting VoiceOver test results: "Navigate to the top of a modal dialog" (Modal Dialog Example, Test 14, V24.05.09) · Issue #1072 · w3c/aria-at 17:30:04 github: https://github.com/w3c/aria-at/issues/1072 17:30:31 Matt_King: This is another VoiceOver conflict 17:30:43 IsaDC: We are fixing this. I didn't advance the test plan yet 17:30:53 Matt_King: I don't think we needed test plan changes for this one 17:31:05 Matt_King: the conflict was: how should we record the fact that the cursor didn't move? 17:31:18 Matt_King: I believe the resolution was that we were going to modify Joe's results 17:31:37 Matt_King: It looks like Joe did that because the app no longer reports conflicts 17:31:58 IsaDC: That's right. Now, there's only the issue about bumping 17:33:27 Matt_King: Bumping was a separate issue at the top of issue #1079 (we were summarizing everything related to dialog) 17:33:31 topic: Review upcoming test queue and report page changes 17:34:04 Matt_King: New test queue in sandbox https://aria-at-app-sandbox.bocoup.com/test-queue-2 17:34:21 Matt_King: The test queue will change next week in some really cool ways 17:34:40 Matt_King: IsaDC and I have both looked at this, and we agreed that we should deploy the heading and landmark structure as-is 17:35:06 Matt_King: When this change comes out next week, the test queue is going to look different 17:35:31 Matt_King: Right now, we have a table for JAWS and Chrome, a table for NVDA and Chrome, and a table for Safari and VoiceOver--all with headings for each 17:36:09 Matt_King: If you look at the new version available in the sandbox, you'll find that instead of having headings related to browser+screen reader combinations, you'll find headings for each test plan 17:36:59 Matt_King: If there are multiple versions of the same test plan in the test queue at the same time, under the level 2 heading, there is a button which is named for each version of the test plan and which expands with the relevant table 17:37:59 Matt_King: The biggest difference for testers is that because the test plan name doesn't have a column, you need to go to the actions section to find the button for "start testing" 17:38:12 Matt_King: Otherwise, the table is largely the same as what you're used to; it's just organized differently 17:38:44 Hadi: Is there a reason the name of the test plan is not a link? 17:39:14 Matt_King: That's because each test plan section describes multiple AT-browser combinations 17:40:52 Matt_King: In the future, it might be nice to have a filter like "show only test plans assigned to me" 17:42:42 Matt_King: Please give it a try, and be sure to share feedback on the usability in the coming weeks 17:52:02 Topic: APIs to support stakeholder use cases 17:52:17 Matt_King: Problem: We don't offer a robust way for AT vendors to integrate and maintain aria-at tests in their CI. 17:55:33 scribe+ Matt_King 17:55:41 TOPIC: VoiceOver and Safari Automation 17:55:49 https://github.com/w3c/aria-at/blob/625a22e13bd117c4bb8f7ecdb5e97454f9e935ac/tests/support.json#L91 17:58:23 scribe+ jugglinmike 17:58:40 Matt_King: In macOS 13, there was a "quickNavOn" setting, and the way to toggle it was the arrow keys 17:59:14 Matt_King: Then we added "singleLetterQuickNavOn" (and Off) and "arrowKeyQuickNavOn" (and Off) to support macOS 14 17:59:48 Matt_King: We kept the older setting in the JSON to continue to be compatible with macOS 13 18:00:30 Matt_King: in the most recent test files, we are only using the newest settings which are arrownav on/ff and letternav on/off 18:02:59 jugglinmike: I will submit a patch to extend the instructions for "quickNavOn" and "quickNavOff" to say something like, "when using macOS 13 and earlier" 18:03:17 Zakim, end the meeting 18:03:17 As of this point the attendees have been jugglinmike, hadi, IsaDC, howard-e, Matt_King, mmoss 18:03:19 RRSAgent, please draft minutes 18:03:20 I have made the request to generate https://www.w3.org/2024/06/05-aria-at-minutes.html Zakim 18:03:27 RRSAgent, leave 18:03:27 I see no action items 18:03:27 I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent. Goodbye 18:03:27 Zakim has left #aria-at