<div dir="auto"><div dir="auto"><div dir="auto">Q: By MSIE, do you mean Internet Explorer, or do you actually mean Edge? If the former, what's the version cutoff? 11? 10? 8? More generally, are we including browser versions in any sense in the matrix?</div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto">Claire</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 19, 2018, 6:52 PM Jason McIntosh <<a href="mailto:jmac@jmac.org" rel="noreferrer noreferrer" target="_blank">jmac@jmac.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Present: Austin, Deborah, Jmac, Zack, Zarf. (Furkle unable to attend but reported to me in writing prior to meeting.)<br>
<br>
• Zarf has a “mostly-complete draft" of Inform’s "Cloak of Access” test game, per his email to the list on June 17. You can find it at <a href="https://eblong.com/zarf/tmp/accessib/" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://eblong.com/zarf/tmp/accessib/</a> . <br>
<br>
I would like everyone on this list (and especially the accessibility experts!) to give this game a whirl and respond with comment. How well does it present a thorough obstacle course of parser-IF-relevant accessibility challenges? Please post your thoughts to this list! (Or to Zarf directly, if that seems more appropriate.)<br>
<br>
• Furkle’s work continues on the Twine CoA test game.<br>
<br>
• I added the test-platform textfile to the team Dropbox.<br>
<br>
• We agreed to remove the (rather nonsensical!) Windows and Linux Safari entries, and add entries for MSIE instead.<br>
<br>
• We also agreed that, when the time comes to adapt this list into a survey for testers to fill out, we should provide an “Other” option. We don’t want to refuse a tester’s work just because they are most comfortable in Opera, for example. (And: we might be surprised to learn how many Opera users there are, e.g.)<br>
<br>
• We agreed that the “accessibility conditions” list (the subject of my own June 18 email to the mailing list) can be short, and cover the 80-perecent-ish of most-common situations (e.g. using a screen reader, or playing with no sound). On the survey we’ll create for testers, we will include a free-text area as well.<br>
<br>
This obviously needs a lot more development, which I’d like to accomplish as a team, so I’ll follow up on that mail from yesterday with some more comments and questions for y’all.<br>
<br>
• Next meeting time is set for 6 PM Eastern on Monday, July 2.<br>
_______________________________________________<br>
Accessibility-testing mailing list<br>
<a href="mailto:Accessibility-testing@iftechfoundation.org" rel="noreferrer noreferrer noreferrer" target="_blank">Accessibility-testing@iftechfoundation.org</a><br>
<a href="http://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">http://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing</a><br>
</blockquote></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jun 19, 2018 6:52 PM, "Jason McIntosh" <<a href="mailto:jmac@jmac.org" target="_blank" rel="noreferrer">jmac@jmac.org</a>> wrote:<br type="attribution"><blockquote class="m_5090902149116082561quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Present: Austin, Deborah, Jmac, Zack, Zarf. (Furkle unable to attend but reported to me in writing prior to meeting.)<br>
<br>
• Zarf has a “mostly-complete draft" of Inform’s "Cloak of Access” test game, per his email to the list on June 17. You can find it at <a href="https://eblong.com/zarf/tmp/accessib/" rel="noreferrer noreferrer noreferrer" target="_blank">https://eblong.com/zarf/tmp/accessib/</a> . <br>
<br>
I would like everyone on this list (and especially the accessibility experts!) to give this game a whirl and respond with comment. How well does it present a thorough obstacle course of parser-IF-relevant accessibility challenges? Please post your thoughts to this list! (Or to Zarf directly, if that seems more appropriate.)<br>
<br>
• Furkle’s work continues on the Twine CoA test game.<br>
<br>
• I added the test-platform textfile to the team Dropbox.<br>
<br>
• We agreed to remove the (rather nonsensical!) Windows and Linux Safari entries, and add entries for MSIE instead.<br>
<br>
• We also agreed that, when the time comes to adapt this list into a survey for testers to fill out, we should provide an “Other” option. We don’t want to refuse a tester’s work just because they are most comfortable in Opera, for example. (And: we might be surprised to learn how many Opera users there are, e.g.)<br>
<br>
• We agreed that the “accessibility conditions” list (the subject of my own June 18 email to the mailing list) can be short, and cover the 80-perecent-ish of most-common situations (e.g. using a screen reader, or playing with no sound). On the survey we’ll create for testers, we will include a free-text area as well.<br>
<br>
This obviously needs a lot more development, which I’d like to accomplish as a team, so I’ll follow up on that mail from yesterday with some more comments and questions for y’all.<br>
<br>
• Next meeting time is set for 6 PM Eastern on Monday, July 2.<br>
_______________________________________________<br>
Accessibility-testing mailing list<br>
<a href="mailto:Accessibility-testing@iftechfoundation.org" rel="noreferrer noreferrer" target="_blank">Accessibility-testing@iftechfoundation.org</a><br>
<a href="http://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing" rel="noreferrer noreferrer noreferrer" target="_blank">http://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing</a><br>
</blockquote></div><br></div></div>