[Accessibility-testing] Fwd: IF blind player
Austin Seraphin
austin at austinseraphin.com
Mon Jan 28 15:55:43 EST 2019
I started wondering about extending the testing as well. We did bring on
some new players.
On 1/27/19 5:04 PM, Furkle Industries wrote:
> Sounds like we may want to consider extending the duration of the
> initial testing round, in case more than a couple would-be testers got
> missed.
>
> On Sat, Jan 26, 2019 at 7:58 PM Jason McIntosh <jmac at jmac.org
> <mailto:jmac at jmac.org>> wrote:
>
> I’m processing the requests from the volunteers that Zack rustled
> up now, and wanted to share this one in particular, coming from a
> member of the blind gamer community who wants to use IF creation
> tools, Twine and Inform included. I of course stand by our
> decision to drop that facet from our testing, but I think this is
> a nice reminder that the interest is out there.
>
> (They are also a Player Panels member who sounds somewhat
> surprised at not getting tapped?)
>
> (Name & email removed because of this list’s public archive, but
> of course I can put folks in contact if they desire.)
>
>> Begin forwarded message:
>>
>> *Subject: **IF blind player*
>> *Date: *January 24, 2019 at 12:29:37 AM EST
>> *To: *jmac at iftechfoundation.org <mailto:jmac at iftechfoundation.org>
>>
>> Hello,
>>
>> Despite me being involved in the Able Gamers Player Panel, I had no
>> idea you were looking for testers for Interactive Fiction. I just saw
>> the blog post but, upon seeing that the player panels are involved, I
>> was shocked. I haven't got an email from them since October.
>>
>> Despite this however, definitely consider me very interested in both
>> helping accessibility of IF both as a player and as an aspiring
>> author. I say aspiring author at this point because it appears that
>> only the Sugar Cube Twine option is accessible when, perhaps, I'd
>> like
>> to use the default easier option. Adrift 5 is completely inaccessible
>> and the developer doesn't seem to want to figure out a way to change
>> it, even if suggestions are provided. The Quest desktop client is not
>> too great either.
>>
>> Inform is the closest to being accessible, but testing/debugging
>> games
>> in the default parchment runner internally in Inform... it needs
>> work,
>> as does being able to read errors and jumping to those lines in the
>> code the errors reference. It may be easier on Windows... there are
>> several blind Inform authors, however it was too slow and clunky on
>> macOS using VoiceOver.
>>
>> So yes, I'd love to be a tester even if we're only at the playing
>> stage for now.
>>
>> Thanks.
>
> _______________________________________________
> Accessibility-testing mailing list
> Accessibility-testing at iftechfoundation.org
> <mailto:Accessibility-testing at iftechfoundation.org>
> https://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing
>
>
> _______________________________________________
> Accessibility-testing mailing list
> Accessibility-testing at iftechfoundation.org
> https://iftechfoundation.org/cgi-bin/mailman/listinfo/accessibility-testing
--
Austin Seraphin: https://AustinSeraphin.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://iftechfoundation.org/pipermail/accessibility-testing/attachments/20190128/6d0ec7d4/attachment.html>
More information about the Accessibility-testing
mailing list