My play and pause button is being read as "button to button" instead of "Play button" or "Pause button" by JAWS. I've checked the alt text and each button have the proper labeling but JAWS is not reading it as such. Has anyone ran into this issue. Is there a workaround for it? Currently, my learners who use screen readers will not know what these buttons are.
Hi, Claire. So sorry you're running into this behavior!
We've identified an issue where JAWS doesn't read a button's alternate text correctly. Instead, it reads the default alt-text. For instance, JAWS will say "Buton 2 button, to activate press spacebar." Pressing spacebar will cause JAWS to read the alt-text entered in the Tab Order window or Accessibility menu.
I'll tag our conversation to this bug's report so we can keep you updated with any new information. If I can be of any other help, please don't hesitate to reach out!
I don't have an update to share just yet, but you're in the right place to stay up-to-date on our progress. You'll be notified immediately since you're now subscribed to this discussion!
I am using buttons throughout as a means to navigate layers. When the alt text doesn't get read this causes the navigation to be invisible to a listener. Any resolution of this issue?
I saw Matthew and Leslie helped you out in this discussion with a similar issue on NVDA. Our team is continuing to work on the issue where a button's alternate text entered in Tab Order is not read by JAWS. We'll let folks know as soon as we have more info to share on that!
10 Replies
Hi, Claire. So sorry you're running into this behavior!
We've identified an issue where JAWS doesn't read a button's alternate text correctly. Instead, it reads the default alt-text. For instance, JAWS will say "Buton 2 button, to activate press spacebar." Pressing spacebar will cause JAWS to read the alt-text entered in the Tab Order window or Accessibility menu.
Does this description match what's in your file? If you're able to share your .story project, we're happy to dig in and let you know what we find!
Yes, thank you.
Thanks for confirming that detail, Claire!
I'll tag our conversation to this bug's report so we can keep you updated with any new information. If I can be of any other help, please don't hesitate to reach out!
Was a solution provided for this problem?
Thanks for checking in, Jackie!
I don't have an update to share just yet, but you're in the right place to stay up-to-date on our progress. You'll be notified immediately since you're now subscribed to this discussion!
This is also happening for me when using NVDA screen reader in Storyline 360. Any resolution at this time?
Actually, it reads the alt text when I press the back tab key combo. Why?
I am using buttons throughout as a means to navigate layers. When the alt text doesn't get read this causes the navigation to be invisible to a listener. Any resolution of this issue?
Hi Laurie,
I saw Matthew and Leslie helped you out in this discussion with a similar issue on NVDA. Our team is continuing to work on the issue where a button's alternate text entered in Tab Order is not read by JAWS. We'll let folks know as soon as we have more info to share on that!
Hi all!
I'm happy to report that in Update 36 for Storyline 360, a button's alternate text entered in Tab Order is read correctly by JAWS!
If you haven't updated Storyline 360 yet, here's how!
This discussion is closed. You can start a new discussion or contact Articulate Support.