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 and that there would be further developments in this regard. Have the accessibility issues been addressed. This is important for me as I am about to develop a course and would like to use RISE rather than Storyline. Thank you

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.

Is there a consolidated VPAT or other documentation that discusses the degree to which RISE is accessible in it's current iteration? Trying to find this answer across multiple threads and product release notes is difficult, at best.

Hello everyone! I’m happy to share our Rise 360 Accessibility Collection, which includes the VPAT to describe how Rise 360 conforms to WCAG 2.1 Level AA criteria.We also updated our roadmap to include Rise 360 features we’re continuing to develop to better support WCAG.Let me know your questions and experiences building accessible courses for all!

Back in December I was so happy to see that there had finally seemed to be a lot of progress made in making Rise accessible and up to WCAG standards. Even though it seemed to only be partially there, I had a lot of hope in that it wouldn't be long before the outstanding components were addressed (based on the messaging I had saw)... It's now almost July and the last updated date on any of the Rise Accessibility docs remain as December 2020. I took a look at the roadmap link that was shared and was super disappointed to see that all Rise-related accessibility items that are outstanding are just listed as "planned", not even "in development"! These aren't just nice to have features, these are crucial features to ensuring proper access to Rise courses. I had thought Accessibility was a priority, but that seems to no longer be the case. Is there really nothing else currently in development for Rise other than quiz question banks?! Sure doesn't seem to be a whole lot to look forward to for the future of this product...

Hi Beth - I'm in the process of doing some extensive testing in this space using JAWS screen reader. I've created a sample course that basically includes all of the available RISE functionality and we're testing to see which functions are problematic. I know that, for example, the multi-response questions are not but the multiple choice are. Happy to share the results once I get them - hopefully, next week.

RISE - accessibility features | Articulate

CoryVanBelois-4
Community Member
4 years ago
Thank you Alyssa!
SibaPrasadPadhi
Community Member
4 years ago
Hello Articulate,

These are 5 years and taking more time to implement the accessibly feature to this product. as the primary design requirements for a eLearning product are accessibility and supporting customization on branding, we are still waiting for these 5 years except some small functionality improvement. One of such request is black theme for Rise, bullet points customization, Symbol library, block content alignment both text and image are still pending. Can these be implemented from Articulate?
BethCase-c92276
Community Member
4 years ago
Developers should not have to pick and choose less interactive or engaging elements to make sure it's accessible. Every feature should be accessible See Softchalk for an example of a content creation tool that has done an outstanding job of redesigning interactions to make them accessible and removing those that could not be made so. And they did it all within a couple of years.

It's great to see so many accessibility features "in development", but without a projected date, it's meaningless. It's like people being engaged but not setting a date for years.

I also see "autoplay" as one of your proposed features. This actually HURTS accessibility. (https://www.boia.org/blog/why-autoplay-is-an-accessibility-no-no)
JoKaptijn-d4ba7
Community Member
3 years ago
Hello! Great to see more accessibility features for Rise 360 are in development etc...

As I'm about to design a new course to meet accessibility standards, would be great to have an overview of the Rise blocks vs accessibility conformance etc. I have looked through the Accessibility Collection, and other than the features mentioned 'in development' - cannot see an overview. Just wondered if this does exist as I know people have requested earlier in this thread?

Thanks in advance!
- hazelB
  Staff
  3 years ago
  Hi Jo! These two links can help!
  
  https://articulate.com/support/article/Rise-360-Accessibility-Conformance-Report-VPAT?#section-508-report
  
  https://articulate.com/support/article/Rise-360-Our-Accessibility-Journey
NadineLacelle-1
Community Member
3 years ago
Are these interactions in Rise WCAG 2.1 AA compliant?

Carousels

Scenario Blocks

Flashcards
- KarlMuller
  Community Member
  3 years ago
  Hi Nadine,
  
  The accessibility status of those interactions are stated here: https://articulate.com/support/article/Articulate-360-Feature-Roadmap#rise-360
  - NadineLacelle-1
    Community Member
    3 years ago
    Thank you Karl. Do we have an idea of timeline?
- SuzianaAhmedShu
  Community Member
  3 years ago
  I ran first accessibility test and found the 3 features have 'barriers'.