| Telegram | t.me/Destranis |
| Telegram | t.me/Destranis |
For screen reader users, text-based multiplayer games (MUDs) are often easier to access than graphical games.
So why can playing one from a web browser feel harder instead of easier?
Brandon Cross (aka bscross) explains it all in this interview:
https://writing-games.org/accessibility-interview-bscross/
Examples that Danish is the most confusing language for English speakers:
In Denmark, when washing machines are done, their displays write, "Slut!", which means "Finished".
When someone enters an elevator, the display changes to "I fart", which means "On the move".
Tourists have difficulty finding a nice WC, because the signs often say "Bad toilet", meaning "Bathroom and toilet".
In lobbies with multiple elevators, one sign may say, "Gods elevator", which means "Freight elevator".
If your app or OS requires a toggle to be turned on for a screen reader to even *access* your UI, you're so, so not helping. We already have to know about the screen reader, we shouldn't have to check an assistive technologies checkbox or a VoiceOver checkbox or a screen reader mode command or, even fucking better, a Braille support command.
Instead, how about get rid of it and default to "everyone uses a screen reader" mode. And if shit's slow with that on, think of how we fucking feel.