Microleaning navigation menu
The numberred stepped navigation menu in microlearning tools does not appear in tablet and mobile viewing options, only in the destop option. The instructional and educational design of our microlearning tools depend on this menu in order to quickly locate specific content and navigate our tool freely. How can the menu be activated at least for the tablet view? Thank you for all help in this matter!Rise flip card issue and screen reader
According to our auditors for accessibility, NVDA/Jaws is reading the flip cards "click to flip" first and then content on the cards second. We were told that this reading order has changed and it use to read the content first and the instructions second. Was there an update to Rise that made this change?How to Remove Only Certain Playback Speed Options (e.g., 1.75x and 2x) from the Storyline Player?
Hi everyone, I'm working on a Storyline project and would like to customize the playback speed options in the built-in player. Specifically, I want to remove only the 1.75x and 2x speed options, while keeping the slower speeds (1x, 1.25x, 1.5x) available for learners. I’ve tried using JavaScript triggers to manipulate the speed control but had no luck. I also looked through the published output (frame.js, etc.), but couldn’t locate any editable section where the speed options are defined. Has anyone managed to: Customize or limit the available playback speed options? Successfully edit the published output to remove specific speeds? Use any alternative method to achieve this? Any guidance, workarounds, or examples would be much appreciated!Control over paragraph spacing
Hello, Where I live we are legally required to meet WCAG standards which require a space of 2x the font size between paragraphs. In order to implement that I need control over spacing between paragraphs. This can't be done by adding empty <p> elements, which is poor practice. It should be done with margin and/or padding. I would also like control over space before/after headings for the same reasons. This functionality is provided in all comparable platforms and word processors. Even the text frame which I am typing into now does so. But not in Articulate Rise 360. Please allow the end user access to the stylesheet for text elements.Making Sliders more accessible
I have a slider with three steps. Basically the user has one of two options. They are presented a scenario and they choose between "Starting a new case" or "Amending the existing case" When using JAWS and arrow keys, the screen reader says zero, one and two as you move right and left. (it starts in the middle). I would like the screen reader to say Starting a new case for the zero/left option or amending the existing case for the 2 or right option, and say nothing when in the middle. Accessibility on the slider is simply the slider itself. Is there anywhere I can set different text for the slider stops?Customise style of drop down graded question
Hi I'm building a quiz in storyline and I'm trying to avoid using drag and drop questions, for accessibility reasons. And I want to replace them with the drop down question style. However, the rounded edge box and white background of the options is starkly different from the rest of the quiz look and feel. I cannot seem to edit the format of the boxes. Am I missing something?Accessibility Checker Early Access Sign-up
Hello everyone, If you've noticed this on the roadmap or seen the demo at DevLearn last November, you know we're building a new Accessibility Checker feature for Storyline 360. The Accessibility Checker will surface potential a11y issues that could prevent some learners from getting the most out of your course. Even better, it will explain why the issue is important to fix, how you can fix it, and, in some cases, it will even fix it for you with a single click! We've been working hard on this feature for the past several months and are nearly ready to let a small group of customers try it out and provide feedback via our Early Access program. Participants in the Early Access program will be able to use the feature via the Storyline private beta and communicate directly with the engineering team to ask questions and provide feedback that will help shape the final version of the feature. If you're interested in participating in the Early Access program, please fill out this interest form: https://lnkd.in/eFAPU3KD NOTE: Not all customers currently in the private beta program will be able to use the Accessibility Checker while it's in Early Access. Once Early Access concludes, the feature will be available to all private beta users for a period of time before being released to everyone. Thanks, RonnieIncreasing the size of the Storyline 360 Editing interface
Hello, I recently had a concussion and I am trying to work on projects in Storyline 360. I can increase the Slide size but I cannot seem to increase the size of the menu ribbon (i.e. Insert, Slides, Transitions) trigger buttons or timeline text. I have increased the screen scaling on my computer - websites have larger text and icons, but Storyline does not. This is making it very hard to work and is not accessible, which Storyline theoretically cares about! Please guide me in how to make the program access for myself in order to create e-learning.Aria-hidden
Since the last update a new warning shows in the console. Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden. Allthough it doesnot prevent anything from working i always get wary from these kind of messages as they often a warning for something changing in the near future. So please Articulate devs... do check if and where aria-hidden is used and if that might give issues in the near future.
