14 Replies
Ashley Terwilliger-Pollard

Thanks Matthew for linking these discussions. I'll include them all in the report we have filed with our team. That specific report is about how alt text on the object's other states is not read by JAWS, both on Flash and HTML5. I'll keep you posted here and in the other discussions on this! 


Crystal Horn

Hey Ludovic. I'm excited to let you know that we just released update 16 for Storyline 360! It includes new features and fixes - check them all out here.

One of the fixes addresses an issue where the alt text on an object's other states wasn't read by JAWS.

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!

Ludovic M

Actually I think there is still a bug (even with the last version of today) :

I have set a button like that:
normal state alt "Chapter 1"
viewed state alt "Chapter 1 viewed "
disabled state alt "Chapter 1 disabled"

When I use the screen reader it always reads "Chapter 1."

If the button is disabled by default, it reads "Chapter 1 disabled" (=>ok)
If I enable it with a trigger, it reads "Chapter 1" (=>ok)
If I click on it it reads "Chapter 1 disabled" (=>not ok) as it should read "Chapter 1 viewed "

If I have done something wrong, please tell me and could you provide a .story file with states working well.

Leslie McKerchie

Thanks for chiming in and sharing what you are running into, Ludovic and Susan.

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.