Focus order: keyboard navigation and screen reader
Hello all, I’m a very infrequent Storyline user, dusting off Articulate Storyline 3 for the first time in about four years. Apologies if this is a newbie question. I’m about to embark on a month of full-on authoring, so I really appreciate any guidance from the Articulate brains trust😊 My goal is to meet WCAG2 accessibility requirements (or get as close as possible). Keyboard Navigation: With a keyboard, I can tab through all the interactive elements in the handful of slides I’ve put together (see the example in my screenshot). I vaguely recall from years ago, perhaps incorrectly, that I could tab through text boxes. I’ve found a workaround by adding a trigger (that doesn’t really do anything) and making the text boxes interactive. Should I be able to tab through my text boxes? Do others keep their text boxes tabbable? JAWS Screen Reader: I’ve downloaded JAWS, and it reads the interactive objects correctly when I tab through. However, it doesn’t pick up text boxes in the Focus Order unless I click on the text on the screen AND have replicated the text in the Alternative Text row. Is this expected behaviour? How would you normally handle this? Should I stick to my keyboard navigation workaround and add the alternative text? Any insights or advice would be greatly appreciated. Thanks, Benflip Card accessibility is not working with the assertive tool JAWS screen reader
Dear Articulate, We have used flip card blocks "Flashcard Grid " into our e-learning with 10 number cards in a block. When we test these in the output with the JAWS screen reader, the screen reader does not guide the learner how to move the next flip card and is also unable to tell which flip card he has to go through in the content for this block. The screen reader automatically for all 10 flip cards with out stop. This is very confusing for the learner when to flip to next card. Could you guide us how to fix this issue or Articulate will release a new update with fixing tis accessibility issue for flip card block. An early solution is highly appreciated. Best regards, SibaAccessing video controls using a keyboard
I'm trying to test a course using NVDA and the keyboard only. My course has video slides, with the new "accessible" player controls enabled. However, I can't figure out how to access those controls using only the keyboard (no mouse clicks). It's great that there's a button with the transcript automatically generated from the CC, but I can't seem to navigate to any of those buttons using the keyboard. Help!Translation / localization
Hi, We currently have our course in English only, but more and more we get requests to translate the content. The content is mostly text and speech (generated with the text to speech feature). I know about the feature on how to export, translate and import again, but now with AI and LLM and translation tools like DeepL is there a smarter and easier way to do it than duplicating slides and courses in different languages? Anyone with ideas, experience or suggestions? I am happy to hear what you think.Focus Order & Feedback Layers
I do a lot of accessibility testing with NVDA on my courses, and there is one major inconsistency that I cannot figure out. What determines if a feedback layer will read before or after I press the submit button? So when you author a question but don't mess with the focus order, the "try again", "incorrect", and "correct" feedback layer items are at the top of the focus order. When you publish the content and read the slide with a screen reader, the action following the submit action is inconsistent. Sometimes the focus jumps to the feedback layer, but sometimes the focus wants to continue down the feedback layer, and you have to up-arrow to get to the feedback layer. I know there are a lot of variables at play. You could create a button on the screen that triggers a submit action, or you could use the submit button. You could apply a layout, or you could build an interactivity from scratch. You could use the feedback master layouts, or you could build custom feedback masters... I have done all sorts of these, but I repeatedly return to having to test each individual question and tweaking the focus order with no blanket best practice. For a long time, I was seeing that questions without a score needed their feedback layer content at the bottom of the focus order, but questions with a score needed their feedback layer content at the top of the focus order; but that general rule is now out the window. Have you seen a pattern?Adjusting Pronunciation in AI Text-to-Speech Functionality
Hi everyone, Our team is currently evaluating the trial version of the AI text-to-speech functionality, and we’re impressed with its capabilities! However, we’re looking for a way to adjust how the voices and characters pronounce certain words, aside from modifying the stability, similarity, and style exaggeration settings. Does anyone know if there are additional options or settings available for customizing pronunciations? Any insights or tips would be greatly appreciated! Thank you!
