Accessibility issues....button name is not announced on a revisit.

May 31, 2022

Hi...I have a course with properly named buttons.  The names are read by the screen reader but when revisiting the slide or after using the button to display a Slide Layer the screen reader no longer reads the label.  Anyone know what's going on here?  Thanks!!! 

7 Replies
Andrea Koehntop

Hi Russ! 

I've tested this on my end using NVDA version 2022.1 in Storyline 360 (Update 64), and the screen reader continues to read the button label, even after clicking on it and revisiting the slide several times.

  • Which screen reader are you using, and which version are you on?
  • Which version of Storyline are you using? 

This article on testing your course with a screen reader may be helpful to you as well.  

I look forward to your responses and helping you work through this! 

Andrea Koehntop

Hi again Russ!

I tested this with the most up-to-date version of JAWS and had the same result as you: the visited button state is not read by the screen reader. 

We have a current bug we are working on where States aren't read by a screen reader.

A current workaround suggested is to, instead of a button or a text box, add a shape with a solid fill at 100% transparency and add the text on the shape. The screen reader successfully reads the alt text of shapes.

Also, I have linked you to the bug so that you will receive notice of any updates.

I hope the workaround helps you in the meantime, and please let me know if there's anything else I can help you with! 

Andrea Koehntop

Hi Russ!

I apologize for the confusion. The bug reported in States aren't read by a screen reader is for both JAWS and NVDA.

My test with NVDA yesterday was regarding button labels: not different states of labels. I should have asked additional clarifying questions from you regarding the specific issue you were experiencing. 

I hope the workaround I mentioned in our previous conversation can help you in the meantime, and I will keep you posted with any updates!

John Morgan

Hello Russ!

Good news! Today, we just released Storyline 360 Update 68 (Build 3.68.28773.0) which included the fix for the bug where states aren't being read by a screen reader.

Now all you need to do is update Storyline 360 in your Articulate 360 desktop app!

If you have additional questions, don't hesitate to reach out in this discussion or in a support case.