Meeting minutes
Review agenda and next meeting dates
https://
mk: This agenda is largely a copy of last week
mk: I've specifically omitted the issue during the second half of last week's call
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
mk: Is there anything else that should be on the agenda?
mk: Hearing none, we'll stick with it as-is
mk: Next Community Group Meeting: Thursday November 14
mk: I'm still planning on a meeting for the following week, on November 20
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
mk: Next AT Driver Subgroup meeting: Monday December 9
Current status
mk: We haven't moved anything since last week; I included this item largely for visibility
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?
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
IsaDC: It's very similar to the radio button with aria-activedescendent
IsaDC: Both links--yes
IsaDC: I'm not going to make any promises on disclosure
IsaDC: Vertical temperature slider, though, that's a "yes"
mk: Got it
mk: So we can potentially next week add four to the queue and have people ready to test them
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?
Hadi: Sure. Simply assign me, and I will do it
mk: Great. We'll check in with you on those next week
Testing Disclosure Navigation Menu
mk: Right now, we have four conflicts in the JAWS results
mk: I haven't reviewed these conflicts, yet
IsaDC: We reviewed them last week. It's me having to change my results and changing the impact to moderate
mk: Ah, so we already aligned on them
IsaDC: That's right. It's just the VoiceOver conflicts
mk: I believe that's just about Dean having to re-do the work
mk: And NVDA is published
mk: So that one's awesome
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
IsaDC: That's right
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
Testing navigation menu button
mk: for this one, I did take a look at the conflicts that are there.
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
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
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
mk: That's apparently affecting only VoiceOver
mk: This is where we're currently waiting on Hadi. It looks like Hadi hasn't started it, yet
Hadi: I wasn't aware that I had been assigned to this
Hadi: I can work on that this week, probably by the end of this weekend
Hadi: Next week, I will be attending a conference, so I'll make sure I finish this work before I go there
Hadi: I will be attending the conference from Tuesday until Friday. I won't be attending next week's meeting
Testing Action menu button with element.focus
IsaDC: I haven't started, yet
mk: I don't think we have people assigned
isaDC: I think Joe offered to run some tests, possibly with NVDA
mk: It looks like we have some VoiceOver Bot problems
mk: The VoiceOver Bot had one test error, zero tests completed, zero tests queues, and ten tests cancelled
IsaDC: Ah, that's because I ran it when adding the test plan to the queue
IsaDC: Could you try to assign me and see if it runs?
mk: I'm surprised to find that the "manage" button isn't present...
mk: I'm definitely signed in
IsaDC: I can see the "manage" button with Safari
IsaDC: For me, it says one test error
IsaDC: And the test plan run has no AT responses
mk: Now, it says it's assigned to IsaDC
howard-e: I'm seeing that status--one test error
mk: Why wasn't there a "manage" button for me?
howard-e: Here, I'm seeing that it's now assigned to IsaDC
mk: Right, she just changed the assignment
howard-e: Could you use the "assign" menu to assign the VoiceOver bot?
howard-e: Whatever that previous run was, it definitely failed since it had 10 cancelled
IsaDC: I'm going to delete that run
howard-e: Could you try creating a new one?
IsaDC: Sure
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
mk: Maybe I should raise that as a bug for these menus...
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
howard-e: That definitely should have been there. I'm still not sure why it didn't show for you
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
IsaDC: Okay, the VoiceOver Bot seems to be working
IsaDC: Oh, no, the output is still blank
jugglinmike: It does take some time to collect AT responses
howard-e: I can confirm that the job is still running in the GitHub Action
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
mk: This seems like a bug; the test plan should still be assigned to IsaDC
mk: You normally can't re-assign it to a person until the test plan run is complete
IsaDC: It said "11 tests queued" and it allowed me to assign it to myself
howard-e: That shouldn't be possible
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)
mk: There's something to look into there
howard-e: I will raise an issue for this
mk: I think we got through everything that's on the agenda for today
mk: What's going to happen to the particular run that's executing right now?
howard-e: I see that the results are being populated right now. It's moved on to test 3
mk: Hopefully, IsaDC, if you come back later, you will find output there. You can run it again and assign it to Joe
IsaDC: Understood