In my course the user has to fill in a few text input fields concerning name, occupation etc. The problem is that you always have to press the tab key twice to move from one field to the next. Is there any solution to this problem?
I've realised what it is now, The tab key works as usual as long as the input field was selected automatically by storyline. When the user goes ahead and marks the field with a mouse click before writing, the tab key must be pressed twice to leave it.
Ah...totally see what you mean. hmmm....I wonder if anyone knows a work around.
I tried playing with layers, but wasn't successful. Can't change states.
Wonder, too, if this should be a feature request or bug report. Seems as though it should work consistently, whether Learners click first or not. In the end, they're doing the same thing...answering and moving on. Still, I don't know the programming around it.
I am clutching at straws with this, but if you use a screen reader such as jaws would the first tab read the alt tag and the second one leaves the object?
Yep, just seems strange that this hasn't been picked up before. I don't do much work with screen readers but I am thinking this may be by design rather than a bug.
Hi Susan! Thanks for popping in to share your solution with everyone. It may not assist the users here, but could certainly assist users in the future.
15 Replies
If you tab once - which object is selected? It may be prevented if we can understand what objects you've used before the fields.
Hi,
The same input field is still selected after the first press. I can even keep writing in it.
Even if I a create a slide with only the two input fields this occur. Does it not happen for you?
Hi Erik,
If I have a blank slide and just add 2 text entries, I can press tab 1x to get to the 2nd one.
Hi,
I've realised what it is now, The tab key works as usual as long as the input field was selected automatically by storyline. When the user goes ahead and marks the field with a mouse click before writing, the tab key must be pressed twice to leave it.
But still no solution =(
Ah...totally see what you mean. hmmm....I wonder if anyone knows a work around.
I tried playing with layers, but wasn't successful. Can't change states.
Wonder, too, if this should be a feature request or bug report. Seems as though it should work consistently, whether Learners click first or not. In the end, they're doing the same thing...answering and moving on. Still, I don't know the programming around it.
Interesting.
Definitely seems as though it should be brought up to me!
I am clutching at straws with this, but if you use a screen reader such as jaws would the first tab read the alt tag and the second one leaves the object?
Otherwise I think it is a bug
So, Phil, do you mean that it may have been purposely programmed that way to avoid issues with screen readers?
Yep, just seems strange that this hasn't been picked up before. I don't do much work with screen readers but I am thinking this may be by design rather than a bug.
Hmm could the field somehow be prevented from being picked up by the screen reader alt-text thing?
Found a solution. Let's say you have a text entry for a phone number: 1234567890.
You create a variable for the entry of te_phone. Your automatic trigger will be:
Set te_phone equal to the typed value when control loses focus.
You will add the trigger with conditions:
Jump to the next slide when control loses focus if te_phone is equal to 1234567890
Your onscreen instruction caption to the user will read:
Enter the phone number 1234567890 and press Tab.
What happens: The user presses Tab once. The control loses focus and the screen jumps to the next page.
Hi Susan! Thanks for popping in to share your solution with everyone. It may not assist the users here, but could certainly assist users in the future.
Thanks. I noticed that most of the postings were about two years old.
Please feel free to use the solution if the question comes up again.
Susan
I appreciate it Susan - and we refer to customer shared solutions very often :)
This discussion is closed. You can start a new discussion or contact Articulate Support.