I am trying to setup some content so it's accessible. I have found using the keyboard very hard when on a Likert scale question. If I use the arrow keys to navigate through the radio buttons, it will select the button that gets focus. This means it always leaves the last radio button in a row selected. If I tab, it will jump out of the activity.
Are there specific keys that need to be pressed when using this interaction? I used to find that using the space bar will select a radio button but this is not behaving like that.
Thanks for reaching out! What you're experiencing sounds correct. We've made some recent enhancements to the player for accessibility, and with that came some navigation differences between keyboard-only and screen reader users:
It sounds like you're currently testing using the keyboard-only method, but feel free to download a supported screen reader like NVDA to test what a user will experience when the screen reader is enabled.
I've followed those instructions but using a keyboard, cannot select the answers.
If I tab, it will end up at the submit button. I cannot move between the rows as it will move the selection to my focus. Its' treating this activity as one button set, not three button sets. That's where I am getting stuck with it.
I'm using Likert survey question, it's not custom.
Thanks for the clarity on what you're experiencing! I tried the question type myself and had the same experience. It was counting X of 12, and I could only scroll through the radio buttons, not each question, then the related radio buttons.
I appreciate you bringing this up, and I'll be sure to reach out to my team on this behavior to ensure we're doing what is expected for this type of slide. I'll pop back in here when I have any news to share!
Thanks for checking in. Our team is investigating changes to the Likert tabbing order as a part of our improvements focused on accessibility, so we'll keep you posted here once we have more news to share!
Hi! For anyone visiting and wondering the same thing, here's how I did it.
Instead of using Tab to select the radio buttons, I ask the user to press 0, 1, 2, 3... to select their level of confidence (that's what my scale is about). I used simple triggers - albeit a lot of them: "Change state of Radio Button 1 to Selected when user presses the key Num1". And I duplicated them with the number pad keys and the regular keyboard keys. Of course... this only works with levels that go from 0 to 9 but... who want a Likert scale with 11 levels anyway? :p
Thank you for checking in! I see that you've connected with one of our Support Engineers. We'll continue the discussion there, and be sure to keep this thread updated when we have a fix. You can stay up to date on our progress by viewing our feature roadmap.
I'm having the same issue. I'm the eLearning Digital Accessibility consultant at my agency. NVDA is reading the first question and then all the buttons. Likert Scale is not accessible if the question is not read before the choices. I'd like to stay informed on when this issues is fixed.
Thank you for sharing your experience with this issue.
Unfortunately, Likert scale questions aren’t currently keyboard-accessible.
We’ve included one workaround in our VPAT to create keyboard-accessible Likert scale questions from scratch using radio buttons and button groups until we release fully accessible Likert scale questions. I understand this can be tedious.
I've shared your comments with our team, and we have you included to receive updates when an accessible Likert scale question ships!
It turns out Storyline's Likert questions don't report any scorm data anyway. They really shouldn't even exist as a question option in my opinion because they report nothing unless you use the Articulate LMS. I ended up having to rebuild every use of these using external survey tools instead (Google Forms, or Teams Forms) and embedding them as web objects. The reporting is still much less than ideal, but at least sort of possible to see the results.
Hi there, I am having the same issue and wondering if there has been any update here.
I am using a survey Q and embedding it into the LMS using GENERICO so it sits inline with the native LMS text elements. I need the screen reader to pick up each Likert option with the ability to select the relevant radio button.
Thanks for sharing your experience with your LMS and that redesigning Storyline Likert scales for accessibility is also helpful for you!
I have no updates to share, but since you are now subscribed to this discussion, you'll be among the first to know once this feature makes it to our roadmap.
Have there been any updates to this issue? I am experiencing the same problem as detailed above. Or are there any work arounds anyone has found (aside from just building pseudo-radio buttons from scratch)?
20 Replies
Hi Geordie,
Thanks for reaching out! What you're experiencing sounds correct. We've made some recent enhancements to the player for accessibility, and with that came some navigation differences between keyboard-only and screen reader users:
It sounds like you're currently testing using the keyboard-only method, but feel free to download a supported screen reader like NVDA to test what a user will experience when the screen reader is enabled.
I've followed those instructions but using a keyboard, cannot select the answers.
If I tab, it will end up at the submit button. I cannot move between the rows as it will move the selection to my focus. Its' treating this activity as one button set, not three button sets. That's where I am getting stuck with it.
I'm using Likert survey question, it's not custom.
Hi Geordie,
Thanks for the clarity on what you're experiencing! I tried the question type myself and had the same experience. It was counting X of 12, and I could only scroll through the radio buttons, not each question, then the related radio buttons.
I appreciate you bringing this up, and I'll be sure to reach out to my team on this behavior to ensure we're doing what is expected for this type of slide. I'll pop back in here when I have any news to share!
Any updates on this? I'm experiencing the same issue. Thanks!
Hi Allison!
Thank you for checking in! I don't have an update to share yet. We'll keep this discussion updated when we have a fix.
I have a client wanting to use this but am unable to use this question type as the accessibility is broken it. Please fix this asap.
Regards
Any progress on that issue?
Hi Agnieszka,
Thanks for checking in. Our team is investigating changes to the Likert tabbing order as a part of our improvements focused on accessibility, so we'll keep you posted here once we have more news to share!
Hi! For anyone visiting and wondering the same thing, here's how I did it.
Instead of using Tab to select the radio buttons, I ask the user to press 0, 1, 2, 3... to select their level of confidence (that's what my scale is about). I used simple triggers - albeit a lot of them: "Change state of Radio Button 1 to Selected when user presses the key Num1".
And I duplicated them with the number pad keys and the regular keyboard keys.
Of course... this only works with levels that go from 0 to 9 but... who want a Likert scale with 11 levels anyway? :p
Any update on this? Going on 2 years now :/
I've just discovered as well that this is a problem. Still unfixed.
Hi Fiona,
Thank you for checking in! I see that you've connected with one of our Support Engineers. We'll continue the discussion there, and be sure to keep this thread updated when we have a fix. You can stay up to date on our progress by viewing our feature roadmap.
I'm having the same issue. I'm the eLearning Digital Accessibility consultant at my agency. NVDA is reading the first question and then all the buttons. Likert Scale is not accessible if the question is not read before the choices. I'd like to stay informed on when this issues is fixed.
Hi Annykay!
Thank you for sharing your experience with this issue.
Unfortunately, Likert scale questions aren’t currently keyboard-accessible.
We’ve included one workaround in our VPAT to create keyboard-accessible Likert scale questions from scratch using radio buttons and button groups until we release fully accessible Likert scale questions. I understand this can be tedious.
I've shared your comments with our team, and we have you included to receive updates when an accessible Likert scale question ships!
Well this has caught me out again. Any chance this can be added to the timeline for fixes?
I can't create this manually as I need the question to report SCORM data.
It turns out Storyline's Likert questions don't report any scorm data anyway. They really shouldn't even exist as a question option in my opinion because they report nothing unless you use the Articulate LMS. I ended up having to rebuild every use of these using external survey tools instead (Google Forms, or Teams Forms) and embedding them as web objects. The reporting is still much less than ideal, but at least sort of possible to see the results.
Thankyou
I did not know that as I have not used one due to this issue.
Hi there, I am having the same issue and wondering if there has been any update here.
I am using a survey Q and embedding it into the LMS using GENERICO so it sits inline with the native LMS text elements. I need the screen reader to pick up each Likert option with the ability to select the relevant radio button.
Hi Kate,
Thanks for sharing your experience with your LMS and that redesigning Storyline Likert scales for accessibility is also helpful for you!
I have no updates to share, but since you are now subscribed to this discussion, you'll be among the first to know once this feature makes it to our roadmap.
Please let me know if you have any questions.
Hello,
Have there been any updates to this issue? I am experiencing the same problem as detailed above. Or are there any work arounds anyone has found (aside from just building pseudo-radio buttons from scratch)?
Thanks!