[Accessibility-testing] Plotting out the rest of the year

[Jason McIntosh]

Y’all,

Just wanted to re-post this with corrected dates (as Zack pointed out during our last meeting that my original dates were off by one week, oops).

So that it doesn’t go past Thanksgiving, I dropped the penultimate “continue testing” step from the original schedule, which shortens the testing period by one week (to three weeks, total).

Would also point out that the first deadline is this coming Monday, August 13. We’ll be having our meeting at the usual time and channel then — come on by if you can — with an agenda of discussing the mockup testing report matrix I shared here last Wednesday, and talking about whatever is needed to finish up the two test games.

Anyway, the corrected schedule:

1. (Due: Aug 13) Complete development of the two games, and build a draft of our testing matrix, including a reasonably finalized list of accessibly technologies and conditions to cover.

2. (Aug 27) Complete internal testing and critique of the two games. Revise the testing matrix based on prior discussion, as well as its internal application to the test games.

3. (Sep 10) Gut check: Should we continue with wide testing, or should we present what we have (including testing and observations provided from our own team’s accessibility experts) and call it good?

If we decide to call it a day, then we take an abbreviated path that sidesteps the remainder of this schedule. We’ll start preparing the final public deliverables early, and otherwise wrap up.

If we decide to carry on with wider-scale testing, then we should start preparing the surveys as well as any other preparatory material we plan to distribute to testers.

4. (Sep 24) Start recruiting testers outside the group. I might suggest beginning with a few “hand-picked” testers so that we can “test the tests” and make sure that our process works at all, refining it based on their feedback.

5. (Oct 8) Start performing wider-scale recruiting.

6. (Oct 29) Commence wider-scale testing and data collection.

7. (Nov 19) Gather up our collected data and materials and draft a report to the IF community.