Forum Discussion
NVDA Storyline 360 Software Simulation Issue
Hello all,
I have been working on a software training course for a while, but I cannot share the product file, so I have tried my best to replicate the issue with a brief PowerPoint activity. My current project file has 6 scenes and 452 slides. I am looking for the easiest fix to the issue at this point, while avoiding backtracking on work. Any assistance would be GREATLY appreciated as I am close to my wits' end. Below is a synopsis of the issue, the fixes I have tried, and the attached PowerPoint Activity project file.
Build Background: I used the screen recording features in Storyline 360 to create both Try Mode Steps and Test Mode Steps for scenes in the course. I turned off Show Animation in the Capture Action Fine Turning. I have ensured that hotspot and text entry interactions are at the top of the timeline, above all other elements. I have deleted triggers where possible, but some of the Play Video Screen Recording Action When the User Clicks Hotspot 1 remain, as the program won't allow them to be deleted even after turning off the animations, so I have disabled them. I had to make additional cover-ups to hide employee IDs and information, as I did not have a fake user account. The cover-ups have been hidden from accessibility tools.
Issue: When navigating the course with NVDA and Microsoft Narrator, the Try Again layer keeps deploying as the user selects the hotspot button for a second and announces "Incorrect," which will lead to annoyance and confusion for the learner. The Try Again layer does not deploy in the Test Mode Steps scenes, but it does in the Try Mode Steps scenes. The Try Again layer does not deploy when using keyboard navigation without a screen reader enabled. I do not want to remove the Try Again feedback, as it is important for sighted users.
Triggers on Base Layer:
- When the user clicks outside Hotspot 1 - Show layer Try Again
- When the user clicks Hotspot 1 - Jump to slide next slide
- (Disabled) When the user clicks Hotspot 1 - Play video Screen Recording Action
Triggers on Try Again Layer:
- When user clicks Try Again - Hide layer this layer
Solutions Tried But No Success:
- Running the file as a published SCORM in test environment, Review 360, and in preview mode- Try Again layer still deploys in all environments.
- Expanding the hotspot area beyond the identified bounds.
- Changing the order of the user clicks outside Hotspot 1 and the user clicks Hotspot 1 triggers on the base layer but Storyline 360 does not allow me to change the position of these triggers under Hotspot 1 in the trigger menu.
- Adding back in the correct layers of the screen recording as shown in scene two of my attached example.
4 Replies
Hi jpatrickomes would you be able to upload a Story file with just one slide, removing any sensitive data, but can demonstrate the issue? This is by far the best way for people to be able to trouble shoot the issue.
Reading the issue I didn't understand what the trigger for showing the Try Again layer was when using a screen reader? Which key are you selecting that triggers the Try Again layer to show? I didn't think it would be possible for keyboard and keyboard + screen reader user to trigger the Try Again as it requires the user to use the mouse pointer outside of the designated target. If you can provide a file that demonstrates this, I should be able to help with troubleshooting the issue.
Thanks,
Sam- jpatrickomesCommunity Member
Hi SamHill , I had attached the made-up story on PowerPoint that is doing the same thing, and I don't know why it didn't stay on my post. I have attached it to this reply.
- SamHillSuper Hero
Hi jpatrickomes you have found a bug. I can confirm this behaviour also occurs with JAWS 2025, but does not occur when just navigating with keyboard and no screen reader. For some reason, the combination of screen reader + keyboard is somehow activating the "click outside" trigger.
I will log an issue with Articulate and direct them to this post and your storyline file.
- SamHillSuper Hero
Hi jpatrickomes looking into this further, the issue is not just isolated to simulations. This issue affect all instances of "clicks outside". The trigger is executed when using screen reader + keyboard.
Case: 01329675