jaws / Tab order problem
Feb 06, 2019
By
Henrik Ax
Hi,
I'm trying to get JAWS to work with my Storyline project without success. Trying to make custom buttons to interact with JAWS but I can't get the "alternate text" in the tab order to be read out loud by the program.
What I'm hearing is the navigation buttons and search bar and when the custom button (shape) is highlighted the alternate text is not read out loud, only something like "button to button" (not the name of the shape/obejct).
Any ideas how to get this to work?
Regads
4 Replies
Hello Henrik,
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 "Button 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!
Hi,
Thanks for the reply.
When pressig spacebar, Jaws reads "spacebar" and not the alt-text, also there is a layer linked to the button pressed that starts right away.
Hi Henrik,
JAWS will narrate the keypresses too, but it sounds like you're not hearing any of the alt text regardless of where it was added. That sounds a bit different than what Alyssa described so,
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to our team here and we'll take a look.
We'll delete it when done troubleshooting.
Hi Henrik!
We've released a fix for this bug in Update 36 for Storyline 360! You'll find that a button's alternate text entered in Tab Order is now read correctly in JAWS. To receive the newest fix, you'll want to update Storyline 360!
This discussion is closed. You can start a new discussion or contact Articulate Support.