Base layer accessibility issue

I'm having an issue where the screen reader reads the base layer when you click on a child layer of the base layer. 

The user is suppose to read text on the base layer and click one of several buttons. The screen reader reads this fine. But when the user clicks a button and goes to a child layer of the base layer, the screen reader re-reads the base layer content (which is mostly hidden on the child layer), before it will read the content on the child layer. 

This makes it very confusing. Is there a way to not have the screen reader re-read the content of the base layer when they click on the child layers? 

2 Replies
Elizabeth Pawlicki

Hi Errol! It's hard to know exactly what's happening without seeing your slide, but it could be a couple of things, either the focus order of the slide content, or your slide preferences. It sounds like your question might be similar to the one posted here. You may want to try what Sam suggested in that thread as well:

If you want the layer to behave more like a Modal window, you need to select the Layer property "Prevent the user from clicking the base layer". Not only does this prevent the user from clicking on anything but the current layer, it means that screen readers will only see what is in the current layer. In this instance, the Focus Order is not as important, and you only need to be concerned about the order of elements within the current Layer, as objects in the base (and other layers) are excluded.

I hope that helps or gets you started in the right direction!

Tanudja Gibson

HI Elizabeth

Preventing clicking on the base layer while on a layer negates one of the great creative functionalities of Storyline 360. It limits creativity in how content is presented. Many are suggesting that instead of tabbed interactions we don't use layers, just add more slides. If you also stop using animations in layers (as suggested in other discussions) and make all text boxes/objects appear at the start of the layer timeline, then that reduces creativity further. 

I don't see any developments planned to overcome these limitations in the Articulate roadmap - what's the point of buying a Storyline subscription if we can't use the very functionality that makes it different from PPT.  

The lack of frank and detailed documentation about what can and cannot be achieved (and how to do it) is also very frustrating. I'm spending hours trawling through forums just to work out how to make basic stuff (like audio narration) work with screen readers and sighted users.