When I use the keyboard only on my radio button questions, the only way to get between answers is the up/down arrow. This doesn't seem intuitive at all. I would think the user would try to use tab and find they were never able to get to any answers past the first one because they had no idea they were supposed to use the up/down arrows.
Is this a problem with my projects or is this how Articulate intended them to work?
The behavior you are experiencing is explained in this article, under the 'Navigation Is Easier' section. It is the intended behavior for how keyboard-users will navigate a Storyline 360 course.
You can check out the following articles which provide additional insight into how learners use Keyboard-Only navigation for Storyline 360 courses, as well as some tips on how to design accessible courses:
This is how a user using accessibility tools would expect to navigate when using a web page when you encounter radio buttons and you should not need to explain it to them. It is also WCAG compliant.
Phil, thanks for replying regarding WCAG and radio buttons, I wasn't aware of that one. I appreciate that your reply was specific to what I was asking about and pointed out it is WCAG compliant.
I can get the idea that an experienced keyboard only user would know to expect this, but I guess I'm wanting to account for inexperienced users as well. So I think I'll keep my instructions to be safe.
Hi Joe, I wrote a rude reply earlier that I want to apologize for. It was really uncalled for and I don't know what I was thinking. Your response was helpful. Please accept my apologies. Thanks much.
4 Replies
Hello C.J.
Happy to help!
The behavior you are experiencing is explained in this article, under the 'Navigation Is Easier' section. It is the intended behavior for how keyboard-users will navigate a Storyline 360 course.
You can check out the following articles which provide additional insight into how learners use Keyboard-Only navigation for Storyline 360 courses, as well as some tips on how to design accessible courses:
Let me know if you have any questions!
This post was removed by the author
This is how a user using accessibility tools would expect to navigate when using a web page when you encounter radio buttons and you should not need to explain it to them. It is also WCAG compliant.
Phil, thanks for replying regarding WCAG and radio buttons, I wasn't aware of that one. I appreciate that your reply was specific to what I was asking about and pointed out it is WCAG compliant.
I can get the idea that an experienced keyboard only user would know to expect this, but I guess I'm wanting to account for inexperienced users as well. So I think I'll keep my instructions to be safe.
Thanks!
This post was removed by the author
Hi Joe, I wrote a rude reply earlier that I want to apologize for. It was really uncalled for and I don't know what I was thinking. Your response was helpful. Please accept my apologies. Thanks much.