We have updated the Storyline 360 on 23rd January, 2018. Due to which the player buttons are not read by JAWS reader.
When we navigate to the Next and Back buttons with keyboard, the JAWS reader doesn't announce that we need to press Spacebar to activate the button.
It was working fine with the previous version (3.11.14249.0) of Storyline 360. However, it is not working since we installed the software updates published on 23rd January, 2018 (version 3.12.14533.0 ).
Hey Ravinder. I'm excited to let you know that we just released update 13 for Storyline 360! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where JAWS was not reading the previous and next buttons, and the spacebar wasn't activating those buttons in HTML5 output.
Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!
Well, it passed our Trusted Tester program which most likely means the JAWS reader is good with it too. Our government clients will be thrilled to hear this!
JAWS seems to be reading the *TEXT* for the previous button, instead of the "Previous button screen reader verbiage" ... so it says "prev button" instead of "previous button.
Anyone have any idea why? I do not want to take up more space by making the text actually say previous, so I would like to figure out how to make use of this field in the player labels area.
For references, I am using the latest storyline 360 (v3.27.18822.0), the latest JAWS(2019.1904.60 ILM), and the latest Chrome(74.0.3729.131).
To circle back to Leslie's post, I wanted to share that this issue is fixed. Thank you for sharing the crucial need for creating accessible content for all learners. While there is more to do, we're at a point where we're confident the work done so far delivers meaningful real-world improvements for learners with accessibility needs.
Below, you'll 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—all while opening up more browser, assistive technology, and device choices 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 there's anything we can help answer, please let us know. We know there is more work to do, so we'll continue to share all the news on this topic!
8 Replies
Hello Ravinder,
Sorry to hear that you're running into an issue with this, but it is something our team is aware of and looking into.
I've added this thread to the report as we track user impact and so that we can update you here when we can.
Hey Ravinder. I'm excited to let you know that we just released update 13 for Storyline 360! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where JAWS was not reading the previous and next buttons, and the spacebar wasn't activating those buttons in HTML5 output.
Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!
This is good news. We're going to test it out today.
Well, it passed our Trusted Tester program which most likely means the JAWS reader is good with it too. Our government clients will be thrilled to hear this!
So glad to hear it Bob! Thanks for the update.
JAWS seems to be reading the *TEXT* for the previous button, instead of the "Previous button screen reader verbiage" ... so it says "prev button" instead of "previous button.
Anyone have any idea why? I do not want to take up more space by making the text actually say previous, so I would like to figure out how to make use of this field in the player labels area.
For references, I am using the latest storyline 360 (v3.27.18822.0), the latest JAWS(2019.1904.60 ILM), and the latest Chrome(74.0.3729.131).
Thanks in advance.
Thanks, Seth.
I'm able to hear the same issue you are sharing here when viewing my test content in the Chrome browser.
It works as expected using IE11, so seems specific to the HTML5 output.
I'll pass this information along to my team to take a look at and link this conversation so that any updates can be shared here.
Hey there, Seth!
To circle back to Leslie's post, I wanted to share that this issue is fixed. Thank you for sharing the crucial need for creating accessible content for all learners. While there is more to do, we're at a point where we're confident the work done so far delivers meaningful real-world improvements for learners with accessibility needs.
Below, you'll find all the details on what this means for Storyline 360, Update 36:
Be sure to also check out these general FAQs on accessibility in Articulate 360 tools!
This release makes it significantly easier for those users to perceive, operate, and understand content published with Storyline—all while opening up more browser, assistive technology, and device choices 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 there's anything we can help answer, please let us know. We know there is more work to do, so we'll continue to share all the news on this topic!
This discussion is closed. You can start a new discussion or contact Articulate Support.