When NVDA Skips an Object in Storyline Focus Order

Questions answered by this guide

• ?Why does NVDA skip the first object in Storyline even though Focus Order is correct?
• ?Is NVDA skipping objects in Storyline a known issue?
• ?Does long text on the previous slide affect NVDA focus in Storyline?
• ?Do custom navigation buttons cause Storyline focus problems?
• ?How do I test whether an NVDA issue is specific to Storyline or to NVDA itself?
• ?Should I rebuild a slide if NVDA skips an object?

What you'll learn

• Correct Focus Order in the Storyline editor doesn't guarantee the published course behaves the same way
• Articulate's own Accessibility Maturity Plan documents a specific case: NVDA skipping the first object after a slide with long text and custom navigation buttons, still Planned, no official workaround
• Testing with the default Player Navigation Buttons or a second screen reader helps you isolate the cause, it doesn't guarantee a fix
• Not every NVDA Focus Order problem has the same cause, confirm before you act

What's inside

Storyline developers and eLearning accessibility specialists troubleshooting NVDA behavior that doesn't match a correctly configured Focus Order

1. 01Focus Order looks correct, but NVDA skips something
2. 02First confirm the problem
3. 03Check the Focus Order
4. 04Check the previous slide
5. 05Check custom navigation
6. 06Test with another screen reader when available
7. 07Decide whether it's a course issue or product behavior
8. 08What not to do
9. 09Legacy course remediation
10. 10Quick troubleshooting checklist

Why it matters

Correct Focus Order in Storyline's editor is a setting, not proof of what actually happens once the course is published and a screen reader is running. NVDA can skip the first object in the focus order, or land somewhere unexpected, even when Focus Order looks right on screen. Articulate's own Accessibility Maturity Plan documents a specific version of this: NVDA skipping the first object in the focus order after navigating from a slide with long text and custom navigation buttons, currently listed as Planned, with no official workaround. That doesn't mean every Focus Order problem has this cause, or that rebuilding the slide is the first thing to try. Confirm what's actually happening before changing anything.

When you'll encounter this

• Focus Order looks correct in the Storyline editor, but NVDA skips the first object, or an expected object, on the published slide.
• The slide the learner is arriving from has a large amount of text, or the course uses custom navigation buttons instead of the default Player Navigation Buttons.
• A learner or tester reports that NVDA "jumps around" or lands somewhere unexpected after moving to a new slide.
• You're trying to work out whether a reported focus problem is something in your course, or a documented Storyline behavior outside your control.

Examples

Best practices

• Confirm the problem before touching anything. Publish the course, open the published version, not the editor preview, and navigate with keyboard alone first. Then test with NVDA. Identify exactly which object is skipped or missed, and repeat the test to confirm the result is consistent, not a one-time glitch.
• Check the Focus Order itself using Storyline's own Tab Order panel, confirming the sequence matches what you'd expect. This guide doesn't repeat that process, see the Focus Order Guide for exactly how to check and fix it.
• Check the previous slide the learner is arriving from. Articulate's own Accessibility Maturity Plan documents a specific, confirmed case: NVDA skipping the first object in the focus order after navigating from a slide with long text and custom navigation buttons. If your slide sequence matches that pattern, this documented issue is a real possibility, currently listed as Planned with no official workaround. It is not the explanation for every Focus Order problem, so confirm the pattern actually matches before assuming this is the cause.
• If the course uses custom navigation buttons, test the same interaction using Storyline's default Player Navigation Buttons instead. This helps you isolate whether custom navigation is contributing to the problem. It's a diagnostic step, not a guaranteed fix, if the skip still happens with default navigation, custom buttons aren't the cause, and if it doesn't, that's useful information, not proof the custom buttons are broken in every situation.
• Test the same slide with a second screen reader where one is available, JAWS or VoiceOver alongside NVDA. This tells you whether the behavior is specific to NVDA or something a broader range of learners would encounter. One screen reader's result doesn't represent every screen reader's result.
• Once you've confirmed the problem, decide what kind of issue it actually is: a Focus Order configuration problem (fix it in the Tab Order panel), a screen reader testing issue (the test itself was inconsistent or set up incorrectly), a course design issue (how the previous slide or navigation was built), or a documented Storyline product behavior (like the long-text-plus-custom-navigation case above, which Storyline itself hasn't resolved yet). Each needs a different response, and mixing them up wastes effort.
• For a large library of existing courses, don't assume the same fix applies everywhere. Identify representative examples, confirm whether the same pattern, long text before a custom-navigation slide, actually exists in each one, prioritize high-use or high-risk courses first, test the proposed change on a small sample, apply it consistently where the pattern genuinely matches, and retest after remediation rather than assuming success in one course carries over automatically.

Common mistakes

• Rebuilding the slide or Focus Order immediately, before confirming what's actually being skipped or whether it's consistent.
• Assuming Focus Order is wrong just because NVDA skipped something. The setting and the screen reader's behavior are two different things to check separately.
• Treating one screen reader's result as representative of every screen reader.
• Changing multiple things at once, Focus Order, navigation buttons, and slide content, before identifying which one actually matters.
• Concluding a course is accessible simply because Focus Order looks correct in the editor, without testing the published version.

Practical checklist

• Confirm the Focus Order in the Tab Order panel.
• Publish the course.
• Test the published course with keyboard only.
• Test with NVDA.
• Identify exactly which object is skipped.
• Check the previous slide for long text.
• Check whether custom navigation buttons are in use.
• Test with Storyline's default Player Navigation Buttons where appropriate.
• Test with another screen reader where available.
• Determine whether the pattern matches a known Storyline behavior.
• Retest after any change.

Frequently asked questions

Summary

If NVDA skips an object even though Focus Order looks correct, confirm the problem on the published course before changing anything. Check Focus Order itself, then check the previous slide for long text and whether custom navigation buttons are involved, since Articulate's own Accessibility Maturity Plan documents that specific combination as a known, currently unresolved case. Testing with default Player Navigation Buttons or a second screen reader helps you isolate the cause, neither is a guaranteed fix. Decide whether it's a configuration problem, a testing issue, a course design issue, or a documented Storyline behavior, and only then decide what to change.