I have just discovered that some unpublished but complete courses I spent many hours setting up accessibility using tab order and alt text are now not working correctly. It seems that only buttons are being recognised all other objects although appearing in the tab order screen are being ignored when previewed.
I am also experiencing a very similar problem to the one Chris describes. Initially, only buttons are recognised, although other items on a slide will be found and read by a screen reader if I use Tab+shift to work backwards through the tab order set up for that slide.
I'd be grateful to be notified of any solution to this issue.
I raised a service ticket with Articulate reporting this bug which they are investigating. They advise rolling back to the previous version (3.35.21017.0), I did this and it did sort out my issue- so you could try that.
To restore a previous version, when launching Storyline 360 hover over the open button and click the down arrow, you'll find the option to restore in there.
We are experiencing the same problem. We have several courses in which we have worked very hard with accessibility, but it seems that only the buttons work, the boxes with texts are not read by Jaws. We had restore a previous version...
Thank you for inquiring about this issue! I see that our team is looking into this further, so I don't have an update at this time. A workaround that Chris mentioned is to roll back to Update 35 and has helped in the meantime.
You're in the right place, and we'll be sure to reach out with an update as soon as we can!
I'm eager to investigate! Storyline 360 behaves differently with screen readers since Update 36 (Build 3.36.21213.0). Rather than having to tab through each object for a screen reader to read off the object, screen readers will now read off the text boxes automatically and read objects when they're tabbed to. The objects that are highlighted when tabbing through a course are the interactive elements that require user interaction. For example, you'll see that buttons are still highlighted.
If you're not seeing interactive elements highlighted, please let me know. This includes buttons, navigation buttons in the Player, radio buttons, etc.
And the tab order? if you have text and interactive elements that need to be read in order. for example, text field, button, text field. if the reading is automatic, how does it work?
Here's my take. We've all gotten used to tabbing between all the items (text, buttons, images, etc.) on our slides because that's the only way Storyline has ever worked. Use a screen reader on a regular webpage, though, and you'll see that the TAB button only navigates between interactive objects like a hyperlink or a button. (BTW, hyperlinks are still not tabbable in the "accessible player" and that's lame.)
You know what stinks if you're disabled? Being told that "accessibility in this course works differently than it does for you anywhere else." Forcing disabled users to use the TAB key to access everything was the real crime.
So, that's how Storyline works now, too. You tab between interactive elements. Now, if you want to read what's on the screen, you use the down arrow (in JAWS) or use similar commands in the other screen readers.
Here's an example of navigating a screen using the TAB button and using the down arrow. Using the TAB button (00:01 - 00:06) only stops at the two buttons. Using the down arrow, however (00:07 - 00:28), stops at every element on the screen and also allows you to interact with them.
So, in my estimation, this was a hard change for me to adapt to. Granted, I still have issues with the way accessibility is being handled, in general, but I'm starting to see this as progress (and so is my accessibility vendor who QAs our courses).
But I'm not seeing any auto reading at all. It just skips the content. Still on December's update to guarantee learners get all the information on the slide if using a screen reader.
In my experience, there's no "auto reading." You have to initiate the reading by using the down arrow (or the TAB key if you only want to navigate to interactive objects).
Hi I have been reading this thread as I am trying to set up and learning module the problem I am having is when I press the down arrows the text doesn't read. Any ideas. I am using Google chromevox as my screen reader
It looks like Chromevox is currently not supported with Articulate 360 content at this time. In case this helps, here is our list of screen readers that are supported:
Can you share more about what you're experiencing and expected behavior? As Lauren mentioned above, there's been significant enhancements to accessibility in Storyline 360 since Update 36.
This article helps with explaining the before and after user experience with these new features. Take a look and let us know if you have any specific questions!
24 Replies
I have raised a ticket with Articulate to look in to this issue.
Thank you for contacting our support team as well, Chris. I can see that Renato is taking a look now and working with you.
I am also experiencing a very similar problem to the one Chris describes. Initially, only buttons are recognised, although other items on a slide will be found and read by a screen reader if I use Tab+shift to work backwards through the tab order set up for that slide.
I'd be grateful to be notified of any solution to this issue.
Thank you.
Hi Barny,
I raised a service ticket with Articulate reporting this bug which they are investigating. They advise rolling back to the previous version (3.35.21017.0), I did this and it did sort out my issue- so you could try that.
To restore a previous version, when launching Storyline 360 hover over the open button and click the down arrow, you'll find the option to restore in there.
Thanks, Chris. I'd been struggling to get that to work as well but you inspired me to give another go and I was successful this time.
We are experiencing the same problem. We have several courses in which we have worked very hard with accessibility, but it seems that only the buttons work, the boxes with texts are not read by Jaws. We had restore a previous version...
Is there any update from Articulate on this problem I am also experiencing problems with this new update …
Hi Brett,
Thank you for inquiring about this issue! I see that our team is looking into this further, so I don't have an update at this time. A workaround that Chris mentioned is to roll back to Update 35 and has helped in the meantime.
You're in the right place, and we'll be sure to reach out with an update as soon as we can!
Yes I have also noticed this - text being ignored within the tab order
I am having the same issue as no text is being recognized and tabbed through in the preview. I would love to be updated on this issue.
Hello Jane and Melissa!
I'm eager to investigate! Storyline 360 behaves differently with screen readers since Update 36 (Build 3.36.21213.0). Rather than having to tab through each object for a screen reader to read off the object, screen readers will now read off the text boxes automatically and read objects when they're tabbed to. The objects that are highlighted when tabbing through a course are the interactive elements that require user interaction. For example, you'll see that buttons are still highlighted.
If you're not seeing interactive elements highlighted, please let me know. This includes buttons, navigation buttons in the Player, radio buttons, etc.
Hi,
And the tab order? if you have text and interactive elements that need to be read in order. for example, text field, button, text field. if the reading is automatic, how does it work?
In my case with jaws reader.
I was checking with Windows Narrator but the text is never read out - it just jumps to the interactive element in the slide.
Hi Juan!
You can customize the Tab Order so the objects are read in the order you prefer. Have you tried customizing the Tab Order?
Hi Jane!
Windows Narrator isn't a screen reader we currently support. Have you tried using NVDA or JAWS?
Here's my take. We've all gotten used to tabbing between all the items (text, buttons, images, etc.) on our slides because that's the only way Storyline has ever worked. Use a screen reader on a regular webpage, though, and you'll see that the TAB button only navigates between interactive objects like a hyperlink or a button. (BTW, hyperlinks are still not tabbable in the "accessible player" and that's lame.)
You know what stinks if you're disabled? Being told that "accessibility in this course works differently than it does for you anywhere else." Forcing disabled users to use the TAB key to access everything was the real crime.
So, that's how Storyline works now, too. You tab between interactive elements. Now, if you want to read what's on the screen, you use the down arrow (in JAWS) or use similar commands in the other screen readers.
Here's an example of navigating a screen using the TAB button and using the down arrow. Using the TAB button (00:01 - 00:06) only stops at the two buttons. Using the down arrow, however (00:07 - 00:28), stops at every element on the screen and also allows you to interact with them.
So, in my estimation, this was a hard change for me to adapt to. Granted, I still have issues with the way accessibility is being handled, in general, but I'm starting to see this as progress (and so is my accessibility vendor who QAs our courses).
But I'm not seeing any auto reading at all. It just skips the content. Still on December's update to guarantee learners get all the information on the slide if using a screen reader.
Are you using the down arrow on the keyboard with your screen reader?
I'm not pressing anything-it just never reads it!
In my experience, there's no "auto reading." You have to initiate the reading by using the down arrow (or the TAB key if you only want to navigate to interactive objects).
Hi I have been reading this thread as I am trying to set up and learning module the problem I am having is when I press the down arrows the text doesn't read. Any ideas. I am using Google chromevox as my screen reader
Hi Colin,
Happy to jump in to help!
It looks like Chromevox is currently not supported with Articulate 360 content at this time. In case this helps, here is our list of screen readers that are supported:
Hi - we are having issues with the tabbing on our scorm files - has this been fixed?
Hi Steven,
Can you share more about what you're experiencing and expected behavior? As Lauren mentioned above, there's been significant enhancements to accessibility in Storyline 360 since Update 36.
This article helps with explaining the before and after user experience with these new features. Take a look and let us know if you have any specific questions!
This discussion is closed. You can start a new discussion or contact Articulate Support.