[Accessibility-testing] Tonight's call
Jason McIntosh
jmac at jmac.org
Tue Dec 4 23:54:13 EST 2018
Debrief of Dec 3 2018 call:
Attending: Austin, jmac, Mark, Zack, Zarf
• We confirmed that the ball’s in AbleGamers’ court regarding the PP application status. (No rush, I said to Mark, since I don’t mind having just a little more prep-time…)
• We discussed the draft documents and surveys I’ve made so far.
• I feel like we don’t quite have a structured plan yet for balancing our expectation that testers play the games only once each with our desire to spread testing coverage across many OS/interpreter combinations. We batted some ideas around and I intend to follow up on-list about this separately.
• Austin and Zack reminded us that Gargoyle is especially problematic for screen-reader users, pretty much to the point of making the game unplayable, walkthrough or not. Therefore, whatever we do, we shouldn’t restrict testers to trying only a single, assigned platform, even if they can get nowhere with it.
• We talked about the differing levels of accessibility challenges between the Twine and Inform games. Those in attendance agreed that a cycle-link (very common in Twine games, and very aggravating for screen-reader users) would be a nice (and hopefully relatively simple?) addition to the Twine test. I’ve contacted Claire about this off-list.
• Austin voiced a desire to get Deborah’s thoughts on our recent progress and direction. Coincidentally, the next day, Deborah emailed me, and we set up a time for a one-on-one catchup Wednesday. Will follow up on here as appropriate.
• Next call will be Monday, December 17 at 7 PM Eastern.
> On Dec 3, 2018, at 4:18 PM, Jason McIntosh <jmac at jmac.org> wrote:
>
> Howdy y’all,
>
> Our usual Skype check-in is happening tonight at 7 PM Eastern. Do join us if you’re able!
>
> I’d like to talk about the testing-materials and survey drafts I’ve been sharing lately, and go over some questions about how we intend to assign testers to cover different interpreter / OS combinations (or not).
>
More information about the Accessibility-testing
mailing list