Forum Discussion
Tips for Making a 508 Compliant Course
I concur with Pierre about e., Kristin. Granted, Articulate has come out with changes for accessibility in the past two years.
These days, in my experience with NVDA and Storyline courses, the Tab key is only for navigating interactive elements, such as buttons, tabs, links, and so on (browse mode). Once virtual (not visible) focus lands on the slide (e.g., via the "skip navigation" button), NVDA announces the title of the slide, and then you can use the various arrow key combinations, such as Insert + Down Arrow in NVDA, to read all of the contents on the slide that are included in reading order (reading mode). As I understand it, this is expected behavior for keyboard navigation with NVDA. Not sure how this works with JAWS, but if Articulate has programmed the output correctly, it should work in a manner that JAWS users would expect.
One way to find out how a given screen reader is really supposed to interact with a web-based deliverable is to go to a website you already know is accessible, such as WebAIM or https://www.w3.org/WAI/ and attempt to navigate it using your keyboard and screen reader.
Hope this helps someone!
Hi Lisa and Pierre, thank you for the feedback. This article was written about two years ago, and at that time you couldn't use the arrow keys to navigate a course while using JAWS. That has since changed, and I should probably update the article to reflect all of the wonderful updates that have happened in Storyline over the last two years. I may also request that these posts have dates attached. I can't tell you how many times I've searched the forums to find an "answer" only to realize the post is from seven years ago. C'est la vie.
