HanonO
(Hanon Ondricek)
September 18, 2026, 2:26pm
74
Welcome Brandon! We always appreciate feedback about how to make our games more accessible.
One good practice for sighted users when posting - if you include an image, edit the alt-text so there’s at least a minimal description of it. The default alt-text will be the file name. If you click the pencil icon in the post preview pane you can edit this and provide a description.
The inline image code will look like this:

Note that the alt-text on larger images is displayed on mouse-hover.
Here are some links to topics about IF accessibility:
Authors! Designers! Developers! Lend me your eyes!
Now that you’ve got no eyes, think about that project of yours - can you still play it?
Nowadays, there are many devices to play IF in, and many players who want to play your game. But those devices may have limitations, and some of your players - maybe the ones who will be your biggest fans - may have some disability that’ll prevent them from enjoying your masterpiece.
You didn’t know about all that? That’s ok, you don’t have to know, maybe …
A lot of the time, accessibility just happens. Parser games naturally have an affinity for it. And yet, sometimes, things don’t work out. Something I’ve had in mind for a while is designing for accessibility. I think there are some basic steps to take: alt text for images, for instance, or thoughtful use (or not using at all) of special characters.
I think this means testing, too. Are there preferred interpreters when it comes to screen reader support? What reader technologies are used for IF? …
Please specify version and format if asking for help, or apply optional tags above:
Twine Version:2
Story Format: 3.1
Hey all,
I would like to know whether Twine stories are accessible to blind players. I ran a story on a mac with Apple’s “speech” feature (not voice-over, though, because it’s super complicated to configure). And I also did the same with voice-over, on the iPhone—again, not very confident about the configurations I have.
It seems to work okay, except for hidden hooks, which …
NOTE: I’ve moved my response and your reply to the Accessibility and Usability thread I’ve mentioned.