Rise inconsistent font sizes
Something that has always irked me when accessibility testing Rise courses is the font sizes in the knowledge check questions. I think there are other blocks that also feature different font sizes, but in this example, it is a multiple choice knowledge check question. Above my multiple choice question I have a regular Text block (paragraph): 17px Multiple choice question (Question text): 16px Multiple choice question (Question options): 15px Multiple choice question (Question feedback): 14px I find this a bit unusual in terms of accessibility and am not sure what the rationale is behind the different font-sizes in some blocks (appears to be hierarchy?), but I always think of users who may be optimising text zoom based on the body text being 17px, and then come to a MCQ where the font sizes get smaller and smaller. Any chance of this being considered for change in future so that font sizes are more uniform? I tend to adjust these manually when building, but would much rather they came out of the box uniform. Thanks, Sam.AI Text to speech not updating closed captions
When I create a new AI text-to-speech file it adds captions just fine. * But when I go to update that file on the timeline, even with the "generate CC" box checked, it still has the old captions. If I delete the existing captions, re-generate the audio with the box checked, and save, no new captions appear. What can be done about this? * Also, the AI generation doesn't honor SSML very well. I can't correct its pronunciation of certain words without writing the prompt phonetically, then manually changing the CC every time I update the script.Screen readers not working correctly on Rise quizzes
Has anyone had issues with this? We have found that the Microsoft screen reader reads out the incorrect answers that have NOT been selected when doing quizzes. The screen reader will say "Your answer...[insert incorrect answer here]" when it has just said aloud the correct answer you have just selected. See recording here: Devices on the go | Rise 360 - Awesome Screenshot Is this something someone can help with? Is there a screen reader that's better equipped to understand Rise quizzes that we should be using instead? Many thanks,Activating subtitles / Closed Captions by default
Hello, I want to display subtitles by default on a video in Rise360. So I Edit the video and upload a vtt file. Then on the video the user can click the CC button to display the subtitles I choose. Is there a way where the learner doesn't need to activate the subtitles, and that it can already be on a defined langage (or the only one in my case), instead of the default: "Caption off"? Thank youCustom 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.Storyline Text-to-Speech loses neural voice when using hyphens to separate letters
I work for an organisation that has an initialisation in its name and we often create courses with text-to-speech. We use a neural voice (English UK: Amy). The initialisation is also a natural word so I have to specify to TTS to spell it out. A while back I noticed that separating the letters with spaces created too great a pause between each letter, so I started separating them with hyphens, which sounded more natural (e.g. 'D-O-G' rather than 'D O G'). More recently however, any time I try this, the neural voice is replaced by the standard voice. I understand that using SSML tags (<say-as interpret-as="characters">) will cause the neural voice to drop too, so I wonder if hyphens are interpreted as a shortcut to this somehow? But I still have older projects where I use hyphens and this doesn't happen, so I wonder if it's a Storyline issue. Example: Neural voice dropping | Review 360 Example of it working fine in an older project (press the speaker symbol to activate): Neural voice not dropping example Story file attached. Storyline version is 3.99.34516.0Closed Caption issues with AI Text to Speech
Hi all I am loving the new AI Text to Speech voices but have found an issue with the Closed Captions. The Closed Caption placeholders are not lining up or splitting where expected. Image 1 is how the closed captions are displaying for the voice to text. Image 2 or 3 are both examples of how I would expect the captions to display, with the placeholders aligned to speech. Either of these would be acceptable. Is anyone else experiencing this? Not sure if this is a bug or an enhancement request or if I'm missing something? Thanks all! Niki StoylesStoryline 360 – Random Focus Highlight Appearing on Interactive Elements During Mouse Navigation
Hi Articulate Community, We are working on an accessibility-compliant Storyline 360 course and are facing an issue with the visual accessibility focus indicator. We have enabled a visible accessibility focus color in Storyline because keyboard-only users need to be able to identify which interactive element currently has focus. Expected behavior When a learner navigates using the Tab key, the currently focused interactive element should have a clearly visible focus indicator. The focus indicator should move as the learner moves through the interactive elements using Tab / Shift+Tab. During mouse-only navigation, we would not expect the focus indicator to appear or remain unexpectedly around interactive elements. Current behavior When testing the published course, we are seeing the following: During normal mouse navigation, a yellow/amber outline or highlight sometimes appears around an interactive element. The highlighted element is not always the element we expect to have focus. The highlight appears only on some interactive elements and seems to occur inconsistently. It can remain visible after a mouse click. When we navigate using the Tab key, the focus indicator works as expected and provides a clear visual indication of the current keyboard focus. This creates a visual issue because the focus indicator was intentionally added to support keyboard accessibility, but during normal mouse interaction it can appear unexpectedly and make the interface look as though an element is still selected or focused. The concern is not that the accessibility focus indicator exists. We understand that a visible focus indicator is required for keyboard accessibility, and we want to retain it. Our question is specifically about the unexpected appearance of the focus indicator during mouse interaction. Could anyone confirm whether this is expected behavior in Storyline 360? Is there a supported Storyline setting that allows the focus indicator to remain visible for keyboard navigation using Tab, while preventing it from appearing or remaining visible unexpectedly during normal mouse navigation? Could browser focus behavior cause the Storyline accessibility focus indicator to appear after a mouse click? Are there any known issues in recent Storyline 360 builds involving unexpected or inconsistent focus indicators? We would particularly appreciate guidance from Articulate on whether this is expected browser/Storyline focus behavior, a known Storyline issue, or something that can be controlled through Storyline settings. Thanks in advance!Changing Storyline Modes
Hi, Is there a way for a user of a course to change between light, dark and custom modes within Storyline? On researching this, I know that the traditional solution is to create different versions within one course, but can this now be done by changing a setting within the player to give the user the choice at that level? Thank you in advance.
