Storyline 3 layers and tab order for acessibility

Hello,

I'm working on a project in SL-Three involving accessible content and slides with layers.
I've created custom tab orders so that the accessible learner selects an object to show the corresponding layer,
and then (with the objects on that layer next in the tab order) the learner can proceed through the layer's content.

It seems now though, that the tab order is ignored, and objects on the base layer are being tabbed through over again, before the yellow highlight
moves to the objects on the layer.

This is something new. On older publishes, which I have tested, the tab order was enforced and when you went to a layer, the
layer's objects were visited immediately if they were next in the tab order.

This no longer seems to be the case, as the base layer objects are repeatedly tabbed through.

Is this a known issue/bug ....perhaps since the latest update?

Thanks

-KM

5 Replies
Alyssa Gomez

Sorry you ran into this, Max. 

Our team is currently looking into an issue that surfaced in a recent update where the tab order in the HTML5 output (and Storyline Preview) restarts from the beginning when a layer is opened. 

I'll include your experience in the report filed with our team, and I'll keep you posted on the issue here. As soon as we get this fixed in Storyline 3, we'll let you know!

Leslie McKerchie

Hello Onoda,

Thanks for reaching out and letting us know you were running into a similar issue.

I was not able to locate a support case for you to pop in and check on things, but I do not have an update on the issue that was shared here.

This conversation is attached to the report so that we can share any updates with you here.

Jay B
Leslie McKerchie

Hello Onoda,

Thanks for reaching out and letting us know you were running into a similar issue.

I was not able to locate a support case for you to pop in and check on things, but I do not have an update on the issue that was shared here.

This conversation is attached to the report so that we can share any updates with you here.

This is a HUGE issue for us as well. Worked in SL2 just fine - worked in SL3 until a couple updates ago.