Accessibility Alt-text not working on static images

Sep 20, 2021


I'm working in storyline and the alt-text only seems to work for action buttons. It doesn't pick up static pictures on the slide. 

I'm creating a guided practice which simulates a software environment. So, I take a screenshot of the software page and fit it to the stage screen of storyline. Then I take a screenshot of the button in the software environment that will be the button that the user will click. The trigger will advance the user to the next slide that will have the next screen of the software environment with a button that the user will click, and so on... This will be a guided practice, that simulates the real environment. 

My issue is that the screen reader is not picking up the static picture which is a screenshot of the software page that is fitted it to the stage screen. I have the alt-text applied, with the checkbox selected. I'm using google chrome and the NVDA screen reader and I have also tried the Chrome extension screen reader. Both read the buttons and other interactive fields in the player, but the static pictures that have no interaction are not picked up by the screen reader. Is there something special that you have to do for static images that don't have interaction to be picked up on screen readers?

Just for clarity, the images that have no interaction and the buttons are both images taken from snagit. They are both configure with alt-text the same way. However the static images without interaction are not picked up by the screen reader; but the images that act as buttons, with triggers applied to them, are picked up on the screen readers.

3 Replies
Elizabeth Pawlicki

Hey Errol! I ran a quick test here and did a short screen capture for you, using a couple of screenshots from Snagit where the center image is a clickable item that navigates to the second slide. It worked for me but I will mention that since the background image isn't an interactive object, it's not part of the focus or tab objects for the screen reader, so the way the user would navigate to have the screen reader announce it it is by using the "down" key rather than tabbing. I included my file in the Review link above if that helps you at all! 

Errol Mackey

Hi Elizabeth! Thank you very much for this thorough explanation. My project works as yours does when using the arrows. I thought that since the static images were part of the Focus Order, that they would be picked up in the tabbing function.

I have one more question, why is the static content (in your example the image "software interface") read as "Clickable main landmark graphic software interface"? I don't understand why the software interface image is listed as clickable when it is just a static image with no trigger. Wouldn't that confuse users who now think that the image has a functional purpose with the word "clickable" being used to describe it?

Leslie McKerchie

Hi Errol,

I understand how that announcement may seem confusing, but it's letting the screen reader user know what is on the screen. 

This is an ARIA landmark. Screen reader users can understand items on the screen and navigate to them.

Simon mentions it here:

Recent accessibility improvements in Storyline 360