Table 2 User testing results

Some users did not wait for the synthesised voice instructions to finish, and tried keyboard commands at inappropriate times, for example, accessing the input field before hearing the question.

The dialogues and instructions can be very long for some players. A solution for future work is to implement a speech synthesiser speed control so that the reading speed could be configured. Shorten the instructions.

Once the user has selected the input field to type in the answer, they no longer have keyboard access to the clues that would help them answer the question in the Library Level. This is a limitation of the Construct 2 game engine, which does not control the focus out of the input field once it is focused in it.

In web projects using HTML5, where text fields are used in game, the text field can be focused in (for text input) or out (to control the remainder of the layout). Specifically for projects generated via Construct 2, this is not possible. In future projects, game engines that have support for control of text fields, such as Unity, should be considered.

Some users attempted to move around the scenario by repeatedly pressing the directional keys, rather than holding them down.

Adjust the movement of the character so that when the keys are pressed, the character walks more than a few pixels.