Forum Discussion

annykaymelendez's avatar
annykaymelendez
Community Member
1 month ago

NVDA in Edge is reading one word at a time when using the arrow keys

I could use some help identifying what is causing the below issues. Attached is video of the issues and the Storyline 360 file.

Review link: Mandatory Subjects Process - Delete | Review 360

My current versions:

  • Storyline 360 - December 17, 2025, 3.107.35974.0
  • NVDA - 2025.3.1 (2025.3.1.53219)
  • Edge - 143.0.3650.80

Edge:

  • Using the keyboard arrow keys and NVDA, when I select the blue button "Am I required to notify Labor Relations..." with the "Enter" key it automatically jumps to the next puzzle button and opens it instead.
  • Using the keyboard arrow keys to navigate the focus order, NVDA is reading one word at a time. For example: the blue puzzle button says, "Am button, I button, required button, to button...
  • There are no issues when using a mouse to open the buttons.
  • There are no issues when using keyboard only to open buttons.

Chrome:

  • The example works great in Chrome with no issues. 

1 Reply

  • LeslieMcKerchie's avatar
    LeslieMcKerchie
    Staff
    1 day ago

    Hi annykaymelendez​ 

    Thanks so much for sharing the details, versions, and video. That’s really helpful.

    I tested your Review link using:

    • NVDA 2025.3.2
    • Edge 144.0.3719.115
    • Both Browse mode and Focus mode

    I wasn’t able to reproduce the behavior you’re seeing. In my testing, NVDA read the full button label as expected, rather than announcing one word at a time, and Chrome behaved the same way.

    I'm not sure if there's something specific to the combination of versions you are on. A couple of things you might try:

    1. Update NVDA and Edge to the latest versions and test again.
    2. In NVDA, confirm whether you’re in Browse mode or Focus mode when this occurs. (You can toggle with NVDA + Space.)
    3. Clear the Edge cache or test in a fresh Edge profile.

    If the issue continues after updating, could you let me know:

    • Whether this happens in a new, blank Storyline file with a simple button
    • Whether it only occurs in this specific project
    • Whether it occurs outside of Review 360 (for example, published for the web and hosted elsewhere)