Meeting minutes
meeting time
Matt_King: We ran two surveys and learned that the current meeting time is the best for the most people, but there are important conflicts. Lola is in the UK and is unable to participate at this time
Matt_King: There was a proposal that we have two different times and alternate between them
Matt_King: If we're going to do something like that, we need to decide on something simple
Matt_King: For the other two potential meeting times, there were some significant conflicts with each
Matt_King: If we have an earlier meeting on Wednesday every other week, and retaining the current meeting time for the other weeks
We're considering 9:00 PT and 10:00 PT on Wednesdays
james_scholes: I can move an internal PAC meeting and then be available every other Wednesday at 10:00 PT. No amount of rescheduling will open up 9:00 PT for me
Matt_King: Fortunately, the W3C calendar supports bi-weekly meetings
michael_fairchild: I can't make that time on Wednesdays, but don't let that stop you
Matt_King: Okay! We will adopt this new schedule and make a habit of closing each meeting with a reminder about the next meeting time. Of course, it will also be in the W3C calendar
Color Viewer Slider testing
james_scholes: Firefox and JAWS. Only one assigned tester (100% complete)
Matt_King: I'm signed in; that looks correct to me
Hadi_Rangin: I have been absent from this call for some time, but if you folks can give me some help getting started, I would be glad to take this on
Hadi_Rangin: I primarily use JAWS, so this is a good one for me
james_scholes: I can send you the introductory material, and if you need any one-on-one coached, I can be available for that, too
Hadi_Rangin: My GitHub ID is hadirangin
james_scholes: we also need help for the same plan using NVDA and Firefox
Dylan_Sheffer: I can be your second tester for the Color Viewer Slider using NVDA and Firefox
Matt_King: We also have only one set of results for this pattern using Chrome and VoiceOver. We need another tester
Dylan_Sheffer: I can take this on, as well
Matt_King: That will complete Color Viewer Slider
Radio Group Example Using aria-activedescendant
Matt_King: There's one conflict, one tester labeled the AT response to pressing the space bar as "overly verbose"
Matt_King: The other tester recorded the same AT response but did not label it as "overly verbose"
The group agreed that the screen reader is indeed overly verbose for this action and overrides the second tester's verdict
This is for JAWS and Firefox. The AT response in question: "Regular crust radio button checked 1 of 3"
choosing next patterns
michael_fairchild: Links are fundamental to the web, but then again, it's exceedingly rare to encounter links that are implemented with ARIA
james_scholes: Menus are becoming increasingly prevalent these days
james_scholes: switches are contentious
Matt_King: I'm hearing alignment around disclosure, menu, and switch
james_scholes: If we're doing menu button, I would vote for the activedescendant version
james_scholes: Okay, to recap: the next three will be disclosure navigation, menu activedescendant, and menu combobox
Matt_King: We're still working through the queue, so these won't happen in the next two weeks, but it's good to have them selected so that they're ready
Matt_King: We will not be meeting next week! We will meet Wednesday, May 24th. I will update the W3C calendar to reflect this.
next meeting
Matt_King: We will not be meeting next week! We will meet Wednesday, May 24th. I will update the W3C calendar to reflect this.