I am testing the accessibility features on a storyline file using JAWs 14.0 demo version. I am using IE 10 to open the published HTML file. The JAWs reader is not reading my ALT text for my images. It is reading the file name in the timeline instead. I have selected to have the object visible to accessibility tools and have entered a description. What could be causing the JAWs reader to ignore my description and just read the file name?

I see the same thing when my image is used like a button. If no trigger is associated with the image, Jaws reads the alt text. When a trigger has been added to show a layer when the user clicks on the image, the filename of the image is being read by Jaws.

I was having a similar problem, though not sure how similar my situation is: I was using images as buttons, giving them multiple states and applying triggers to them. NVDA was reading my image file names instead of the alt tags I'd given the images. I was able to resolve the issue by applying the alt tag not only to the image, but also, specifically, to the instance of the image within its Normal state. Also noticing that if I have separate alt tags on the image and the image's normal state, the normal state's alt tag is what gets read.

Hi Ashley, are there any plans to support the NVDA reader? Thanks!

Hi Janet, The answer from Articulate will likely be 'No'. But the good news is that you don't have to worry about whether or not NVDA is supported by Articulate because from my experience any Storyline bugs that have occurred in NVDA have also occurred in JAWS. So I don't accept 'We don't support NVDA' as an answer. I will always ask them to actually test the issue in JAWS and to confirm if the same behaviour occurs. In my experience, it always does. In relation to Douglas' post, I can confirm that this issue definitely occurs in Storyline 2, whether you're using NVDA or JAWS. The Articulate team have no intention at present to fix this bug in Storyline 2. Instead they want you to pay to upgrade to Storyline 3 in order to fix the bug. This is quite odd, as most software companies fix bugs in their software as free updates. I haven't tested Storyline 3, so I can't confirm whether it has fixed the bug and whether this is the case in both NVDA and JAWS. Personally I don't have the time to bother testing it in the free trial myself... Since this bug has been around for 4 years, I'm now very accustomed to using the dodgy workarounds that we had to devise to overcome the issue (such as the nifty one that Douglas mentioned). But if you do have time to test Storyline 3, let me know how you go with NVDA.

Hi Sandy and welcome to Heroes! It sounds like you've had things set up correctly in terms of selecting that the object is visible to accessibility tools, and including text within the Alt text box below: If you'd like us to take a look at your .story file, please share it here.

JAWs Reader is not reading ALT Text | Articulate

JackieWaskew168
Community Member
5 years ago
Hi Lauren,

We are using JAWS 2019. For a button with the built-in states, we put Alt Text on the built-in VISITED state, the text simply says 'you have already visited this section.' We then trigger the Visited state change with the button press. When revisiting the button with JAWS after the Visited state is triggered, the Normal state alt text is read.

If we do the exact same steps, but create a new Done state (add the same alt text, trigger, etc.) the Done state alt text is read by JAWS.
LaurenConnelly
Staff
5 years ago
Hi Jackie!

I appreciate you describing the specifics! We've logged a bug where JAWS only reads the alt text for a normal state, which is exactly what you're running into!

It's hard to nail down a timeline to share since we have an in-depth process in place for tackling bugs. What I can do is add your comments to the report and since you're already subscribed to this discussion, you'll be notified when we do release a fix!
VinceScoma
Community Member
5 years ago
Hi Everyone,

I am happy to share that we just released the newest version of Storyline 360 Build 3.37.21453.0, which fixed the issue where screen readers would only read the alt text for the normal state of an object.

The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline 360.

As always, we are happy to answer any questions you have by posting in this discussion, or you can contact our Support Engineers directly.
KatieRiggio
Staff
5 years ago
Hi All,

Update 11 for Storyline 3 is live: We fixed the issue where JAWS would only read alt text of the Normal state.

Tour the release notes for more details

Take these steps to update Storyline 3 and see the latest enhancements

As always, we're here for any questions!
EmilyMcDonell
Community Member
5 years ago
Hi there! I have just updated JAWS and Storyline 3, and am testing a published course. JAWS is not reading the image alt-text at all. Currently there are no states other than Normal on any of the images, object is visible to accessibility tools, and alt-text is set. Still, when I arrow to the image, all I get from JAWS is "graphic." Any suggestions? TIA!
- LaurenConnelly
  Staff
  5 years ago
  Hi Emily!
  
  The JAWS screen reader adds graphic or button to object descriptions when it's narrating a published course. This is how JAWS is designed to operate for accessibility support.
  
  For example, JAWS adds graphic to descriptions of pictures, screenshots, and characters, since these elements are graphics. Similarly, JAWS adds button to descriptions of buttons and objects with click triggers.
EmilyMcDonell
Community Member
5 years ago
Hi Lauren! The issue is that it's not reading the actual alt-text - ALL it's saying is "graphic." I have alt-text in the correct place, but it's not being read. I did submit a case with some example slides, so hopefully that will help clear things up. Thanks so much!
- MelissaSurezdel
  Community Member
  3 years ago
  Hello Emily,
  
  I'm having this exact same issue. Could you find a solution for your this?
  
  Thank you!
LeslieMcKerchie
Staff
5 years ago
Thanks for explaining what you are seeing and I appreciate you letting us know that you've reached out to the support team, Emily. I can see that you are working directly with Johnrey.
LeslieMcKerchie
Staff
3 years ago
Hi Melissa,

I was able to take a look at Emily's case and see that it was specific to Storyline 3. It looks like you are using Storyline 360.

I want to take a look at your project file to investigate what's happening with your permission. You can share it publicly here or upload it to me privately. I'll delete it when troubleshooting is complete.
JayantTiwari
Community Member
3 years ago
whenever I put alt-text on content, the focus goes elsewhere.

Please share a solution for this issue.

we are using jaws 20 and storyline 360.
MariaCS
Staff
3 years ago
Hi, Jayant.

I'm happy to help!

Can you expand on what you're experiencing when using JAWS? Is this happening with every object that has alt text?

If you can share a screen recording or the .story file, it would help us troubleshoot your specific scenario. You can share it privately through a support case if you prefer.