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...
I just got my testing results back and I'm happy to share them with the community.
My approach:
I created a course and basically inserted one of every type of block there is in Rise. I applied as many accessibility considerations as I could in terms of contrast, alt text on images etc.
I shared the course with a colleague who is blind and uses JAWS screen reading technology, and here's what we discovered:
What to avoid:
- image galleries and carousels
- fill in the blank questions
- continue divider - the block seem to add a lot of 'noisy' script
- labelled diagrams - tab order just keeps looping between labels
- quiz block - hard to navigate, each question is announced twice (use knowledge check instead)
- quiz maker inserted as storyline block - 'noisy' script that could not be navigated
- step order process interaction
- timeline interaction - headings 'style' is a problem
- flashcard interaction
- any drag and drop - eg card sort interaction and question type
- multiple response questions
What worked well:
- buttons with links (but they 'appear' below in a screen reader announcement, not right as visually displayed)
- accordion - however, headings are problematic as often not in sequence
- single response radio button questions (but this is very limiting for non-vision impaired learners)
- Text, statement, quote, list functions
- file downloader
- two column text function
- image function - using alt text (alt text space not limited which is good)
- embedded video (provided video has closed captions)
Hopefully, this helps those of you who are keen to use Rise but still need to provide accessible eLearning.
I'd welcome the chance to continue a best practice dialogue in this space and look forward to hearing about the approach that you are taking.
From all of the above, if I could have just one wish:
- The ability to apply a CSS style for headings would be an amazing win. Many of the blocks have hard-coded heading styles that aren't editable as part of the design process, which causes many tab order and sequence problems.
Hi Sharon, a huge thank you for sharing your results. I too am about to complete an accessibility exploration of Rise blocks, so your findings are very helpful.
