508 Compliance issue

Hi Hassy

we found the same thing recently - it would read Shutterstock 123455.png.  We had to go and rename every image to Picture1, Picture2 etc...it was a lot of work

Hi Hassy and Wendy - This sounds like an issue we would want to look further into. 

If you could share a .story file with our team here, that would be helpful.

Hi,

I found a work-around for it in the FORUM - 

Possible Workarounds for the Articulate Alt-Text Issue

Douglas Harriman

4 months ago

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.

Douglas Harriman

3 months ago

...

Was building a project in Storyline 2 and upgraded the project file to Storyline 3 to take advantage of Storyline 3-produced projects not having a tab navigation bug I was encountering with S2-produced projects. Found that after upgrading the project to S3, the buttons within it were now  exhibiting the same bug I reported earlier in this thread regarding multi-state image alt text in S2. Since I don't think my previous assessment of that bug was fully accurate, I'd now describe it as:

For images in S2 that have more than one state AND a different alt text for the image (outside of Edit States) and the Normal state (within Edit States), the Normal state alt text is what will be read by the screen reader; if the Normal state's alt text is blank (but detectable), the image file name will be read by the screen reader. The fix for this bug is to give the Normal state the desired alt text. The best method, I found, for applying this fix is to give the image the desired alt text BEFORE creating any additional states; that way all additional states will automatically be given that alt text (however, then if you want to change the alt text, you have to do so within the Normal state). 

In S2, this bug did not occur with buttons. The button's (outside of Edit States) alt text was being read, even though the button's Normal state alt text was blank.

I've found in S3 that the button's Normal state alt text is what is (initially*) read by the screen reader AND that if the Normal state's alt text is left blank, S3 will automatically populate that field with the button's original Timeline designation +1. E.g., when first created, a button appears in the Timeline as Button 1. Its Normal state alt text is automatically populated as Button 2 (even if you delete the alt text, it will be re-populated as Button 2). All other button states appear to have the auto-populated alt text of Button original # + 2. E.g., Button 1's hover state has Button 3 as its auto-populated alt text.

*Other observations:

In S3, if a button has different alt text for its Normal state and outside of Edit States:

If you tab navigate to the button, its Normal state alt text will be read until you hit enter or click on it, at which point its outside of Edit States alt text will be read.
If you hover over it, its outside of Edit States alt text will be read.
In S3 and S2, if an image has different alt text for its Normal state and outside of Edit States, its Normal state alt text will always be read, even after you hit enter on it.

In S2, if a button has different alt text for its Normal state and outside of Edit States, its outside of Edit States alt text will always be read.

I have another query with regards to 508 compliance. I have a quiz, how do I make the screen reader read the actual score and not just say "Your Score"

How do I give my Alt+Text for the actual score output?

Hi Hassy,

The score is a variable, so it can't be added to the alt text, but since it's text on the screen your screen reader should be reading it normally. Can you let us know what screen reader, browser and version of Storyline you're testing this all in?

Thank you. I never thought of that until you told me. Hmm..so i guess I shouldn't have given any alt+text in it. This will make the reader read the value in the text box itself. Thank you Hassy.

No problem Hassy, glad that you were able to fix it up!