Keyboard-only web interface

[szabgab]

Make it easy to use the web interface without the mouse using only the keyboard of a computer. If this is already available, then add some explanation how to do this.

[ ] Select the module to practice [ ] Select the skill skill to practice [ ] Multi-choice with radio buttons (1-2-3 work, maybe up/down arrows should also) [ ] Skip (A hot-key for this, eg ctrl-p) [ ] Finish early [ ] Chips (maybe left-right arrow keys should work on them, and a hot-key (space?) to select one, Up/Down arrow to move to the selected text, left-right arrow to move inside the already selected text and same hot-key to remove chip. Ctrl-left/Ctrl-right could be used to move a chip in the selected text) [ ] 3 -pictures (here too I think left-right arrow keys would be useful) [ ] Submit (maybe instead, or in addition to ENTER, there should be also a hot-key) [ ] Continue (maybe instead, or in addition to ENTER, there should be also a hot-key)

[kantord]

it's more-or-less possible

• for most lesson types, numbers (1-2-3-4) are hotkeys for selecting the answer
• the Enter key is a hotkey for submitting your answer
• for free-form text inputs, the input field is selected by default

what doesn't work:

• everything else needs tabbing through the page to use with the keyboard, or the usage of browser plugins that implement this in a different way
• for the chips challenge, the first chip is not selected by default, so tabbing through can also be painful
• the mini-dictionary is close to impossible to use without the mouse probably

My questions:

• how would you like to have this documented?
• how would you improve the experience?
• how would you implement the mini-dictionary?

[szabgab]

• documenting: I'd have a button with a question-mark (?) somewhere visible on the screen that you can either click with the mouse or press the question mark on the keyboard. Then it would show a pop-up explaining all the keyboard options.

• improvement: I'd probably create a list of things that need improvement and as they are implemented they can be copied to the documentation. I am adding them to the original report above.