Accessibility feature requests
We have recently been working on a Twine game, and had the opportunity to work with an accessibility consultant to improve the experience for players with visual and other impairments.
It’s been a really interesting process, and a huge learning curve, and we’re aware there are likely to be others in the same position. So we’d like to raise some feature requests for Twine accessibility. Not as a complaint - the total opposite. What you provide with Twine is truly amazing, and we hope that by making a request for these features our voices will be helpful to you in support of your development of this (and other) tremendous tools and resources for creating interactive fiction.
We found that it took a surprising amount of labour to research and make adjustments to the defaults for accessibility, so it would be brilliant to be able to save others having to do this from scratch each time. We’d like to put in a request for:
A default setting for optimised accessibility. A quick, best-practice reference guide to optimising accessibility in Twine projects.
We were able to make a lot of tweaks ourselves, but also found that there were some elements we couldn’t make work with screen readers. Within Twine, it would be really helpful to be able to:
Make the sidebar navigation arrows compatible with screen readers. Make links compatible with screen readers.
Hopefully these feature requests are useful to you in your mission. We love what you do.