Closed captions not appearing
Not sure what happened with the last update, but now closed captions are not appearing on my video. The project is a single slide, video dropped in and the srt file uploaded. when i look at the captions editor all the captions are there, when I preview the file, the first caption appears then nothing after that. This issue started today after the update, didn't have the issue earlier today when i did the exact same process. anyone else seeing this?Solved230Views6likes23CommentsBuild an Accessible Drag and Drop Interaction in Storyline
If you've ever needed to build an accessible course in Storyline, you may know that the built in drag and drop interactions are not accessible (see the VPAT). However, with some extra work it is possible to create your own drag and drop interaction in Storyline that is fully accessible. The issue with drag and drop interactions and accessibility is that people who access the computer using only a keyboard or assistive input device, and no mouse, cannot click-and-drag. So, the interaction must have another option, that works through the use of keyboard inputs (typically, the tab and enter keys). In Storyline triggers, anything that is done "on click" can be mimicked by a keyboard or other input device. To build a keyboard-accessible drag and drop requires building a second set of triggers that function using click-based rather than drag-based interactions. Here is how to build your own keyboard accessible drag and drop interaction in Storyline. Please note that you may include other elements that are not fully accessible. Take a look at theWCAG Guidelines to evaluate other aspects of your course creation This interaction relies on a user-selected submit button. This button needs to be on the slide, as the triggers used are not compatible with the built-in submit button in the Storyline player. Note: It will be easiest to create all layers, elements, and states before creating the triggers. LAYERS NEEDED Base Layer – Most of the triggers will be on the base layer. Correct – A feedback layer for when the user submits the interaction, when all items have been moved to the correct drop location. Incorrect – A feedback layer for when the user submits the interaction, when the interaction is incomplete or some items have been moved to the wrong location on the screen. BASE LAYER Elements Needed Drag items – one or more Drop targets – one or more Submit button – one Drag Item States Normal - The built in state. This does not need to be modified. Selected - Create a “Selected” state. Make sure to edit the selected state to include a visual indicator that the item is selected. An easy way to do this is to add a “glow” shape effect in a color contrasting the object. Drop Correct - Create the “Drop Correct” state. You may want to visually signal that the drop was completed. One way to do this is to darken or desaturate the object in the “drop correct” state. Drop Incorrect - Create the “Drop Incorrect” state. Make this state visually identical to the Drop Correct state. Triggers Submit Button 1. Show layer Correct when user clicks If Drag item 1 state equals Drop correct And Drag item 2 state equals Drop correct … (Continue through the rest of the drag items) 2. Show layer Incorrect when user clicks If Drag item 1 state does not equal Drop correct Or Drag item 2 state does not equal Drop correct … (Continue through the rest of the drag items) Drag Items For each drag item: 1. Change the item’s state to Drop Correct when it is dropped on the right drop target Change state of Drag Item 1 to Drop Correct when user drops Drag Item 1 on Drop Target 1 2. “Deselect” all other drag items when this drag item is selected (Change other drag items’ states to Normal, if they are currently selected) Change state of Drag Item 2 to Normal when user clicks Drag Item 1 If Drag Item 2 state is equal to Selected Change state of Drag Item 3 to Normal when user clicks Drag Item 1 If Drag Item 3 state is equal to Selected … (add this trigger for all other drag items on screen) 3. Change the item’s state to Drop Incorrect when it is dropped the wrong drop target(s) Change state of Drag Item 1 to Drop Incorrect when user drops Drag Item 1 on either Drop Target 2 or Drop Target 3 … (include all incorrect drop targets in the list) Drop Targets For each drop target: 1. Move the selected Drag Item along a motion path to the Drop Target when the user selects the drop target. NOTE: The move triggers MUST be before the state change triggers in the list Move Drag Item 1 on Motion Path* when the user clicks Drop Target 1 If Drag Item 1 state is equal to Selected * For the motion path, create a line motion path with start and end points in the center of the drop target. This will move the object to the correct location without showing movement on screen. Make sure to go into the path options and select “locked” for origin. This will ensure that no matter where on the slide the object starts from, it will move to the correct position with the trigger. Name the motion path something descriptive so you can identify it in the trigger list (ex: Drag 1 to Drop 1 Path). NOTE: When you create a motion path, Storyline automatically adds a trigger to the object to follow the motion path when the slide timeline starts. Make sure to go in and remove all of these triggers. … Make this trigger for all drag items on the slide. 2. Change the state of the corresponding Drag Item to Drop Correct, if the Drag Item is selected Change State of Drag Item 1 to Drop Correct when the user clicks Drop Item 1 if Drag Item 1 state is equal to Selected 3. Change state of the selected drag item to Drop Incorrect for all drag items that do not match with this drop target Change State of Drag Item 2 to Drop Incorrect when the user clicks Drop Item 1 if Drag Item 2 state is equal to Selected … Make this trigger for all remaining drag objects on the slide. CORRECT LAYER Elements Text box(es) Continue button Triggers Continue button Jump to next slide INCORRECT LAYER Elements Text box(es) Try Again button Triggers Try Again button Jump to slide (current slide) – this restarts the interaction on the slide base layer NOTE: Make sure the slide is set to “Reset to initial state” for the “when revisiting” selection in the slide properties. And there you have it! It looks like a lot, but once you've done it a time or two you can get the hang of it. Below is an example .story file of this interaction. It uses the same names as the instructions above so you can see how this all looks in a project.199Views0likes94CommentsArticulate Storyline + JAWS + Slide Title + "F"
Our 508 reviewers have indicated that a slide title which is set up in a master slide, is reading the title followed by "F". For example, "This is the slide title - F." This does not happen in every instance of a slide using this master. It does not happen on other slide masters. Has anyone experienced a similar issue and, if so, what is the fix? Thank you!198Views0likes3CommentsQuestion accessibility
Hello, I have a question regarding the accessibility of modules, specifically about handling questions. I'm working on the focus order, and I noticed that the focus order of a slide also includes the elements of the feedback layers (see screenshot, sorry it is in french^^ but you'll get it). Does this mean that a learner using a keyboard or screen reader will encounter the positive and negative feedbacks before even answering the question? How do you handle such cases? What are your recommendations? Thank you!97Views1like9CommentsClosed Captions Only Displaying on First Line of Video
I'm experiencing an issue with the closed captions on my Storyline 360 imported videos. The captions only appear on the first line of the video and then disappear for the rest of the playback. This is happening even when I manually type the captions or try importing .srt or .vtt caption files. I recently updated Storyline 360 on August 27th, and this issue started occurring after that update. Has anyone else experienced this problem? I've tried troubleshooting it but can't seem to find a solution. Any advice or insights would be greatly appreciated. I'm hoping this is just a temporary bug that will get resolved in a future update, but in the meantime, I'm struggling to get my videos properly captioned. Thank you in advance for your help!90Views2likes4CommentsRise 360 - Screen Reader testing - Accessibility
Hello, we recently developed a course in Rise 360 and had it tested by a screen reader user. They found a number of accessibility issues so we are sharing them here so that Articulate is aware. Text and Font Superscript (for references) is not read as superscript by the screen reader, which can be confusing. The user was also expecting link to follow each point immediately. Text block – information. Screen reader detects the "i" icon in information box but does not read anything, user advised it leaves them wondering what the screen reader detected. Storyline blocks For Storyline items inserted into Rise, sometimes the screen reader reads the storyline item file name. Text in Storyline slides seems to be read twice. There is some kind of marker the screen reader picks up on the slide before the text boxes which reads all the text on the slide, then the cursor moves to the text boxes on the slide and reads the text again. Knowledge Check questions Knowledge check feedback sometimes reads a period as "dot" even at the end of a sentence, and it isn’t clear why. Audio files duration is not read in a regular manner. Screen reader reads time of 1:04, as “one-oh-four” (not 1 minute, 4 seconds) and does not say "duration" or something similar. User was not clear what “one-oh-four” meant or was, and said it should read “duration 1 minute, 4 seconds”. Multiple response (select all) checkboxes read each checkbox choice twice. The user said they have encountered this many times before in other products, but it should not be read twice. Single response (multiple choice) radial buttons are read twice like checkbox items but the user advised they usually are not read twice in other products. It also re-reads the question after every option, which the user advised is not normal or desirable. Feedback of "Correct" or "Incorrect" is not formatted as a heading and could not be navigated to directly and easily by the user. Images Images are automatically formatted by Rise to include a Zoom feature and the screen reader reads info about the Zoom option after every image. The user advised this is not necessary. Navigation Bar Drop-downs in the navigation bar cause screen reader to say “same page” but it really means "same drop-down" in the navigation bar Accordions If accordions are used in conjunction with a Continue button to require completion, the accordions do not indicate which drop-downs have already been opened or not opened. Continue buttons If Continue buttons are the last thing on a page, selecting the Continue button takes you to the next page instead of a link that is from the navigation. (which is normal if the page does not end with a Continue button) The user advised the navigation bar type link should be the final item on every page for consistency and to avoid confusing the user.Solved67Views0likes7CommentsNVDA and Rise Video Player
Hello, anyone else have this issue: We have multiple videos in our course (using Multimedia/Video block. Not embed). When testing for accessibility using NVDA 2024.3, it reads the "Volume Level" button repeatedly. This is causing us to fail accessibility criteria. Has anyone experienced this issue as well? Does anyone have a solution? It is not the project since we have tested on a few and the behaviour is the same. Note: embed YouTube videos don't seem to have this issue. Thanks in advance for any input/ideas!54Views0likes8CommentsStudent Adjust Lesson Player
Hello, I am doing some research on authoring tools and LMSs for a college course and would like to know if the end user (learner) can modify the lesson player for an SL or Rise course. If so, to what extent are they able to adjust the player? Thanks in advance!! JenniferSolved48Views0likes4CommentsScreenreader reading incorrect question choice text - even after alt text has been changed
Hi, Whenever I create a quiz in a Storyline 360 course (or edit a quiz from a template course), I usually duplicate the question slides to speed up the question creation process so I don't have to reformat the slides every single time. However, when I test the course with a JAWS screenreader, it often reads the OLD question choices text even after I've changed/updated both the question choices AND the corresponding accessibility text for each choice. This means I have to go back and rebuild each individual question slide from scratch so that the screenreader will read the choices properly, since it will only read the "original" question choices text. If Articulate could address and correct this issue in the near future, it would save me entire days of re-work on future projects. Thank you.Solved41Views0likes6CommentsContent 360 Storyline Templates that Meet AA WCAG Accessibility Requirements?
Hi everyone, I'm a longtime Rise 360 user who is starting to dive into Storyline, and I'm finding it a bit more complex when it comes to accessibility. In Rise 360, many of the templates/sample courses meet WCAG requirements, and if they don’t, I can easily check which block types aren’t accessible via the online list Articulate provideshere. However, with Storyline, I can't seem to find similarly straightforward information. Does anyone have any recommendations for Articulate Storyline templates that meet, or mostly meet, AA WCAG standards? For example, I recently imported the slides from the "Illuminate" template, and while they look fantastic, I noticed some issues right away—like the very light grey font on a white background, which doesn’t meet contrast requirements. I'm really excited to get started with Storyline, but I’d love some advice on which templates might be better to use, especially those that are more accessible out of the box. Any suggestions or tips would be greatly appreciated!38Views0likes3Comments