Text/number inputs can be tabbed to even if they are on hidden layers or are not active on the timeline.

Hello Jhuny!

Thank you for attaching your file! You can control what a screen reader will pick up by unchecking the box next to Object is visible to accessibility tools.

To do this, right-click on an object and choose Accessibility from the drop-down menu. Uncheck the box next to Object is visible to accessibility tools. Here's what this looks like in action.

You can also customize the Tab Order to remove objects as well.

Hi Lauren,

But this is about the input fields, and I need to have them visible to accessibility tools. It's just when I change to another layer (and on the layers I've set 'Hide other slide layers') you can tab back to the input fields on the other layers, even though the layers and hence the objects on those layers shouldn't be visible.

Also notice you can't tab to input fields on layers that you haven't visited yet. I've also attached a new version with a random radio on Part 2 layer. When you get to Part 3, you can't tab to it because it's on a different layer. This is what I think should happen to input fields on that layer.

I'm not concerned with the tables.

And now this is the timeline version. The button jumps the cue point ahead to a point where there isn't an input field or a radio, but you can tab to the input and not the radio.

Maybe it isn't important. But it seems messy and I'm not the only person to notice this.

Of course this might just mean that Articulate Storyline isn't really the tool to be using if trying to create slides with multiple question types and many text entry boxes. But it's way too late in the project to jump ship. Be warned.

Hi Jhuny!

Thank you for sharing the extra projects!

When testing your project, I saw that after filling out the first table, the focus shifts from the buttons to the Player Tabs to the browser controls and the table.

There are three reasons for this.

1. The setting in slide properties to Prevent User from Clicking the Base Layer needs to be checked.
2. The tables and numeric/text entry fields are below everything else on the timeline. They need to be at the top of the timeline, so the user tabs to them first.
3.  The Focus Order shows objects on the second layer above the first layer. The Focus Order should represent how the learner will move through the course. 

I've made these changes to Inputs_and_Tabbing_with_radio and attached the updated project. Please let me know if you have any additional questions. 

Hi Lauren,

I'm not concerned about tabbing order right now.

I'm concerned that 'Text/number inputs can be tabbed to even if they are on
hidden layers or are not active on the timeline.'

In any case, it doesn't seem to have changed the fact that the user can
still tab to fields on other slide layers. Keep tabbing (or shift-tab to go
backwards), you will eventually get back to text inputs on slides that
aren't visible. I have set visibility of slide layers to 'hide other slide
layers' so these inputs shouldn't be "visible" (which should also mean
"accessible"). There is a radio button on Part 2 that cannot be tabbed to
unless you're on layer Part 2, which is what I expect should be the
behaviour of text inputs on that layer.

I think at this point it seems that there isn't really a solution here, and
that designers need to just avoid putting text inputs on different layers
so that this anomalous behaviour isn't possible for their projects (or be
okay with it and hope learners don't backwards-tab too far)

Regards,
Jhuny

Also, this is the project that has the layers in the "correct" order, which puts the input fields in the "correct" order, too. The tabbing issue still occurs.

Hi Jhuny!

I see a different output on my end. Here's a quick screen recording.

Do you mind also sharing a quick screen recording to see what is appearing on your end?

Hi.

I particularly hate my voice on recordings so sorry for not explaining what's happening in my screen recordings but here's what I'm seeing:

This image shows the Slide Layer Properties for layer Part 2. It shows that the property 'Prevent user from clicking on the base layer' has been set for this layer.

This video is of the slide, which I've published in Review https://360.articulate.com/review/content/0cac5714-cbe9-43c8-8335-eb5c64898b54/review 

The same thing also occurs to me when I publish to web. I also tried the Review version on Safari on my Mac.

Once the answers are submitted, the next table appears but tabbing (admittedly a lot of tabs are required) to get all the way back around to the first set of text inputs. I could have gotten there quicker using shift-tab to tab backwards but, either way, the inputs on the previous layer shouldn't be visible or accessible.

This particular activity I'm trying to support the learner to "go back" and change the Additional allocations after they have reflected on their answer. The Core allocations, however are set in stone, they just need to know what they are. The voice over audio explains this, which is why the design of the activity doesn't really allow me to split these up into separate slides, but also why backwards tabbing is important here.

Oh dear... got it... I just noticed that a newer version of Storyline had been released a couple of days ago and so I've updated Storyline and it seems to have fixed the problem on this slide!

I'm going to try to republish my actual project with this slide now.

Actually this is still problematic because, on this slide, I do need the base layer to be clickable.

And that doesn't change the fact that the option 'Hide other slide layers' should be the option to set to not allow text input boxes to appear on other slides, not 'Prevent the user from clicking on the case layer'. The label of an option should correspond to its action and, even in this latest version of Storyline, the option 'Hide other slide layers' isn't doing that for tabbing and text input (and your screen recording even demonstrates that, right at the end)

Hopefully the fact that selecting the other option to make the first option work properly means that it can be fixed?

Hello Jhuny!

After looking at the Peek video I recorded, I can see where the numeric entry fields appeared on the Finish Audio Layer. That was one layer where I hadn't changed the settings, so thank you for catching that!

I'm happy to hear that updating Storyline 360 did the trick for the numeric entry fields.

Lastly, Hide Slide Layers will hide all other layers (except the base layer) when the current layer is visible to the learner. Here's a description of each of the options in the Slide Layer Properties. 

NO THIS DOESN'T RESOLVE THE ISSUE!!! You claim that 'Hide Slide Layers will hide all other layers' but, from a tabbing (hence accessibility) point of view, this isn't the case. Your video shows it, and updating Storyline didn't help.

I need the base layer clickable. Please read ALL of my replies.

Thanks, Jhuny.

I'm able to see the behavior you are reporting as well. I've submitted this issue as a possible bug for further investigation.

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

Hi Jhuny,

Happy to share the good news with you! 

We just launched the newest version of Storyline 360 (Build 3.46.23620.0) this morning. This fixed the issue when a layer was set to hide other slide layers, learners could still tab to data-entry fields on the other layers.

The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline 360.

As always, we are happy to answer any questions you have by posting in this discussion, or you are always welcome to contact Support directly.