Accessibility
591 TopicsStoryline Keyboard Navigation not working with Buttons
Hello everyone! Can anyone help resolve this accessibility issue? I am creating a scenario interaction where the user selects 1 of 3 answer choices. The selection and submit interaction work with keyboard and mouse, but when I try to navigate on the keyboard using the "Tab" key, I can only select the first (not second or third) button. I duplicated the second and third from the first button, so I don't know what happened/why it is not selectable with the keyboard? The buttons are not stacked on top of each other They have the "visible by accessibility tools" enabled Triggers include: emphasize, hover for audio, hover for character state changes, and submit interaction but those are the same for the functional first button Anyone have ideas on how to fix this? I would prefer not to have to recreate the buttons and relink all the triggers/recreate the feedback layers. Storyline file is attached.Solved70Views0likes7CommentsStoryline 360 - keyboard accessibility - tabbing to select the continue button on answer layers
I have 12 questions included in a Storyline 360 course that are either sequence drop down, multi choice or single answer that all act in the same way, no matter what changes I make for keyboard navigation in the focus order. I wanted to check if this is a known issue, bug, something I'm not doing correctly and if there are any options for me to resolve this and make it more accessible by keyboard navigation only. All the other accessibility components work ok and the course includes a voiceover throughout so the focus order of text paragraphs to enable a screen reader to pick them up is not needed. The focus order only includes the selectable answers, buttons, weblinks, and continue buttons on the answer layers for correct, incorrect and try again. Once any of the questions have been answered and the feedback layer pops up, the next keyboard tab goes to the resources, and it takes two more presses of the tab key to get to the continue button on any answer layer, no matter what order I put the two/three continue buttons in the focus order, or if I change the layer order. This isn't ideal for accessibility as I'd like the first tab to go straight to the continue button, rather than it taking three tabs to get there. I found another known bug with the menu states included in this forum, which require two tabs instead of one, even when removing the accessibility tick box so the visited or completed states don't show in the focus order. I'm wondering if this is a similar issue/bug. Does anyone know if this is an issue, bug or something I'm not doing correctly? Is there something else I can do to get the first tab to be on the continue button? Or would you suggest programming a different key to get past this issue, ideally without too much extra instructions for the user needing to be added in, for the workaround?133Views0likes4CommentsUnlocking Videos and blocks after going through the Rise course once
Hello everyone, I’m wondering if there’s a way to configure Rise and/or Saba LMS so that once learners have completed a Rise course, any subsequent launches allow full access to all blocks, videos, and sections. Ideally, learners would be able to revisit specific content freely—whether to reread, rewatch, or review—without having to go through the entire course again. This is important for accessibility purposes. Has anyone implemented this successfully or found a workaround? I did some research and it is said it should be set on Saba LMS. Please advise Thanks in advance for your help!8Views0likes0CommentsTab function in 360° image
There was a known bug with 360° images where the tab function would freeze and you couldn't get out of the image. I don't know if this is resolved, yet, but I tried to make a guided tour of the image to support the tabbing function. I cannot get it to work on the guided tour. What is the trick to tabbing through the hotspots and markers?Mute controls across all browser windows launched by the course
Is this even technically possible? Problem: I want to be able to allow learners to have a single audio mute control across a whole course but not impact the PCs own mute settings - when introducing Text-to-Speech to SL360 slides and also Captivate Web Objects launched from button triggers. Any thoughts from the community seeing as this is not wholly Articulate content? Thanks. Currently, it will require: a mute button for the SL360 player, for the slides of the course a mute to be used each time the learner opens the simulation in a new browser window The simple answer, you might say, is to mute the PC and not rely on the mute buttons. However, in the environment where I work, it is important not to mute the PC, as the user might forget to unmute it. Of course, if this isn't technically possible, then that is what they will have to do if they don't want to hear the audio. Why are we not using SL360 for capturing? I have further investigated how capturing works with the extra effort spent. I'm not happy with the downsides compared to using Captivate, as this is for simulation work. No single player bar for the whole simulation - individual bar plays for each captured image Extra triggers required for right-clicks, double-clicks - within the Try again layer Action Fine Tuning more fiddly to edit - even though both products place the click event after the click instead of before it actually happens The only way simulations would work natively (in-slide player) as opposed to SL360 captures also being launched as web objects, is to use the Modern Player as it would need to have controls for fullscreen, but Articulate still refuse to allow customers to customise the player. They force adherence to strict contrast rules, impacting the ability to use Brand colours which still have strong contrast but not enough to meet the rules.Solved27Views0likes3Commentscustom buttons in Storyline not working with ipad trackpad
Hi, has anyone come across similar issues? Storyline content using player frame for generic navigation (next/back), but has some custom buttons on screen for certain functions. When viewing on an ipad and using a trackpad on a detachable keyboard the buttons in the player work OK, but the custom buttons on screen aren't being recognised. Almost like the player takes the focus? They can be selected by tapping on the screen, just not the keyboard. Anyone found a solution or is it a bug? Thanks60Views0likes8CommentsIn Case You Missed It (ICYMI): Accessibility Updates in Q4 2024
Welcome to 2025! Since my last update, this accessibility group has grown by 61 members, bringing its total to 403 members. The first ICYMI edition was published on October 23, 2024, and established a foundation, but we can keep it short and sweet from now on. Product Updates: Rise 360 New: Immerse all learners in customizable interactive experiences with accessible scenario blocks that offer alternative text, screen reader support, and a visible focus indicator. New: Select the source course language when exporting your training for translation. Enhanced: Select the text of a hyperlink to apply formatting, including changing the color of the text. Enhanced: Line height and letter spacing are now available in the text formatting toolbar. Storyline 360 Enhanced: Expand your reach with a new AI text-to-speech model that supports Hungarian, Norwegian, and Vietnamese in addition to the 29 other languages already supported. Enhanced: You can now add text-to-speech narration and sound effects to markers. Fixed: Text alignment wasn't preserved in existing projects. Upcoming accessibility features: We've released Rise Accessible Drag-and-Drop Questions (Q1 2025, but released before posting this) and added Rise Math Equations. Current accessibility items on our feature roadmap include: Storyline Accessibility Checker Storyline Math Equations Rise Math Equations Updates in articles, documentation, resource center, or training: Refreshed: Storyline 360: Working with Hyperlinks New blog: What Is Section 508? A Quick Guide to Section 508 Compliance Upcoming webinar: Beginner's Guide to NVDA and Storyline for Accessibility Testing New entry in Storyline 360: Our Accessibility Journey - Accessibility Enhancements to Kick Off 2025145Views2likes2Comments