Triggers for keyboard navigation- branching scenario
I'm trying to make this course (my first one!) accessible by keyboard navigation only. I've set the focus order so that users can press tab to move through the different options. I'm trying to figure out how to create a trigger so that when the user presses enter when they've selected their answer, it takes them to the appropriate slide. Right now, when I select jump to slide or show layer when user presses a keyit's adding a condition- after clicking on this slideor clicking on object. I don't want them having to click on any objects- that's the whole point of keyboard navigation, right? What should I do? I did create another state- the object when selected- and had thought to create triggers like jump to slide when user presses enter if object (envelope) is selected but that doesn't seem to be working either. Are there any workarounds for this? Or is there something I'm doing wrong? I can upload more attachments if needed. Thank you so much!23Views0likes1CommentClosed Captioning Tips and Proposed Improvements
I've found a way to quickly create captions for my Storyline files by importing my audio files to Microsoft Clipchamp and selecting the Captions (CC) option. Clipchamp quickly creates the .srt files making it very easy to import these files into the Storyline captions editor. I typically need to break up a couple of the captions, so the periods are at the end of the caption and not in the middle (personal preference) and quickly check the spelling of common homophones (e.g. die could be spelled dye, etc.). Does Articulate have any plans to add spellcheck to captions? My biggest issue with the Storyline captions is the editing screen. When I expand the window to fill my screen in the hopes of being able to see it better, the audio is the only component that gets bigger. I don't need to see the audio in this screen; I need to see the captions and the preview. I can barely see these on my screen because they are so small! Hopefully Articulate can increase the viewing size of these components in a future update!12Views0likes0CommentsHow Articulate Uses a Prioritization Framework to Drive Accessibility Maturity
Articulate is one of the world’s leading course creator platforms for workplace learning. In this special webinar, a trio of experts from Articulate will share their methods for streamlining their digital accessibility practice, improving their products, and making a major impact on customers. At the heart of their approach is their accessibility maturity model and prioritization framework. Join Simon Taghioff (Senior Product Manager), Leslie McKerchie (Accessibility Program Manager), and Robert Pearce (Senior Software Engineer II) to get an inside look at how Articulate’s accessibility team implemented a maturity model and prioritization framework to build a sustainable accessibility practice and drive growth. Join the webinar to learn how to: raise your organization’s digital accessibility maturity level develop a framework to prioritize issues and development resources measure the impact of a model on customer happiness and revenue and more! Register Here132Views0likes0CommentsNVDA 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!54Views0likes8CommentsClosed Caption Text Has Shadow
I used text-to-speech using the slide notes for a prototype in Storyline 360 (current update). All of the closed captions have this awful text shadow that I don't seem to be able to eliminate (see attached screenshot). I have gone to the player>colors & effects>closed captions and adjusted the font, text color, background color, font size, and position, but there is nowhere in there to adjust the text shadow. Does anyone have a suggestion for how to eliminate this without rebuilding the whole file? Thanks!23Views0likes8CommentsTable with row headings
I need to be able to create a table in either Storyline or Rise that has both column headings AND row headings, and I need it to be 508 accessible and properly read out both headings along with cell contents. As best I can tell, both products only support column headings. The recommendation is to use an image of a table and then describe it in alt text, which I know my 508 auditor will not accept. Has anyone found a solution to this?14Views1like2CommentsAccessibility Best Practices in eLearning
There are many ways that you can create an accessible eLearning course. Feel free to share any resources or knowledge that you have! I'll go first: Here are some resources from that describe what you can do to make sure that your content is accessible by people from all walks of life: All About Accessibility | Articulate - Community A Quick Reference Guide On eLearning Accessibility Standards (elearningindustry.com) eLearning Accessibility: Best Practices, Tips, And Tricks - eLearning Industry48Views2likes0CommentsScreenreader 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.Solved41Views0likes6CommentsRise 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.Solved64Views0likes7Comments