Accessibility Cookbook for the Empathically Challenged

[jjmcc]

From the general thread above, to some specific TADS things:

@jjmcc

• Quick Travel is something I’ll need to look at seriously

@inventor200

In TADS 3 (or maybe just the Adv3Lite library? Not sure…) There’s a GO TO (room) command. The idea is you say something like “GO TO HANGAR”, and the game would find the path there, and then you’d use the CONTINUE command for each step of the way.

So it appears to be an Adv3lite thing, or at least not a default TADS capability, in that my WIP only allows it for adjacent rooms. Anyone aware of an ADV3 library or extension for this, before I start coding? :]

@jjmcc

• From a crying-for-more-engagement TADS Cookbook Wiki, there is a recommendation to reconfigure the default Status Banner for screen readers. It surprised me a bit that this did not show up in other lists. Has screen reader technology made this moot, or is this still a Good Practice ™?

Deeper on this a bit, the Cookbook implementation appears to be challenged, specifically in QTADS. Lectrote, Gargoyle, Frobtads and Parchment all handle this well:

statusLine.statusDispMode = StatusModeText;

QTADS, however, seems to insist on Suffixing every output with the Room Name. To wit:

ROOM
A room description.

There is an object here.  ROOM

Particularly intrusive when the system messages do not contain trailing spaces:

ROOM
A room description.

Obvious exits: EastROOM

Now, maybe QTADS is not invoked when screen readers are employed? Though I understand them to be intended for any window interface. Am I missing something, and this is Helpful, Actually?