Tab Highlighting / Focus order

Any possible way you could share the SL file?

Hi, sorry I'm not able to share it. But obviously you can recreate the yellow boxes just by pressing tab. I just want to get rid of it... But there is an update. 
In the previous storyline project where pressing tab did not highlight anything with yellow boxes at all; I attempted to recreate exactly the same classic player settings. This still didn't work. So I exported the player, and imported it into my project. Now pressing the tab doesn't start the yellow highlights. 
And I have no idea why. I wouldn't know how to see why an exported previously classic player file would work.  I can attach the export if you want to import it and see that pressing tab does nothing... 

That's alright.  I was mostly curious how your Focus Order is set up. Perhaps you could provide a screenshot?

Ok, I think I got something put together that checks off each of your requirements:

• Pressing the Tab key moves the learner onto the next layer

• Pressing the Tab key moves the learner from one data entry to another data entry field

https://360.articulate.com/review/content/912dbfab-5b9a-42d9-8126-c0230f76e2fd/review

The trick here was to ensure a custom focus order is in place that only cycles through the data entry fields and the DONE buttons...

...Why a DONE button? In order to take advantage of the when "User presses a key..." trigger, it requires something to be clicked first.  By incorporating a conditional button, and triggers noting those conditions, moving from slide to layer to layer is now possible. 

Let me know if that makes any sense 😅

Thank you. What you're saying makes sense. Unfortunately, the issue is the yellow highlighting box, and even with a custom focus order, if you keep pressing tab, you'll start to get other areas of the player and the screen even into Edge (in my case).
I imported the old player that was used, so although I'm stuck using a classic player (not just selecting classic player in my current version, but actually importing an old one from a previous project), I can use the tab key to move to the next slide without using a done button and with no highlight anywhere. Though I would have been happy using a button, the software we are simulating is operated by keyboard only, mainly enter and tab. I'm assuming there is a change in the coding of the player XML file somewhere that either engages the use of tab  key as an accessible feature or disables it? Since I'm not going to  compare the codes line by line, and I'm sure it's changes a lot since my older project.. I'm happy with this 'solution'. For the future though, I'll bear the custom order in mind when clients are happy with the yellow highlighting boxes. It's not a bad feature, but I'm surprised the tab key is used for this, it would be good to have a choice of using a chosen key to help highlight where someone is if they get lost. I understand why it's the tab key, but unfortunately so many systems use the tab key for data entry, and clients may not want the yellow box at all because it doesn't appear in the real thing.
Thank though for taking the time to answer. 

It was worth a shot!  Hopefully a feature request has already been put in for assigning other keys to cycle through focus order content - you've certainly made a strong case!

Cheers

Thanks for sharing your thoughts, Elizabeth, and Daniel for popping in to help. This Storyline feature (tab key for interactive navigation) is in alignment with accessibility tools.

The Tab key is commonly used for accessibility and reads the next focusable item (link, button) in screen readers:
NVDA
JAWS
Voiceover

I hope this helps!