Forum Discussion
Problem with Set Focus trigger
I wouldn't use set focus to achieve that just set the text in the focus order
That's my conclusion. I'm reviewing several courses and it seems that when SET FOCUS is used to automatically read a non-interactive text box it's a little buggy.
The authors' intent was to save those using a screen reader the requirement to arrow down to read the text box (as is the case with the focus order).
Hi IanMarkiewicz,
Thanks for sharing the details, and great catch from PhilMayor on the focus order approach.
You’re right, the Set Focus trigger can act unpredictably when it targets non-interactive text boxes. The yellow outline you’re seeing is the browser’s visual focus indicator, which can flicker or appear in unexpected spots when Storyline shifts focus dynamically.
For the most reliable screen reader experience, we recommend using the focus order alone rather than a Set Focus trigger. That way, learners using assistive tech can still reach the text naturally when the layer opens.
If you’d like us to take a closer look at your setup, you can share a sample slide with us in a support case.
Hi Eric, I hope you're well.
I see you have said this 'For the most reliable screen reader experience, we recommend using the focus order alone rather than a Set Focus trigger.'
And I would ask, what it the point of the Set Focus trigger if it cannot be used properly for screen readers. What if your screen has complex interactions or multiple layers?
My experience, until now, is that the Set Focus trigger works very well, but I've noticed recently that it will go to the wrong button and I have no idea why.
I would also be great if the browser’s visual focus indicator would only appear when you use the keyboard and not when using the Set Focus trigger.
Has there been reports that the Set Focus trigger is not working as well as it used to?
Thanks.
