Forum Discussion
Rise Storyline Blocks & Screen Readers
Hi there, I saw this conversation still open so figured I could join here vs creating new. I have worked with Steven on an issue with lightboxes a while back and it ended up being a bug. But I still really struggle (not knowing how screen readers fully work) on when to use tab vs spacebar vs arrow up or arrow down within RISE to even get the course started and then move through the course particularly getting to a storyline block in and out of it. I am adding one of my review links for a module in RISE and was wondering is anyone willing to help me guide through it with NVDA, I feel like I have done everything I can with regard to focus order, alt text, tags for images (and left blank for decorative), captions, transcripts, but all the extra audio that the screen reader reads before the actual content in the course is so confusing for me. Wonder if Articulate would run a few sessions teaching folks how to use NVDA/JAWS commands to go through a RISE and Storyline course, I think many of us would watch. Anyway attaching a link to one of my RISE courses that I think is accessible in case someone is able to help me walk through it. https://360.articulate.com/review/content/f29bcc6a-def4-49ac-beab-3f319f08030e/review
Hi Teresa, found a little time to have a look at your review link. I didn't of course go through all the content, but what I've established so far is: 1. the images in RISE need 'alt text' to describe the illustrations. Sometimes illustrations/photos are there for decoration, however they should have a short description so the user knows the purpose of the asset when the SR is navigating over the page. 2. I also found inside storyline blocks, the words were not being read. Its also best not to use layers, unless its via a 'dialogue box' the reader recognises dialogue boxes and not layers. And of course all images need 'alt text'. I also found through experience that when adding 'alt text' to storyline; to not over describe the images - use short concise language. Ensure the focus order navigates the screen consistent with a screen reader (left-right, top-bottom) I think that's correct. Wherever possible place items in a table because the semantics for how a table is constructed is easier for the screen reader to describe. If using a table, all text must be repeated in the focus order settings for 'alt text'. When designing for screen readers, the best approach is to 'keep it simple'. Learning about how a screen reader navigates a page meant that I had to really think about if the creative methods I wanted to use were needed. By designing for SRs it does reduce your design choices but it does make the content more accessible across cohorts. RISE has all the information you need via their site. It may be a good idea to start here if you haven't already read through their information: https://www.articulatesupport.com/article/Rise-360-How-to-Design-an-Accessible-Course. Good luck Teresa...