Meeting minutes
Meeting pole update
<Matt_King> Matt gave Sam input for a pole.
<Matt_King> Sam made draft.
SS: Sam sent Matt a draft of the poll
MK: How long should we keep the poll open? I propose we announce the poll on the mailing list
MK: I will add a reminder about the poll when I send out next weeks agenda for this meeting
MK: I propose keeping the poll open for two weeks, send it out tomorrow, a reminder next week and a final reminder Tuesday the 28th
JS: I concur
JG: We may also want to consider using a poll for people to volunteer for a specific pattern?
MK: We don't have a good way to train new people on testing. James what do you think about people testing who don't normally attend meetings?
JG: I was thinking you could ask people how confident they are when testing.
JS: I think there is something to be said about having more testing capacity, and would encourage more involvement and ownership.
JS: The lack of clear training material, and the time it takes to clear up conflicts are concerns
JS: It may be worth documenting the instructions I've recently sent David and Louis to get them on board and making it public
MK: I am working on some Wiki updates right now, I've put in some place holders related to getting started running tests
<Matt_King> Calendar for aria-at CG: https://
MK: I've added this meeting to the ARIA and Assistive Technologies Community Group - Calendar
Test running status update
MK: It looks like all of the first 5 plans are marked with a status of ready for all three screen readers
MK: I think we are waiting on input from Howard as to when do we get to push the button to mark as in review
HE: This feature exists in the sandbox now, if anyone wants to test it
HE: We can duplicate this feature for the candidate test page
HE: I think monday afternoon or Tuesday morning we can push this update to PROD
HE: I would like if its possible, to confirm that we are seeing what we would expect in sandbox
MK: Is the latest data in the sandbox?
HE: No, but we can work on getting that data in today, so people can review Monday morning
MK: So for these, Alert, Command Button, Link, Toggle Button, and Radio Group with Active decsendent all look ready to go
JS: Yes Dylan completed the testing for Toggle button, any feedback?
DS: No, I found the testing instructions were easy to understand and run
DS: I use a virtual machine on a mac to test
MK: How well does that work?
DS: It works well, I had to remap a few key commands and add a delete key as one doesn't exist on macs
MK: Delete on a mac is FN+Option+Backspace
MK: Okay then those 5 are ready, and it looks like we are close on a few more. Dialog has one conflict, Alyssa it looks like you are almost done with that?
AG: Yes I'm about a third of the way done with that, there was one conflict
JS: Lets save the discussion for that conflict, I haven't read the issue yet
JS: Also a new version of JAWS was released this week, Alyssa have you updated? I would almost ask you not to
MK: James after slider and menu dialog, you have some other tests assigned to people correct?
JS: No, I don't think the Queue is accurate beyond the 8
JS: We don't have the next patterns prioritized, the spreadsheet of test plans is almost ready and we can review it next thursday
Status of Site Changes
MK: We already covered this, Howard said the new changes to the site will be ready Monday. James you and I should coordinate some testing on Monday
MK: We can decide which patterns we should each test with offline
Gathering pattern usage data for test plan prioritization
MK: Last week, one of the dimensions of prioritization that we discussed, that wont be in the spreadsheet that James is working on, is prioritization based on usage of a pattern
MK: We discussed using HTTP Archive and others. Can we make any of those ideas actionable? I personally don't have the time to query the data, and I also don't have much knowledge with HTTP Archive
MK: I don't know that we want to add it to the Bocoup or PAC agenda as they have so many things to do already
MK: Does anyone have advice on how to make these ideas actionable?
MK: The one thing I can do is get data from the w3C web masters, regarding the traffic and number of visits to the APG pages
JS: I think that there were alot of interesting ideas last thursday, many were fairly ambitious and make have a high signal to noise ratio that would make it hard to understand with the effort we have available
JS: In the interest of putting together a priority list ASAP, my feeling is that the APG visitor data will be extremely useful, and then we should canvas opinions from this group in this meeting and asynchronously, and then perhaps table the other ideas for now.
JS: We could also have people spend their time in different ways like documenting testing instructions
MK: You are suggesting if these ideas were easily actionable we could do them, but not if they are resource intensive
JS: The sooner we can prioritize the next few patterns, the better
JS: I would like the next priorities to be as stable as possible for the next 6 months
MK: I agree
MK: Does anyone else have thoughts or experience with this kind of research?
DS: Not really
AG: No not really, I could gather some opinions from the team of testers I work with to see what patterns then encounter the most and have the most issues
MK: Yeah that would be helpful
DS: I could also ask some of my collogues at Deque if we had some specific questions
AG: I see alot of badly done navigation
JG: Yeah Navigation stuff is really bad
MK: So it sounds like we think we will have enough input for prioritization without that kind of additional research
MK: The spreadsheet will allow us to take a first pass at prioritization, then we could ask people to rank a subset of the next priorities
AG: Yeah that would work
JG: I think that would be a good idea