In Storyline 3, I have a button which is in disabled state, and when I use NVDA or Jaws, I would like the screen reader to tell "The text on my button. Disabled". I have tried to change alt in disabled state, but it doesn't work.
Not really. You'll see in that thread a workaround I tried but it didn't really work. The other option is to have completely seperate buttons that you show and hide using triggers rather than using states, but it's a pain to build and maintain. Hopefully Articulate get's this resolved soon.
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!
Thank you for the answer. I am in France, so I get the french version of the Storyline 3 versioh history page and I don't see the history for the latest Storyline 3 published in March 2018. Is there a way to access the english version of ST3 version history?
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!
The update fixes the the alt read on other states, so I it can tell on NVDA: "Help disabled, button". It is better but that would be even better if it could tells "Help, button disabled" like it does with HTML aria-disabled="true"
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.
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.
14 Replies
As noted here, states are picked up by JAWS. This is on Articulate's radar but I don't believe it has been resolved yet.
Thank you for the answer, is there a workaround ?
Not really. You'll see in that thread a workaround I tried but it didn't really work. The other option is to have completely seperate buttons that you show and hide using triggers rather than using states, but it's a pain to build and maintain. Hopefully Articulate get's this resolved soon.
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!
Thank you Ashley.
Unfortunately this problem is not solved in Storyline 3 March update :-(
Hi Ludovic,
We'll let you know here once it is resolved, and you can also always check the Storyline Version history here for Storyline 3 and Storyline 360.
Hi Ashley,
Thank you for the answer.
I am in France, so I get the french version of the Storyline 3 versioh history page and I don't see the history for the latest Storyline 3 published in March 2018.
Is there a way to access the english version of ST3 version history?
Hey Ludovic,
Sorry about that. Our translated versions run a bit behind the English version.
If you scroll all the way to the bottom of the page, you should be able to switch the language:
I hope that helps :)
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!
The update fixes the the alt read on other states, so I it can tell on NVDA: "Help disabled, button".
It is better but that would be even better if it could tells "Help, button disabled" like it does with HTML
aria-disabled="true"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.
I am experiencing the same thing. When a button is normal it reads the alt text, if it is selected, it reads the same alt text as the normal state.
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.