ElevenLabs integration roadmap for new V3 Tools?
Hello Heroes! I am using the AI Voice Generator withing Storyline to generate audio narration and sfx. The generator behind those voices and effects is 11Labs, arguably one of the best AI generators available today. 11Labs very recently (June 2026) released V3 of their engine offering significant improvements to voice design. https://elevenlabs.io/ I am curious if anyone has insight into when this updated 11Labs V3 driver might be integrated into Storyline? Do you remember when Storyline updated its AI generation to V2? Not as in introducing AI voices, but the update that came after that where they really got good and included more language bases. I felt like it was pretty fast after 11Labs updated, but not sure how to look it up specifically. I understand part of offering the new tools has to do with creating new user interface within Storyline to control the new features--so this may take a while. Do we have any insight into when additional VO tools common within 11Labs V2, such as voice cloning, might be made available withing the Storyline dashboard? Thanks so much!In Case You Missed It (ICYMI): Accessibility Updates in Q2 2026
Welcome to our Q2 2026 update! This quarter continued our focus on supporting the creation of accessible training and improving the learner experience. From new capabilities for identifying accessibility improvements to refinements for screen reader users, keyboard navigation, and color contrast, these updates reflect our ongoing commitment to accessibility across Rise and Storyline. Our community continues to grow. We now have 970 members, an increase of 54 this quarter. We’re glad you’re here. Let’s take a look at what’s new this quarter! Highlights This Quarter This quarter's accessibility updates centered around three themes: Identifying accessibility improvements earlier Storyline Labs introduces an experimental Color Contrast Check that helps identify color contrast issues across an entire project, while updates to Rise theme colors ensure contrast is calculated correctly across supported theme elements. Giving authors more control Storyline now lets you choose which objects are visible to screen readers, giving you greater control over how your training is presented to assistive technologies. Improving the learner experience Across Rise and Storyline, we refined screen reader support, keyboard navigation, focus management, and question interactions to provide a more predictable experience for learners using assistive technologies. Together, these updates continue our focus on supporting accessible training and improving the experience for everyone who creates and completes it. Product Updates Rise Enhanced: To improve accessibility, we've globally applied WCAG 2.1-compatible contrast to theme color elements that previously had contrast calculated incorrectly. Enhanced: Improved screen reader focus behavior so that, after answering a knowledge check, focus moves directly to the next relevant content. Enhanced: Improved tooltip behavior so that only meaningful tooltips are displayed for interactive elements like the block selector and sorting activity. Enhanced: Preview now opens the entire course, with full navigation. Enhanced: The video player is now consistent across the app and provides a refined experience with better responsiveness on mobile devices. Storyline New: Easily control which objects should be visible to screen readers with a new accessibility toggle in the timeline. New: Storyline Labs is here! Access experimental features early from the Labs button in the File or View tab. Available in Labs: Color Contrast Check helps identify color contrast issues across an entire project using the accessibility checker. Fixed: Screen readers announced extra text when certain question types were used. Fixed: A trigger designed to fire with a user click incorrectly executed when using a screen reader. Fixed: Text-entry fields didn't follow the defined custom focus order during preview. Fixed: Windows Narrator read bulleted and numbered list items twice. Fixed: Screen readers didn't correctly announce nested list items in the Notes panel. Fixed: The accessibility checker incorrectly reported issues on screen recording slides where all objects were hidden from accessibility tools. Fixed: The focus order was incorrect for screen readers when the Transcripts tab was opened. Fixed: Drop-down question choices didn't display a scrollbar when the list couldn't fit all choices. Other Updates Updated Articles Storyline 360: Working with Buttons Rise 360: How to Use Process Blocks Rise 360: Our Accessibility Journey Storyline 360: Our Accessibility Journey Storyline 360: Working with Variables Storyline 360: Working with Triggers Storyline 360: Pick-One Questions Accessibility IndexAnchor points and Dragon voice commands
Simple version: Can I change an object's anchor point? Long version: I'm creating linear guided systems simulations for a client. They are fond of the interactive nature of getting to practice in a safe environment. Accessibility are also important to both myself and the client. We're able to include their JAWS screen reader users, but they also have Dragon voice command users. Dragon and JAWS are very different tools with different use cases. Generally speaking, their JAWS users have vision-based challenges. They can interact with the content, but they can't perceive it. Dragon users typically have motor-based challenges that prevents them from using a mouse and / or keyboard. They can perceive the content, but they can't interact with it. Dragon uses voice commands like "Click button." We're seeing an issue where when we say, for example, "Click contact details." the mouse cursor moves to the bottom left-hand corner of the button. This means it sometimes clicks it, but is sometimes a pixel or three away from the button and so clicks... blank space near the button. Working with the client's accessibility expert, and noticing the consistency in the behaviour, we wonder if the cursor goes to the bottom-left of the button because the anchor point is there. If so, changing the anchor point to the centre of the object could resolve the issue. Unfortunately, the official line is, "Articulate does not support Dragon." (or any voice command software as far as I can tell) and the only thing I can find regarding changing anchor positions is a staff member response on these forums from 9 years ago confirming you can't change an object's anchor position, but suggesting the user submits it as a feature request. There is a workaround of placing a transparent shape over the button and then grouping them together to manipulate anchor points, but that plays havoc with the very accessibility tools and assistive technology we're trying to support in the first place. So yeah, is there something I'm missing here, or is it still impossible to change an object's anchor point?Custom block font size not matching
Has anyone else noticed that the size of the font in a custom block looks completely different than a regular text block? My statement block and my custom block are both Karla size 18 bold but the custom block is noticeably smaller. This make course consistency impossible.Need efficient way to advance through slide timeline with keyboard or screen reader
When using the keyboard and screen reader to go through a Storyline course, there is no easy way to advance in chunks through a slide's seekbar. I can press the right arrow or left arrow (or PageUp or PageDown keys, which do the same thing) but it only advances or rewinds by about 1 second. So if I want to move to minute 1:00, I'd have to hit the key about 50 times in a row. This is a terrible user experience for any keyboard user trying to skim through a slide. The Home and End keys take you to the very start or end of the slide, but if the slide is of any appreciable length, it its an ordeal to try to jump to somewhere in the middle of the timeline. Would want the PageUp or PageDown keys to advance at least 10 sec, and/or perhaps give different sized jumps for holding down CTRL or SHIFT when pressing the right/left arrow keys or PageUp/PageDown keys.Rise Default Text Colour Pallet - Gone
Hi, I would like to ask the Articulate team, what happened to the default text colour pallet in Rise. There used to be a grid of colours for text colour changes, now we must input the hex code if the colour we need is not one of the two theme colours. Our organisation uses #313537 for 95% of text. Now instead of clicking this colour which was previously in the default colour grid pallet, we now need to type in the hex code for every text block which is frustrating and increases our workflow (see screenshot below). Unless there is another way of setting a greater array of theme colours (e.g. 5 or 6 colours) then this is another step backward Articulate. Thanks, Tony Thomasaudio transcript hides exit button
Hi, when I add an audio file with a transcript to a RISE course, the audio transcript (on the right-hand side of the browser window) obscures both the button to skip to the next/previous lesson and /or the ‘Exit’ button, if it is active. I am using the ‘APEX’ theme. Is there a solution to this? Many thanks and best regards, MartinPicture States and Visibility to Accessibility Tools
Hello! I recently build some interactions in a project using the "Insert pictures as states" feature (https://www.articulatesupport.com/article/Storyline-360-Adding-and-Editing-States ) based on this tutorial Flipbook Animation in Storyline | Sync PNG Frames to a Slider or Dial where the user could then animate the states. It's a neat way to get some animation into storyline as well. The trouble I have is the "Object is visible to accessibility tools" is checked on for all of these pictures within the states. Right now it's like 30 images; 1 per state, 30 states, all on one main picture 'object'. I do not want to have to go to each state to uncheck each image if I can help it. I tried using the accessibility checker, as it lists all the images in all the states as missing alt text, and allows you to uncheck them from there, but there is some strange behaviour. When you uncheck just one of these, they ALL disappear from the accessibility checker, and are ALL disabled to accessibility. However, this also disables the main object on the timeline. When I then try to enable the main object on the timeline again, so there is at least something visible by a screen reader, ALL of the pictures get turned back on. So it's an all or nothing situation. Any chance I'm missing something here, and there is some other way to disable all these images for screen readers, but still leaving the main timeline object enabled?I can't increase the width of drop down interaction bars?
With no text wrap and "Resize shape to fit text" selected, the drop downs look like: The other options (wrap text or shrink text on overflow) look really bad: All size adjustments are disabled: How can I increase the width of the drop down bars so that the text fits without shrinking? The shrunk text is too small to read and is not ADA compliant.Score is reported to the LMS before the final Result Slide
I'm working on a Storyline 360 course with three separate module assessments. Each module uses a question bank and presents a set of random questions. After each module, I only want to display a Pass/Fail message without sending the score to the LMS. The learner's overall score should be calculated and reported only after all three modules are completed and they reach the final Result Slide. To do this, I removed the Submit Results trigger from the three module Result Slides and kept it only on the final Result Slide. However, when I test the course in SCORM Cloud, the learner's score is still being sent to the LMS after completing the second module, even though they haven't reached the final Result Slide. Is this expected behavior in Storyline 360? If so, is there a supported way to prevent the score from being sent to the LMS until the learner reaches the final Result Slide?
