Forum Discussion
Can't get a question slide to work with keypresses...
Hi all,
I have this problem with a question slide that I am developing. This does not go to a results screen etc. If you look at the example you have a choice of 4 answers, you choose one by clicking on it with your mouse and then click the Submit button. By the way 450 is the right answer! And you get feedback layers with these silver grey oblong panels telling you if you are right or wrong. This all works OK when you use your mouse BUT...
I want this to work just with keypresses for accessibility reasons if someone cannot use a mouse. If you click the icon in the top-right hand corner it shows you which key to press, for example, you can choose an answer by pressing one of the following keys; 1, 2, 3, 4 and after you have picked one you press the T key to submit.
Now... this doesn't work even after I have selected the correct answer as a get this white box stating "Invalid answer" which is not in one of my feedback layers. See the image.
Do these types of questions work with keypresses or am I actually doing something wrong?
Thanks in advance.
Keith
Hi KeithTrodden-48 what is your reason for using keyboard shortcuts, and not just allowing the usual keyboard navigation for accessibility? Why not allow people to just navigate to the different elements using their keyboard, and then select them, using the ENTER key or SPACEBAR. These functionalities do not need to be added, they are part of the standard functionality. This way, you are also not having to teach somebody the shortcuts to use the slide.
I've had a good look through your file as I noticed some other things whilst having a look. I think it is being over engineered for accessibility and much of the information your are providing as ALT text on text fields is information that is inherent and available through the HTML if structured correctly using the correct stylers and mark-up.
I also picked up that you have triggers setting the states of the radio buttons. This is not necessary as it is a radio group, and select one radio-button will automagically de-select any previously selected buttons. The state the radio button goes to when selected, "selected" is really important for accessibility too, as it communicates to screen readers the current state, and the user knows which radio button they have selected.
Some of the stuff I picked up, I've popped in this video for you (I couldn't help myself, accessibility testing is generally what I do). FYI: I had my system audio off until I tested with my screen reader. I didn't realise the course had audio talking over me. Sorry about that.
I've also made adjustments to the Storyline file. In my opinion, the changes to this file:
- Define headings using H1 and H2 elements
- Remove custom ALT text from text fields (inherit the text in the text box)
- Make layers exclusive, and include continue buttons on Correct/Incorrect layers
- Remove audio from the radio buttons & submit (conflicts with screen reader, unless it can be switched off for all slides by the user?)
- Audio feedback is fine (as long as screen reader users can turn off permanently for the session)
- Check the focus order.
- Remove Hide Layer triggers from the radio buttons
- Remove triggers that set states of radio buttons
- Add mask on layers to visually communicate items can't be accessed on the base layer.
- Added standard "Selected" state to the radio buttons
- Remove the Submit button from the pick-one button group
The changes simplify and make the content more accessible. Much easier for you to maintain, and a much more expected behaviour for assistive technology users and keyboard navigator.
I think some of the keyboard shortcuts are fine, but I think "T" is generally used for Video/Audio transcripts for accessibility. It's also not necessary to provide a shortcut for the Submit button.
Let me know if you have any questions.
