[Accessibility-testing] Reminder: Meeting on May 14, 6 PM Eastern
jmac at jmac.org
Mon May 14 16:24:57 EDT 2018
Reminder that we’re meeting at 6 PM eastern this evening (about an hour and a half from my typing this.) Like last time, let’s make it an audio-only Skype call, with your presence encouraged but not mandatory. If you show up after we start the call, send me a Skype message and I’ll patch you in.
Here’s a short agenda for tonight:
Update of Cloak of Access schedule and expectations
Update expectations: ChoiceScript
Update the deadline to have all first drafts of games & docs complete
Generate and pin the list of interpreters & tools to test against
I, jmac, dropped the ball here.
Let's get this done in email before the next meeting. (I'll start... really!)
Cloak of Access status updates & discussion
Interpreter resilience (Deborah's suggestion)
Adding to the team?
Mark suggested Dr. Christopher Power (AbleGamers' VP)
Various people last time mentioned Liza Daly
Mailing list consensus: Let's stick to who we have, but be open to further counsel? (And we are likely to work with Christopher WRT Player Panels anyway!)
Next meeting time
> On May 8, 2018, at 2:21 PM, Jason McIntosh <jmac at jmac.org> wrote:
> Hi everyone,
> Reminder that our second biweekly meeting’s set for next Monday, May 14 at 6 PM Eastern on Skype. I’ll make the audio-only call at 6 sharp, much as I did last time; attendance encouraged but not mandatory.
> Bit of homework to do before then (for me, as much as for anyone else!):
> • Review my notes & minutes from our last meeting, posted to this list on April 30 at 9 PM Eastern
> • Review Zarf’s notes on his “Cloak of Access” work in progress, posted to this list on April 30 at 10 PM Eastern
> • Refamiliarize with Furkle’s Twine work from last fall: https://github.com/furkleindustries/iftf-twine-testing
> • Have a look at AbleGamers’ Player Panels program: http://www.ablegamers.org/player-panels/
> I’ll post a more agenda-looking agenda shortly before the meeting next week. The general topic, I expect, will be further work on implementing “Cloak of Access” on our target platforms, and finalizing our list of interpreters (and browsers?) to test.
More information about the Accessibility-testing