Forum Discussion
Inconsistent behavior when using keyboard navigation
I have a project that I am adapting for accessibility and I've notice the focus order works differently when using TAB than when using the up and down keyboard arrows.
For context, in the project I have a menu slide with 8 hotspot buttons, each button opens a layer inside the same slide. The focus order is organized as it follows:
- Button 1
Button Layer 1 Content
Close Layer 1 Button - Button 2
Button Layer 2 Content
Close Layer 2 Button
Once inside the layer if I TAB to the close button to hide the layer everything works as expected. Which is the focus being on the next selectable button. If you are closing LAYER 2, your next TAB in the base layer will be to select the BUTTON 3.
The problem is when you are in the layer and use the arrows to read the slide when the SR reads over the close button, and then you hit enter to close the layer. The focus order of the base layer restarts completely starting to read from the top of the base layer.
The question I have is if this behavior is expected or why it could be happening only when using the KEYBOARD arrows.
Hi angieserratos2!
Sorry to hear your screen reader isn't following the Focus Order of your Storyline content!
The behavior you reported sounds similar to a bug we are tracking in Storyline 360. This bug is impacting the functionality between Storyline's Focus Order, and the NVDA screen reader. Do you mind clarifying which screen reader you're working with?
Also, if you're comfortable sharing the affected .story file, we'd be happy to take a closer look to confirm if you are being affected by the same issue. Feel free to upload a copy here in the discussion or privately through a support case.
We'll delete it from our system as soon as we're finished!
Thank you for replying StevenBenassi . We are using NVDA, so it could be. I would need to review sharing the file with my employer, it definitely would be helpful as we have encountered other issues.
Hi angieserratos2,
I'm happy to chime in. Thank you for your response!
I agree that it would be helpful if we could look at your project file. We can help with a nondisclosure agreement as needed to assist in troubleshooting the issue.
Let us know by opening a support case, and we'll share the steps regarding the NDA if required.
