How to Fix Storyline Layer Focus for Screen Readers

Questions answered by this guide

• ?Why does NVDA lose focus when a Storyline layer opens?
• ?Should I use Set Focus to fix a Storyline layer focus problem?
• ?What is the yellow box that appears with Storyline's Set Focus trigger?
• ?How do I test keyboard and screen reader focus in a Storyline layer?
• ?Where should focus go when a Storyline layer closes?
• ?How do I fix focus problems across a large library of legacy Storyline courses?

What you'll learn

• Don't start by adding Set Focus, find out where focus is going and why first
• Screen reader focus, keyboard focus, and the visible focus indicator are three different things to test separately
• Check the layer's own settings, especially its 'Prevent the user from clicking on other layers' property, before adding a trigger
• For a large legacy library, test representative patterns instead of every file

What's inside

Storyline developers and eLearning accessibility specialists testing or fixing screen reader focus behavior in course layers

1. 01The problem
2. 02The three things you're testing
3. 03Reproduce the issue before changing anything
4. 04Check the layer before using Set Focus
5. 05Testing Set Focus
6. 06Test the complete focus path
7. 07Legacy course remediation
8. 08Common mistakes
9. 09Testing checklist

Why it matters

Opening a layer in Storyline can move screen reader focus, keyboard focus, and the visible focus indicator in ways you didn't design. The common first response is to add a Set Focus trigger and point it at the layer. That can work, but it can also mask a different, real cause, like a layer property that was never turned on, and it introduces its own behavior that needs checking, including a visible yellow outline around whatever it focuses. The central rule worth keeping in mind: don't start by adding Set Focus. First find out where focus is actually going, and why, then decide what actually needs to change.

When you'll encounter this

• A layer opens over base content and NVDA seems to jump somewhere unexpected, or stops announcing anything new at all.
• A layer has interactive content, buttons, text entry, extra instructions, and you're not sure a screen reader user could find or use it.
• You've inherited a large library of Storyline courses built over time, possibly with inconsistent layer settings, and need a realistic way to check them.
• Someone on the team suggests adding a Set Focus trigger as the first response to a reported focus issue, before anyone has reproduced it.

Examples

Best practices

• Separate three different things when you test a layer: what a screen reader announces and where its virtual focus is, where keyboard Tab actually moves, and what a sighted keyboard user sees as the visible focus indicator. These can behave differently from each other. Fixing what NVDA announces does not automatically mean Tab order is correct, and neither one confirms the visible focus outline is where it should be.
• Reproduce the issue before changing anything, and do it in the published course, not the Storyline editor's preview. Test the trigger that opens the layer with keyboard only, then test it again with NVDA running. Open the layer and note exactly where focus goes, navigate through its content, close it, and note where focus returns. The editor doesn't reliably reflect how a screen reader interacts with the published output, so testing anywhere else risks confirming a problem, or a fix, that isn't real.
• Check the layer itself before adding a Set Focus trigger. Look at whether "Prevent the user from clicking on other layers" is turned on, since this one setting controls where focus goes when the layer opens and closes. Check the layer's Focus Order, whether its interactive objects have accessible names, whether anything has timing that delays when it becomes available, and whether the layer is meant to work like a dialog the learner must address or just additional content they can ignore. A missing setting is a different problem than a missing trigger, and the two aren't fixed the same way.
• If you do add a Set Focus trigger, know what it's actually for: pointing focus at a specific object when the layer's own built-in behavior doesn't already handle it. After adding it, test it the same way you tested the original problem, once with NVDA and a keyboard together, and once with a keyboard alone and no screen reader running. The keyboard-only pass is where you'll catch the visible yellow outline Set Focus adds around the focused object, which can look like a rendering glitch to a sighted user who doesn't know where it came from. Also confirm the trigger hasn't changed the order the rest of the layer's content is announced, manually setting focus can move an object ahead of instructions that were meant to come first.
• Test the whole path, not just the moment a layer opens: trigger, layer opens, focus enters the layer, layer content, any interaction inside it, layer closes, focus returns. A fix at one step can look complete while a different step is still broken, closing behavior especially gets skipped.
• For a large library of existing courses, don't try to open and manually test every file. Identify the highest-use or highest-risk courses first. Look for the same layer pattern repeated across multiple courses, most legacy libraries reuse a handful of templates. Test a representative example of each pattern, fix the underlying pattern once, apply that same fix to the other courses that share it, then retest a sample after remediation rather than assuming the fix behaves identically everywhere. A pattern that tests correctly in one course is a strong signal, not a guarantee, for every course that reused it, especially if any of them customized the pattern differently.

Common mistakes

• Adding a Set Focus trigger before reproducing the issue, so the actual cause is never identified.
• Testing only with NVDA and never checking keyboard-only behavior on its own.
• Testing only with a keyboard and never confirming what NVDA actually announces.
• Checking Focus Order in the editor without testing the published course, where focus behavior actually happens.
• Fixing what happens when a layer opens and never checking what happens when it closes.
• Assuming a visible focus outline and a screen reader's virtual focus are the same thing. They can point to different places.
• Fixing one layer and moving on, without checking whether the same interaction pattern repeats across other slides or other courses.

Practical checklist

• Open the published course, not the Storyline editor.
• Test the trigger that opens the layer with keyboard only.
• Open the layer and confirm keyboard focus moved somewhere sensible.
• Test the same interaction again with NVDA running.
• Confirm NVDA announces the layer's meaningful content, not just its title.
• Test every interactive element inside the layer.
• Check the visible focus indicator, with and without a screen reader running.
• Close the layer.
• Confirm focus returns somewhere logical, not lost at the top of the page.
• Retest after any change, including after adding a Set Focus trigger.

Frequently asked questions

Summary

When a Storyline layer causes a focus problem, don't start by adding Set Focus. Reproduce the issue in the published course first, with keyboard and with NVDA separately, and check the layer's own settings, especially "Prevent the user from clicking on other layers." Fix what's actually causing the problem, test the complete path from trigger to layer close, and if you do add Set Focus, check its visible yellow outline along with everything else. For a large legacy library, test representative patterns instead of every file, and treat a fix in one course as a signal for similar courses, not a guarantee.