Alt text not being read by JAWS

Mar 30, 2018

Hi,

We are facing issues currently where some of our slide objects are not being read correctly by JAWS in Chrome (Or NVDA/Voice Over for that matter).

The "Myth" buttons in the attached story file are read as "Error Button" instead of their alt text, which is a pretty major issue.

I have tried recreating the buttons multiple times with new icons, but they still read as "Error Button". I have another file where other buttons are read different from their Alt text as well.

Please assist

8 Replies
Jeff Forrer

I tested this publishing from SL3, Update 2 , not using latest Update 3 as I have had issues with it.  Performed as expected with latest version of JAWS 2018.1803.24

I did change out the custom Sans fonts to OpenSans and published to HTML5 with Flash fallback here:

https://sales.alleni.com/client/test/story_html5.html

 

Matthew Bibby

Thanks Jeff. I didn't test this in JAWS, but I suspect slide one works fine and the problem occurs from slide 2 onwards.

I do need to do some testing to see how JAWS works with states alt text these days. Last time I tested it wasn't being picked up at all, but I know that Articulate have made some changes that should have fixed this (although I believe that if the alt text differs between states, e.g. selected, one would need to navigate away from the state and then back again for that to be picked up). 

Jeff Forrer

You are correct, it happens after slide 1. 

And yes we had issues with the Alt states with Update 1 so we had to do a workaround to make items read correct in JAWS, it was supposed to be addressed in Update 2 and it is better, but there still is a method to the madness, the latest Update 3 I have not used because of its instability, so I have not made the leap yet to see how it works with states there.

Lisa Spirko

Matthew Bibby, thank you so much for identifying  accessibility on the states as being the culprit. I have been experiencing the same problem for months and chalked it up to being an issue with NVDA. Now it works fine. :)

As Jeff noted in sharing the link, this is a bug, and it's frustrating that Articulate hasn't fixed it yet. This was identified over a year ago.

Thanks again, guys. This was a very helpful thread!

Lisa

This discussion is closed. You can start a new discussion or contact Articulate Support.