accessibility
517 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.Solved82Views0likes9CommentsExporting all captions
I have created a Storyline360 file, and each slide has its own audio and closed captioning created within Articulate. I can export the closed captions for individuals slides but can I export all captions for the whole file? Also when I publish to video the captions don't appear to come with it, and I then need to attach a caption file? I am VERY new to this, and hope some can help.1.3KViews4likes67CommentsCaptions button not showing
I have been unable to get my captions button to show. I am using the AI voice insert with "Generate closed captions" checked. I've also got my captions button check marked in the settings, but when I preview AND publish it still is not there. I've already reset the player, didn't help, and made sure I had captions under "Manage Captions."15Views0likes1CommentStoryline 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?146Views0likes5CommentsProblem with Set Focus trigger
I have a Storyline slide that has 4 tabs on the base layer and 4 layers: each tab when selected displays a unique layer. Each tab selection also has a Set Focus trigger to a text box within that layer. The intent is for those using a screen reader, they select the tab, the text box is read. Issue: When selecting a tab, a yellow line flashes at the edges of the slide (for both screen reader and non-screen reader users). Occasionally, a rogue highlight appears in various locations (see screen capture). The flashing and the rogue highlight seem to disappear when the layer's text box is removed from the focus order: but then the screen reader never reads the text box, even though it receives the focus. Any ideas?29Views0likes2CommentsStoryline + OneDrive: How to Stop Temp File Sync Issues?
I frequently run into issues where OneDrive automatically backs up all temporary files created by Storyline. When Storyline closes, these files are deleted, which results in unnecessary sync activity and bandwidth usage without any real benefit. To improve workflow and system performance, I’d like to suggest the following enhancements: Set a default folder for “Save As” It would be helpful to have the ability to define a default folder that opens when using “Save As” in Storyline. For example: C:\Temp\ArticulateProjects\ This would allow users to work in a local folder outside of OneDrive (which is often required by IT policies). Set a custom folder for temporary files Storyline should allow users to specify where temporary files are stored. For example: C:\Temp\ArticulateTemp\ This would prevent OneDrive from syncing and deleting these files, improving stability and reducing unnecessary network traffic. Separate folder for Storyline templates It would be ideal if templates could be stored in a dedicated folder, such as within OneDrive: C:\Users\<username>\OneDrive\ArticulateTemplates\ This ensures templates are backed up and easily recoverable in case of a system crash. It also supports better reuse of custom features across projects. These features would significantly improve the user experience, especially in environments where OneDrive sync is enforced. I’m curious if others have encountered similar issues or found effective workarounds?19Views0likes2CommentsExit course button not displaying on black background
Hi there, I've noticed a change in how Articulate Rise publishes courses over the last little while. Previously, when I published a Rise course, the "Exit course" link/button in the top right would display on dark backgrounds with a white shade behind it to ensure it was always visible. This no longer seems to occur. See the attached screenshots. Does anyone have any ideas on how to resolve this issue?WCAG Reflow criterion (1.4.10)
Accessibility is important to us. We want to comply with the WCAG accessibility guidelines (AA 2.2.) as far as possible. With regard to the reflow criterion (1.4.10), you refer to an exception in the WCAG guidelines that relates to presentations, among other things. Two-dimensional scrolling is currently necessary when using the zoom. We would like to know: Are there already efforts to adapt with regard to the reflow criterion? 2. Are adjustments planned in the near future? FYI: We do not work with responsive design.113Views0likes4Comments