Forum Discussion
Likert tabbing order / selecting radio buttons.
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
Hi Everyone,
I'm happy to share that we've just released a new update for Storyline 360!
In version 3.111.36309.0, we’ve included essential fixes and new features. One of the new enhancements we've added is:
- Deliver accessible surveys with a built-in Likert scale question that supports screen readers and keyboard navigation.
Even more good news! You don’t need to rebuild your existing Likert scale questions.
If you republish an existing project in the February 2026 update of Storyline 360 or later, the new version’s previously inaccessible Likert scale questions will automatically support screen readers and keyboard navigation. There’s no need to recreate those questions in newer versions of Storyline 360.Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need any additional help!
21 Replies
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!
Hi Everyone,
I'm happy to share that we've just released a new update for Storyline 360!
In version 3.111.36309.0, we’ve included essential fixes and new features. One of the new enhancements we've added is:
- Deliver accessible surveys with a built-in Likert scale question that supports screen readers and keyboard navigation.
Even more good news! You don’t need to rebuild your existing Likert scale questions.
If you republish an existing project in the February 2026 update of Storyline 360 or later, the new version’s previously inaccessible Likert scale questions will automatically support screen readers and keyboard navigation. There’s no need to recreate those questions in newer versions of Storyline 360.Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need any additional help!
