JAWs Reader is not reading ALT Text

Hello,

Using latest version of storyline 360 and jaws

I am experiencing the issue whereby JAWS is reading the alt txt within the button's state, not the Alt Text signify in the Tab Order screen. Just as Crytal's video shows above. 

Thanks for confirming Jason. 

This thread is attached to that report and we will update you here when we can.

Was really hoping this newest update would deal with the Alt Txt + States issue. According to the version history it doesn't look like it was addressed for this version.

This bug makes it so you have add the alt txt in two places: 1) In the Tab Order, and 2) within the accessibility tab of the object state.

Hoping it is still being looked at.

Absolutely Jason. 

It's still open with our team.

I wanted to share some information on how we define bugs and how we tackle them when they occur.

Hello, We had 30+ training modules in Rise, and I am in the process of learning Storyline to transfer them to Storyline for Accessibility purposes-

I am trying to make sure I am up to speed on everything in Storyline that is Accessible/508 Compliant, and where there are bugs/issues that I should be aware of on the front end until we are able to get a screen reader to check our modules as we go-

Has this issue in this thread been resolved? Just wondering as I am making a list and I didn't see a final comment, but I wasn't sure if  that was typical or not and I just wanted to check, thank you!

Hello, Arin! 

Accessibility is important to us, and we still have more to do in Rise. We're working hard to add features that will meet Web Content Accessibility Guidelines (WCAG). So far, we’ve increased the contrast for built-in course features, added alt text for images, and added keyboard-accessible navigation. And we’re currently working on full screen reader support. 

Now, let's focus on Storyline. The bug Leslie referenced earlier in this conversation relates to custom buttons. When you add alternate text to a custom button, JAWS doesn't read that correctly. Instead, it reads the default alternate text. 

For example, JAWS will say "Buton 2 button, to activate press spacebar". Pressing spacebar will make JAWS read the alternate text entered in the Tab Order window or Accessibility menu.

Let me know if you have any more questions about that bug, or other Storyline accessibility questions. I'm here to help!

Will these accessibility issues mentioned above also be deployed to users of Storyline 3? We have a manager who uses JAWS and we're also a state health agency that has to comply with ADA and WCAG rules. 

I'm running the newest version of Storyline 360 and have had similar issues.

Here is a workaround:

1. Open up and edit the States for the button/image.
2. Select Make sure the Normal state is selected.
3. Right-mouse click on the object and select Accessibility.
4. Type in the Alternate text.
5. Click on "Done Editing Status" in the States panel.

From my experiments it seems like using Tab Order doesn't always associate the alt text with the Normal State.

I don't have JAWS and only tested this with NVDA. By the way I discovered I can test each slide with NVDA using the Preview option without having to Publish the file.

1. Preview a single slide
2. Run NVDA
3. Tab through the slide to double-check how alt text and tab order is responding.

Hi everyone!

Quickly popping in to this discussion to share that JAWS reads ALT Text correctly in Update 36 for Storyline 360! Like many of you have seen, in the past JAWS wasn't reading a buttons ALT Text entered in Tab Order. 

If you haven't updated Storyline 360 yet, here's how!

Hi Lauren, We are still seeing an issue with the alt text on system generated button states. If you create your own button state and add alt text to it, it seems to read fine. If you use a pre-built button state and add alt text to it, it doesn't seem to read.