Base layer accessibility issue

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!

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.

I agree!  The accessibility documentation is nearly impossible to piece together.  Their articles and how-to's focus on basic information and not the little details that actually make it work.  Hope they look into this a little more!

Hi Mind,

Thank you for reaching out and I appreciate you sharing your thoughts with us. I'll be sure to pass your feedback along to our team as we want our accessibility documentation to be clear and helpful to our customers. If you need any assistance in the meantime, please let us know here or privately in a support case!

We are developing a course for blind people, so the assessment scores and other results should be read using screen reader tools such as NVDA. But currently, the values stored in the variable are not reading out in screen reader tools. We need an expert's advice to resolve this issue. Kindly do the needful.

Can you post the slide or a screenshot of the focus order?

That is not the results slide can you send one of the results slide?

Sent from my iPhone

please find snapshot of result slide

That has too many items on it and they have not been ordered. You need to clean it up and remove all the things that are not text and don't have alt tags.  I suspect you may have prevent user from clicking on the base layer for the layers, really difficult to say without the slide but my first job would be to clean it up first.

Hi Phil, 

I hope you find this message. Have you checked the source file? We are eager to hear your response.

I had a quick look; you haven't rationalised the objects in the focus order and have other variables on the slide that I think you don't need. As I mentioned before the first thing you need to do is rationalise the focus order to only have the objects you want read

It is difficult to make a drag and drop accessible.  There are examples on here. You can use the drop correct and drop incorrect states to announce this.