18:07:10 <RRSAgent> RRSAgent has joined #aria-at
18:07:15 <RRSAgent> logging to https://www.w3.org/2024/11/06-aria-at-irc
18:07:15 <Zakim> RRSAgent, make logs Public
18:07:16 <Zakim> please title this meeting ("meeting: ..."), jugglinmike
18:07:31 <jugglinmike> meeting: ARIA and Assistive Technologies Community Group Weekly Teleconference
18:07:35 <jugglinmike> present+ jugglinmike
18:07:39 <jugglinmike> scribe+ jugglinmike
18:07:51 <howard-e> howard-e has joined #aria-at
18:07:54 <jugglinmike> present+ howard-e
18:07:56 <howard-e> present+
18:07:57 <jugglinmike> present+ IsaDC
18:08:02 <jugglinmike> present+ Hadi
18:08:10 <jugglinmike> present+ james
18:08:17 <jugglinmike> present+ mfairchild
18:09:06 <jugglinmike> Topic: Review agenda and next meeting dates
18:09:28 <jugglinmike> https://github.com/w3c/aria-at/wiki/November-6%2C-2024-Agenda
18:09:33 <jugglinmike> present+ mk
18:09:45 <jugglinmike> mk: This agenda is largely a copy of last week
18:10:24 <jugglinmike> mk: I've specifically omitted the issue during the second half of last week's call
18:10:44 <jugglinmike> mk: That's really important because it's blocking everything related to menu at the moment, but I feel unprepared to move beyond where we ended up last week
18:11:11 <jugglinmike> mk: Is there anything else that should be on the agenda?
18:11:28 <jugglinmike> mk: Hearing none, we'll stick with it as-is
18:11:34 <jugglinmike> mk: Next Community Group Meeting: Thursday November 14
18:11:56 <jugglinmike> mk: I'm still planning on a meeting for the following week, on November 20
18:12:51 <jugglinmike> mk: The following week, however, the meeting falls on the day of Thanksgiving here in the US--Thursday, November 28. I have cancelled that meeting
18:13:01 <jugglinmike> mk: Next AT Driver Subgroup meeting: Monday December 9
18:13:11 <jugglinmike> Topic: Current status
18:13:26 <jugglinmike> mk: We haven't moved anything since last week; I included this item largely for visibility
18:14:07 <jugglinmike> mk: IsaDC, I sent a list of plans that I think are all pretty lightweight lifts in terms of getting into the test queue for next week. Is that something you could focus on?
18:14:40 <jugglinmike> IsaDC: Yes, in fact the next radio button is ready for review already (I created the pull request only recently). That should be quite straightforward
18:14:56 <jugglinmike> IsaDC: It's very similar to the radio button with aria-activedescendent
18:15:04 <jugglinmike> IsaDC: Both links--yes
18:15:13 <jugglinmike> IsaDC: I'm not going to make any promises on disclosure
18:15:25 <jugglinmike> IsaDC: Vertical temperature slider, though, that's a "yes"
18:15:47 <jugglinmike> mk: Got it
18:16:07 <jugglinmike> mk: So we can potentially next week add four to the queue and have people ready to test them
18:16:47 <jugglinmike> mk: Hadi, as one of our primary JAWS testers, is there's any chance that you could help out here between next Thursday and the end of the month?
18:16:54 <jugglinmike> Hadi: Sure. Simply assign me, and I will do it
18:17:03 <jugglinmike> mk: Great. We'll check in with you on those next week
18:17:29 <jugglinmike> Topic: Testing Disclosure Navigation Menu
18:18:25 <jugglinmike> mk: Right now, we have four conflicts in the JAWS results
18:18:33 <jugglinmike> mk: I haven't reviewed these conflicts, yet
18:18:49 <jugglinmike> IsaDC: We reviewed them last week. It's me having to change my results and changing the impact to moderate
18:18:59 <jugglinmike> mk: Ah, so we already aligned on them
18:19:10 <jugglinmike> IsaDC: That's right. It's just the VoiceOver conflicts
18:19:28 <jugglinmike> mk: I believe that's just about Dean having to re-do the work
18:19:58 <jugglinmike> mk: And NVDA is published
18:20:09 <jugglinmike> mk: So that one's awesome
18:20:32 <jugglinmike> mk: Since we know the path forward on the JAWS one, it seems like you will be able to publish JAWS, IsaDC, and then we'd just be waiting for Dean
18:20:35 <jugglinmike> IsaDC: That's right
18:21:10 <jugglinmike> mk: Unfortunately we don't have Dean here today. It might be good to nudge him, IsaDC. I just want to get this out of the test queue because we don't have any technical issues blocking us, here
18:22:02 <jugglinmike> Topic: Testing navigation menu button
18:22:13 <jugglinmike> mk: for this one, I did take a look at the conflicts that are there.
18:22:38 <jugglinmike> mk: I didn't look at all ten conflicts, but I'm pretty sure they're all related to the issue we were talking about last week with hints
18:23:00 <jugglinmike> mk: Again, I don't want to talk about that issue today. I'd prefer to prepare more and have a fuller discussion next wek
18:23:27 <jugglinmike> mk: I think I have three or four options; I'd like to write those up along with trade-offs and risks and share that with folks to help reach a conclusion
18:23:35 <jugglinmike> mk: That's apparently affecting only VoiceOver
18:23:59 <jugglinmike> mk: This is where we're currently waiting on Hadi. It looks like Hadi hasn't started it, yet
18:24:17 <jugglinmike> Hadi: I wasn't aware that I had been assigned to this
18:24:30 <jugglinmike> Hadi: I can work on that this week, probably by the end of this weekend
18:24:45 <jugglinmike> Hadi: Next week, I will be attending a conference, so I'll make sure I finish this work before I go there
18:25:08 <jugglinmike> Hadi: I will be attending the conference from Tuesday until Friday. I won't be attending next week's meeting
18:25:25 <jugglinmike> Topic: Testing Action menu button with element.focus
18:25:32 <jugglinmike> IsaDC: I haven't started, yet
18:25:57 <jugglinmike> mk: I don't think we have people assigned
18:26:09 <jugglinmike> isaDC: I think Joe offered to run some tests, possibly with NVDA
18:26:17 <jugglinmike> mk: It looks like we have some VoiceOver Bot problems
18:26:35 <jugglinmike> mk: The VoiceOver Bot had one test error, zero tests completed, zero tests queues, and ten tests cancelled
18:26:53 <jugglinmike> IsaDC: Ah, that's because I ran it when adding the test plan to the queue
18:27:07 <jugglinmike> IsaDC: Could you try to assign me and see if it runs?
18:27:33 <jugglinmike> mk: I'm surprised to find that the "manage" button isn't present...
18:28:37 <jugglinmike> mk: I'm definitely signed in
18:28:43 <jugglinmike> IsaDC: I can see the "manage" button with Safari
18:28:56 <jugglinmike> IsaDC: For me, it says one test error
18:29:45 <jugglinmike>  IsaDC: And the test plan run has no AT responses
18:30:05 <jugglinmike> mk: Now, it says it's assigned to IsaDC
18:30:29 <jugglinmike> howard-e: I'm seeing that status--one test error
18:30:40 <jugglinmike> mk: Why wasn't there a "manage" button for me?
18:30:59 <jugglinmike> howard-e: Here, I'm seeing that it's now assigned to IsaDC
18:31:07 <jugglinmike> mk: Right, she just changed the assignment
18:31:26 <jugglinmike> howard-e: Could you use the "assign" menu to assign the VoiceOver bot?
18:31:43 <jugglinmike> howard-e: Whatever that previous run was, it definitely failed since it had 10 cancelled
18:31:58 <jugglinmike> IsaDC: I'm going to delete that run
18:32:00 <jugglinmike> howard-e: Could you try creating a new one?
18:32:03 <jugglinmike> IsaDC: Sure
18:32:37 <jugglinmike> mk: First-letter menu navigation does not work in that menu. If I type "v" to go to "VoiceOver Bot", it doesn't go there
18:32:46 <jugglinmike> mk: Maybe I should raise that as a bug for these menus...
18:33:54 <jugglinmike> mk: I thought there was supposed to be a button in the "status" column named "Manage Bot Run" which would have allowed you to re-run it
18:34:08 <jugglinmike> howard-e: That definitely should have been there. I'm still not sure why it didn't show for you
18:35:20 <jugglinmike> mk: Given that we only have Hadi here (we don't have Joe or Dean or Alyssa or anyone else), and given that we want Hadi to focus on the navigation menu button right now, I don't think we should assign any people to this plan today
18:35:51 <jugglinmike> IsaDC: Okay, the VoiceOver Bot seems to be working
18:36:14 <jugglinmike> IsaDC: Oh, no, the output is still blank
18:36:27 <jugglinmike> jugglinmike: It does take some time to collect AT responses
18:36:47 <jugglinmike> howard-e: I can confirm that the job is still running in the GitHub Action
18:37:15 <jugglinmike> mk: What I see in the test queue right now is that it is assigned to IsaDC right now and that there are 0 tests evaluated
18:37:35 <jugglinmike> mk: This seems like a bug; the test plan should still be assigned to IsaDC
18:37:56 <jugglinmike> mk: You normally can't re-assign it to a person until the test plan run is complete
18:38:12 <jugglinmike> IsaDC: It said "11 tests queued" and it allowed me to assign it to myself
18:38:19 <jugglinmike> howard-e: That shouldn't be possible
18:39:57 <jugglinmike> IsaDC: It's a bug. Before, I could see when the bot was still running, and it wouldn't let me assign or do anything. Now, it was showing as if it finished the run, and I could assign myself (even though it wasn't actually complete)
18:40:05 <jugglinmike> mk: There's something to look into there
18:40:13 <jugglinmike> howard-e: I will raise an issue for this
18:40:25 <jugglinmike> mk: I think we got through everything that's on the agenda for today
18:40:40 <jugglinmike> mk: What's going to happen to the particular run that's executing right now?
18:40:53 <jugglinmike> howard-e: I see that the results are being populated right now. It's moved on to test 3
18:41:13 <jugglinmike> mk: Hopefully, IsaDC, if you come back later, you will find output there. You can run it again and assign it to Joe
18:41:17 <jugglinmike> IsaDC: Understood
18:44:08 <jugglinmike> s/ IsaDC: /IsaDC: /
18:44:22 <jugglinmike> Zakim, end the meeting
18:44:22 <Zakim> As of this point the attendees have been jugglinmike, howard-e, IsaDC, Hadi, james, mfairchild, mk
18:44:24 <Zakim> RRSAgent, please draft minutes
18:44:25 <RRSAgent> I have made the request to generate https://www.w3.org/2024/11/06-aria-at-minutes.html Zakim
18:44:32 <Zakim> I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent.  Goodbye
18:44:32 <Zakim> Zakim has left #aria-at
18:44:38 <jugglinmike> RRSAgent, leave
18:44:38 <RRSAgent> I see no action items