Screen reader (JAWS) not reading Prev and Next buttons

Hi all,

I'm creating an HTML5 course in Storyline 360, using the inbuilt player to provide Prev and Next buttons on each screen. When published, the tab key is cycling focus through all slide objects, then onto the player buttons/features as designed.

The problem is that the screen reader (JAWS) is not reading any kind of Alt Text for the Prev/Next buttons on the player, so even though they have focus, they are essentially invisible to a non-sighted user.

Has anyone else experienced this? I would love any suggestions for solutions please, as my poor client is getting seriously discouraged at the accessibility hurdles we are encountering as a result of Storyline "features".

(I would love to not have to manually rebuild the Prev/Next buttons on each screen if possible, as they have triggers attached - and besides, if the Storyline 360 output is touted as being accessible then I assume there is some way for these buttons to be read by screen readers.)

Thank you!

41 Replies
Kenneth Dyer

Hey Loic,

Back in August, Articulate Support logged issues with tabbing and the JAWS Reader as a possible software bug. I have since reverted back to the May 2018 version of Articulate Storyline 3 (version 3.4.15731.0) and everything works as it should. I'm weary to update it again until this bug is resolved.

Katie (Gokhshteyn) Riggio

Hello, Catherine. Sorry you and your client are at this roadblock.

Happy to help! Are you using Storyline 3 or Storyline 360?

  • Storyline 360, Update 13: We fixed the issue where JAWS did not read the previous and next buttons on the Classic Player. Let us know if you come across this on a current update!
  • Storyline 3: While this issue isn't fixed in Storyline 3 just yet, we promise to keep this discussion updated as soon as new information is available. 

Also, we're happy to test your project file to look for some custom approaches. If you're able to share the .story file, please use this private upload link.  We'll let you know what we find, and will delete the file after!

David Sprouse CU

Hi, I've been struggling with the same thing in both JAWS and NVDA screen readers. I discovered, as a work-around, if you change your button settings from icon only to either text or text and icon, then both screen readers announce the button purpose which is apparently based on your Aa Text Labels (which are also set in the Player Properties)

Look at the Navigation settings in Player Properties > Colors & Effects > Button Styles (see attached)

Also, this seems to be the case for other "icon only" buttons too like the submit button.

 

Catherine Orfald

Thanks Katie! The issue has been resolved (not an SL bug). I was using SL360 with the Classic player and buttons with names, not just icons. We'd previously published this course which was working fine. The client said yesterday, "It's working
now after I did a swap between the new version and the old version, then
back to the new. I'm not sure why that made a difference, but it did! I'm
going to chalk that one up to Jaws finickiness." Thanks for your swift response.

Catherine Orfald

Thanks Katie! The issue has been resolved (not an SL bug). I was using SL360 with the Classic player and buttons with names, not just icons. We'd previously published this course which was working fine. The client said yesterday, "It's working
now after I did a swap between the new version and the old version, then
back to the new. I'm not sure why that made a difference, but it did! I'm
going to chalk that one up to Jaws finickiness." Thanks for your swift response.

Katie (Gokhshteyn) Riggio

Greetings, Philip! Appreciate you clarifying this key detail, and you're right. We have an open issue where JAWS and NVDA screenreaders read the Next/Prev buttons as "Button" on the Modern Player. The issue fixed on Update 13 was on the Classic Player. I'll edit my last reply to reflect that the fix was in the Classic Player, and promise to keep you posted on any updates to this bug.

Hello, David: I'm sorry this bug has an impact on your work, and appreciate you sharing this workaround. Super helpful, and I'll add this to the report!

Hi, Catherine: Thanks for your update! Glad to hear you and your client are up and running again. If you hit any other snags while building out your course, please let us know!

Ashley Terwilliger

Hi Emily,

Thanks for checking in on this issue! Our team is digging into the issue and we'll update folks here once we have more info. It's one of the areas we're focused on as we look to larger improvements within accessibility. 

For the latest information on the accessibility improvements coming to Storyline 360, head over to Simon's post in this discussion.