Meeting minutes
<Matt_King> CHAIR Matt King
May meeting schedule
Matt_King: We won't meet next week--that's the ARIA face-to-face
Matt_King: The following week, I hope we can meet as scheduled
Matt_King: It's possible that I may have a conflict, though
Matt_King: And I'm definitely away on May 18
Matt_King: So we should expect just two meetings in May: May 11 and May 25
Testing and reporting check-in
Matt_King: Let's review by test plan
Matt_King: For "Toggle Button" we are only missing a report for VoiceOver in Chrome
jongund: the app is telling me that I'm not done testing, but when I review the tests, it appears that I've completed them all
jscholes: You may need to press "save"
jscholes: there's a conflict on the final test
jscholes: It's because jongund has noted a sound which was emitted. We don't typically track that right now
jongund: I can remove it
jongund: There was no output; how should I express that?
Matt_King: How about just inputting two double quote characters with nothing between them?
Matt_King: Should the app offer a more explicit way to indicate "there was no output"...?
jscholes: Others have expressed it in other ways
jscholes: Ideally, we would have a checkbox that says "No output" and that enabling it would cause the text entry field to become disabled
Matt_King: That would be ideal, but for now, we just need to agree on something to represent that idea
jscholes: As for the conflict. We see "no output" for one, and "incorrect output." I can understand how both of those apply
Matt_King: In this case, because there was some output, the accurate response here is "incorrect output"
jscholes: There are conflicts, but I'm not seeing them in the test queue. It appears to be because the conflicts related to the final test, which is now listed as "in progress"
Matt_King: I didn't see that initially, but after refreshing, I can confirm that behavior
(the group collectively explores the unexpected behavior)
Matt_King: There isn't necessarily a bug here because there was an incomplete test
jscholes: Yes, the incomplete status alleviated my concern
jscholes: Well, everything is in agreement. I think we're ready to publish. I've published it!
Matt_King: Matt_King: Next up, let's consider "Link"
jscholes: No conflicts for JAWS and Firefox. It was last published after this meeting last Thursday. Since then, this appears to be ready to go, so let's publish it
Matt_King: For NVDA, it looks like Alyssa and Isabel are in agreement. So I'm going to press publish
jscholes: For VoiceOver and Chrome, everything is complete and there are no conflicts, so I'll publish that as well
Matt_King: Matt_King: Next on the agenda is "Radio Group Example Using aria-activedescendant"
jscholes: I've published Radio Group for NVDA and Firefox
jscholes: Radio Group for VoiceOver and Chrome has four conflicts. Let's work these out
jscholes: This is a long command! Anyway, Joe marked it as "no output" and Isa marked it as "incorrect output"
jscholes: I need to run this as Joe and change the result to "incorrect output"
Matt_King: Let's set aside the app issue for JAWS and Firefox for now and handle that offline
Matt_King: Matt_King: Next up: "Modal Dialog"
Matt_King: We need a volunteer for JAWS and Firefox
Dylan_Sheffer: I can do that
Matt_King: For JAWS and Chrome, it looks like all the testing is completed and without conflicts
jscholes: I think that Alyssa's results are with an older version of JAWS, but I could be wrong
Matt_King: Is anyone available to test Modal Dialog for Firefox and NVDA?
Alyssa: I can do it within the next couple weeks. Is that an acceptable timeline?
Matt_King: That would be great!