20:02:41 RRSAgent has joined #aria-at 20:02:45 logging to https://www.w3.org/2024/01/11-aria-at-irc 20:02:47 rrsagent, make log public 20:02:54 Zakim, start the meeting 20:02:54 RRSAgent, make logs Public 20:02:56 please title this meeting ("meeting: ..."), jugglinmike 20:03:16 meeting: ARIA and Assistive Technologies Community Group Weekly Teleconference 20:03:22 present+ jugglinmike 20:03:26 scribe+ jugglinmike 20:03:51 present+ 20:05:31 3 of us got in 20:06:29 I clicked jion from the email that was sent out 20 minutes ago 20:08:16 howard-e has joined #aria-at 20:08:23 present+ 20:11:07 Topic: Manual testing progress check-in 20:11:38 Matt_King: We have four plans that we're trying to get new versions into "candidate review" 20:12:01 Matt_King: Alert, command button, link, and toggle button 20:12:50 Joe_Humbert: I use VoiceOver completely up-to-date. I have NVDA on my personal machine, but I'll have to check if it's completely up to date 20:13:09 Joe_Humbert: I do not have JAWS 20:13:44 Matt_King: That's very helpful; we have folks who can test with JAWS 20:14:00 Matt_King: We don't have anyone assigned to Command Button with VoiceOver besides Isabel 20:14:14 Matt_King: Isabel completed a run for Command Button, so we only need one additional tester 20:15:14 Matt_King: It looks like Alert might be ready to advance to candidate, now 20:15:40 Joe_Humbert: It might be due to the testing I completed just before Christmas. I can't recall which test plans I ran, though. 20:16:34 Joe_Humbert: Out of curiousity, is there a way for me to see what I've already tested? 20:16:46 Matt_King: Not at the moment 20:17:20 Joe_Humbert: As soon as you change the phase, it leaves the Test Queue, and I no longer have a way to see what I've done 20:18:02 Joe_Humbert: It's not a big deal for me, though 20:18:27 Matt_King: It would also be useful for administration, if only to recognize the contributions of all the volunteers 20:18:52 Matt_King: I've made a note of this to myself; I'll raise an issue at least (though I don't know where it fits in the roadmap) 20:19:41 Matt_King: I want to prioritize VoiceOver and Safari for the remaining three: command button, link, and alert 20:20:27 Joe_Humbert: I can do all three no problem. I might not be able to complete them by next week, but I can certainly complete them by the next meeting on 2024-01-25 20:20:47 Matt_King: That's awesome! You can go ahead and use the "assign yourself" button on https://aria-at.w3.org 20:21:23 Matt_King: Please try to complete them in alphabetical order 20:21:36 Matt_King: I have a meeting with Vispero on the 24th. If you could get a few done before then, that would be very helpful 20:21:46 Joe_Humbert: I think that's definitely possible 20:22:00 Matt_King: Great! 20:22:17 Topic: Upcoming app updates 20:22:49 Matt_King: The plan is to deploy into production on 2024-01-22 with the NVDA automation 20:22:54 howard-e: That's right 20:23:21 Matt_King: We also have some bug fixes. I haven't reviewed the entire list of everything that needs to be tested on the "sandbox" server yet, though 20:23:37 howard-e: I think "staging" is where the bug fixes are, now 20:24:09 howard-e: The "sandbox" server is running the automation work right now, which is currently on a distinct branch of development from the bug fixes 20:24:16 Matt_King: Ah, yes, I remember that, now 20:25:10 howard-e: That includes the "key up" work. Also, there was an issue with the test results not being properly migrated when there was a new R&D version pushed. The fix for that should be included, too 20:25:23 howard-e: I think there are some other details, as well. 20:25:36 howard-e: We should be able to support the v2 test report page, as well 20:25:55 howard-e: There are a couple things that would also be important, but I don't think they will be a part of "staging" necessarily 20:26:09 howard-e: For instances, supporting "level 0" assertions, and also capturing severity 20:26:54 howard-e: Those are pull requests that exist for ARIA-AT, not the App. But once those changes in ARIA-AT land, then we should be ready to move on the corresponding updates to ARIA-AT App 20:27:15 howard-e: Everything I'm mentioning here, I'll push to staging toward the end of the day 20:27:25 Matt_King: If you could send me an e-mail when you do, that would be great 20:27:39 Matt_King: I'm looking forward to announcing those changes 20:28:00 Matt_King: Joe_Humbert do you have any feedback about the new content in the data collection form? 20:28:22 Joe_Humbert: It seemed fine. I haven't come across any unexpected behavior, yet, though. That will be the true test 20:28:36 Matt_King: Ah, okay, though we don't have those specific changes deployed yet 20:28:51 Joe_Humbert: Having fewer tests overall was definitely nice 20:29:15 Topic: Targets for 2024 H1 20:29:48 Matt_King: I have a proposal here in the agenda. The first part is a breakdown for what I'd like to see from a testing perspective 20:30:19 Matt_King: It's "6+ test plans achieve recommended status," and we're well on our way for that 20:31:25 Matt_King: For the next set of testing, we'll go back to using our prioritization method 20:32:21 Matt_King: I'm hoping we have enough people to get all that testing done before the middle of April 20:32:51 Matt_King: Then we'll have a long tail of stuff that we can get into the "draft review" phase and ready for the "candidate" phase 20:33:21 Matt_King: I think we'll need more people present in this meeting before we can have a meaningful conversation about whether this plan is too aggressive or not aggressive enough 20:33:43 Matt_King: We still have a lot of talking to do about the details of the App development 20:33:58 Matt_King: But I've laid out some goals in broad strokes on today's agenda 20:34:29 Matt_King: Total: refactoring and testing complete for at least 20 test plans. 20:34:44 Matt_King: 2. 12 to 20 test plans have AT support tables in APG. 20:34:48 Matt_King: 3. APG AT support tables are redesigned to show must/should/may counts. 20:34:51 Matt_King: 4. Automation is updating data for each new release of JAWS, NVDA, and VoiceOver. 20:34:54 Matt_King: 5. Report site shows trends for each AT. 20:35:05 s/Total: /1. Total: / 20:36:06 Matt_King: When I meet with the folks at Vispero, I'll be speaking with them about their recent efforts to run the tests automatically 20:36:38 Matt_King: I believe they have some technical questions, so I'll be sure to connect them to howard-e and jugglinmike to discuss 20:38:29 Joe_Humbert: It'd be nice to get manual test results from Vispero in addition to the two volunteer-reported results 20:39:20 jugglinmike: And Z has started on the VoiceOver work. I don't have a sense for when that will be ready for production, though 20:40:05 Matt_King: As for the fifth goal: we want to be able to understand how interop data has changed over time, both at a high level and for any given test plan 20:40:20 Matt_King: That's another thing we're hoping to complete before June 30 20:41:04 Matt_King: We launched the first version of the support tables in time for Global Accessibility Awareness Day, so I'm thinking it could be nice to launch version two of those tables in time for the even this year 20:42:05 howard-e: Sounds good! I'm especially looking forward to being able to surface trends and progress 20:42:45 Zakim, end the meeting 20:42:45 As of this point the attendees have been jugglinmike, Joe_Humbert, howard-e 20:42:47 RRSAgent, please draft minutes 20:42:49 I have made the request to generate https://www.w3.org/2024/01/11-aria-at-minutes.html Zakim 20:42:56 I am happy to have been of service, jugglinmike; please remember to excuse RRSAgent. Goodbye 20:42:56 Zakim has left #aria-at 20:42:59 RRSAgent, leave 20:42:59 I see no action items