Forum Discussion
RISE - accessibility features
One year ago there was a discussion around accessibility - WCAG AA, WAI-ARIA Labels, Section 508, DDA, Equality Act and Screen Reader Supports.
It was noted that Articulate were working on this a...
Sharon or anyone else who has tested accessibility in Rise, do you happen to know if Storyline blocks that are built to standard maintain their usability when imported to Rise?
Hi Elizabeth - whilst Rise does not fully support screen readers, testing we've done with JAWS does (for the most part) work. Even if an authoring tool is classified as accessible, poor design can still result in a finished product that is not. For example, drag and drop activities. It is also important to remember that accessibility is for all disability types, not just for visual impairment. So Rise can work, you just need to really consider the design. The main issue in Rise is the lack of Heading styles (eg H1, H2 etc) which screen readers use for navigation purposes, and there are certain functions that screen readers tend to get stuck in (from memory, labelled diagram is one).
To answer your question in relation to Storyline blocks- the integrity of the block functionality has been maintained in all the testing we have done.
So adjustments to tab order and use of alt tags "sticks" in the Storyline block? That's the bulk of what I was thinking about.
They have for me Elizabeth. I needed to create a number of scenarios and used Storyline block with customised tab orders and that worked. I also created a few quiz blocks as the Rise knowledge check has a 'try again' button even if the learner has responded correctly. This is confusing for vision impaired learners. Again, all Storyline functionality worked within Rise.
