Question: key input saves bad results

When (a) autoFirstChar is false, (b) answers are in string, not array format, and (c) there is a correct answer, the code which responds to key presses incorrectly assumes that the answers are in array format, thereby basically mimicking autoFirstChar behavior, but then *storing the second character of the answer string as the result*. This results in unexpected behavior where, for answers like `['Yes', 'No']`, if a user presses "y", the answer "e" is recorded.

Suggested patch attached.