Rise Storyline Blocks & Screen Readers

Hi Teresa, I have recently finished a major project for the organisation that focusses on users with disability.  I too was very unaware of what to do when designing in RISE and Storyline. Its been a massive learning curve for me.  We also engaged with a group that offered a fee for service where we connected with a person who used only a screen reader to navigate. The funded project last for about 2 years from engaging with focus groups - development - design - and testing. We had regular meetings where the package was tested by this person. It was a 'train wreck' to start with, but then as I did much PD about the skill I slowly learnt how to re-design RISE and Storyline. It was like 'xmas' to me when the person navigated all the course using a JAWS screen reader without issues, but it took a lot of development to get it to that stage -- that was a great day for me professionally.  Anyway I'd be happy to pop into the review link for you.  I have NVDA loaded on a USB stick, so my PC doesn't need to be impacted by a screen reader. Having a screen reader actively read the screen is definitely 'trip'. I'll get back to you soon later today.  I need to get some work done this morning then happy to give it a test drive with the NVDA reader.  Check back later.  Take Care.

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...

Hi Teresa, I also meant to add into my last post that if you can afford it, its worth engaging with an organisation that will have people who will navigate the course with a screen reader and provide feedback. It was the only way I could accurately learn from my mistakes and eventually have a course that was up to WCAG standard at least as much as RISE have developed their tool sets for.  Happy to discuss further.  Take Care