[Accessibility-testing] The Inform (Glulxe) Cloak of Access design goals

[deborah]

  One thing I just thought of.  One of the issues I’ve had with several 
interpreters is how easy it is to completely reset things. With  speech 
recognition, even though it constantly gets better, it is still 
relatively frequent for an utterance to be misheard  as something 
different. In some of the interpreters, if a cough is misheard as a 
word, sometimes the interpreter will  completely reset the current game.

So one of the things I would like to test for is interpreter resilience. 
That is. Before you do a reset, quit the game, refresh without saving, 
or anything that seems fairly irrevocable, do you ask for confirmation ?

I’ve run into this problem with twine, obviously, but I think also with 
one of the desk top windows interpreters. I just can’t remember which 
one.

  This is an something that we would write into the design of Cloak of 
Access; It is something we would write into our testing scripts.  I.e. 
“Tell the game you’d like to quit, but then change your mind. Are you 
still in the pit full of grues?“

Deborah