We are building a course in Storyline 360 that needs to meet the WCAG 2.1 standards. Our partner just did accessibility testing and found the following glitches:
• Currently, Storyline is handling only one type of knowledge interaction (Select all that apply) 100% correctly. • For multiple choice questions: JAWS instructs learners to use their keyboard arrow keys to make a selection. However, the course doesn't actually react to those keys. Radio buttons only react to either the space bar or the enter key. • For matching questions with drop-down lists: Learners are unable to select an item other than the first item in any drop-down list with the keyboard.
When will these glitches be resolved? Does anyone know?
Hi there, Wendy. Thanks for sharing the areas where you need better accessibility from Storyline 360 output. To confirm, we've got those issues documented.
We're making good progress on accessibility enhancements for Storyline 360. We've been consulting our customers about specific needs and have identified a range of improvements we can make.
The way the Storyline player is currently built, we're able to make incremental improvements, but we want to aim higher. So we're working on a better player structure that'll provide industry-leading accessibility support. We have several enhancements planned to comply with the latest accessibility standards across more screen readers and web browsers.
We're excited about these changes, and we think you're going to love them too! I can't share the details yet, but I'll be sure to update you as soon as the features are ready.
Hello, we are running into issues with stoyline 360 course that is resulting in Broken Aria references. We worked with an Articulate engineer to try and solve this issue and changed to the modern player. Unfortunately, our customer's testing is still coming up with the same issues. Can you assist in a solution for this? thanks
Thank you for continuing to share the crucial need for creating accessible content for all learners. While more work remains, we're at a point where we're confident the work done so far delivers meaningful real-world improvements for learners with accessibility needs. I've included links below where you can find all the details on what this means for Storyline 360 Update 36:
This release makes it significantly easier for those users to perceive, operate, and understand content published with Storyline, while opening up more choices of browser, assistive technology, and devices for the first time. Learners will benefit from the vast majority of these improvements, even when the course author is not designing their course for accessibility.
If you have any questions or concerns, let us know here or reach out to our Support team. We know there is more to do, so we'll continue to keep you posted about future releases.
6 Replies
Hi there, Wendy. Thanks for sharing the areas where you need better accessibility from Storyline 360 output. To confirm, we've got those issues documented.
We're making good progress on accessibility enhancements for Storyline 360. We've been consulting our customers about specific needs and have identified a range of improvements we can make.
The way the Storyline player is currently built, we're able to make incremental improvements, but we want to aim higher. So we're working on a better player structure that'll provide industry-leading accessibility support. We have several enhancements planned to comply with the latest accessibility standards across more screen readers and web browsers.
We're excited about these changes, and we think you're going to love them too! I can't share the details yet, but I'll be sure to update you as soon as the features are ready.
Hello, we are running into issues with stoyline 360 course that is resulting in Broken Aria references. We worked with an Articulate engineer to try and solve this issue and changed to the modern player. Unfortunately, our customer's testing is still coming up with the same issues. Can you assist in a solution for this? thanks
Hi Valerie,
Thanks for reaching out and sharing what you are running into.
I see that you were able to reach out to Christopher as well and he is still doing some testing and working with you directly.
Hi Wendy and Valerie,
Thank you for continuing to share the crucial need for creating accessible content for all learners. While more work remains, we're at a point where we're confident the work done so far delivers meaningful real-world improvements for learners with accessibility needs. I've included links below where you can find all the details on what this means for Storyline 360 Update 36:
You'll also find our general FAQ on accessibility in Articulate 360 tools here.
This release makes it significantly easier for those users to perceive, operate, and understand content published with Storyline, while opening up more choices of browser, assistive technology, and devices for the first time. Learners will benefit from the vast majority of these improvements, even when the course author is not designing their course for accessibility.
If you have any questions or concerns, let us know here or reach out to our Support team. We know there is more to do, so we'll continue to keep you posted about future releases.
I also wanted to quickly add that drop-down lists are read correctly in Update 36 (Build 3.36.21213.0) for Storyline 360!
Again, thank you for sharing how important accessible content is!
Thanks for your efforts on this issue! We appreciate all that Articulate is doing to continually upgrade your products to meet user needs.
This discussion is closed. You can start a new discussion or contact Articulate Support.