Meeting minutes
[jokes and revelry]
Testing status and issues
Update on current testing progress
Alyssa: I can take "Navigation Menu Button" using NVDA and Firefox
Dylan: I can take "Navigation Menu Button" using JAWS and Firefox
Alyssa: instead, I'll take "Navigation Menu Button" using NVDA and Firefox and also JAWS and Firefox
Dylan: And I'll take "Navigation Menu Button" using Voiceover, along with "Modal Dialog" using VoiceOver
James_Scholes: Great! Thank you both
Test issue 948: "Read information about a slider in interaction mode" (Color Viewer Slider, Test 8)
github: w3c/
[the group reviews a conflict between results reported by Isabel and Dylan]
James_Scholes: I can replicate Isabel's results. If I switch to browse mode, then I observe the results reported by Dylan. I expect Dylan accidentally entered browse mode
Dylan: That seems likely. I'll verify and then update my results
Test Issue 947: "Open a nested modal dialog using a link in reading mode" (Modal Dialog Example, Test 27)
github: w3c/
[the group reviews a conflict between results reported by Isabel and Dylan]
James_Scholes: I can replicate Isabel's results. It sounds to me like JAWS isn't automatically switching to focus mode for Dylan
Dylan: No matter which mode I'm in, I get the same output. I can double-check, though. It's just that I'm not good a multi-tasking, so I'll follow-up after the meeting
Wiki updates
Matt_King: The first thing I did was to insert a "left navigation"
Matt_King: Now, instead of just a search box and a listing of all pages, the wiki has a structured navigation bar
[Matt_King gives a quick review of the contents of the navigation menu]
Matt_King: Next, I re-did the content of the home page
Matt_King: Including information for new members and information about meetings
Matt_King: I included a link to the W3C calendar, there
Matt_King: Most importantly, I added a table of key resources and repositories
Matt_King: It's not exhaustive, but it helps folks find the work that takes place across our various repositories, application deployments, and mailing lists
Matt_King: We've long been talking about a "welcome kit" for new members
Matt_King: I've added a link to such a kit for new members
Matt_King: The "kit" is just a draft, and I'm really interested in having other members take it and run with it
Matt_King: I don't expect much original content in this kit, but rather an ordered list of things to look at. A "step-by-step" list--it currently has seven items
Matt_King: It mentions getting authorized to run tests, but that is not a link. That's an area where it would be good to have other folks involved
James_Scholes: Given that we're currently trying to onboard three new people, we should take a look at this and hopefully get feedback from those people
James_Scholes: I'm glad to see this work happening!
Matt_King: As I was doing this, I organized a lot of the files in the wiki. GitHub Wikis are Git repositories under-the-hood, so anyone who works on the wiki as a Git repository will be able to see those improvements
Working mode process
Matt_King: Establish explicit test plan life cycle in working mode · Issue #950 · w3c/aria-at
github: w3c/
Matt_King: Essentially, what I want to do is document the lifecycle of a test plan version
Matt_King: this is critical because we have zero capability to edit tests within the system
Matt_King: That architecture allows us to bring tests in from other sources, so it's probably the direction we want to go in the long-term
Matt_King: I definitely want input from someone on the PAC team and someone on the Bocoup team. I'd also appreciate input from others
James_Scholes: you can assign it to me for the PAC side of things
jugglinmike: You can assign it to Carmen for the Bocoup side of things
App development
Appp Issue 632: Questions on proposed database changes to better support #518
github: w3c/
Matt_King: This is about the data model, so I wanted to call it to James_Scholes's attention
Matt_King: I've started to take a look at this, but I haven't had a chance to dive in deep
Matt_King: I think some parts will inform the next issue I'm bringing up in this meeting
App issue 648 - Design Missing Test Plan Status Management Functions
github: w3c/
Matt_King: We currently have this page called "TestManagement". Isaac has some mockups in gh-518 which we've previously discussed, but the designs aren't quite what I was thinking we need
Matt_King: This issue is kind of a fresh take
Matt_King: I'm proposing changes to a table on the "test management" page
Matt_King: I'm really curious about what James_Scholes has to say about this
gh-518: w3c/
James_Scholes: got it; please assign me
Matt_King: Next meeting is Wednesday, June 7 at 10:00 Pacific