Accessibility in Rise
Dec 01, 2016
Hi,
As mentioned on the website under FAQ for Rise "Are Rise courses compliant with accessibility guidelines?
Rise employs many modern web standards for accessibility, and additional accessibility improvements are in development."
Could you please specify in detail which of these are supported in current version:
WCAG AA, WAI-ARIA Labels, Section 508, DDA, Equality Act and Screen Reader Supports.
Thanks
Mayuresh
342 Replies
Hi I agree with everyone about the workarounds we have to do in storyline to make it accessible - will welcome more updates about accessibility in Rise
I'll mention that I'm participating in a Storyline group dedicated to testing a new accessible player. So far, they've addressed a lot of the issues I've shared. It sounds like they're first addressing accessibility issues with the player and then they're going to address issues on the "stage" (inside the player). Like others, I'm cautiously optimistic. Wouldn't it be great if both Rise and Storyline were fully accessible?
Thanks for asking, Carrie! We will address those specific questions as we get closer to becoming fully accessible.
Great question about screen readers, Marc. We will have more details on this as we get closer to becoming fully accessible!
Hello! At my company, we want to create courses and ancillary resources for higher ed and K-12 in Rise. But in order to do that, we need to ensure that those resources will be WCAG 2.1 Level AA compliant--and of course that's not currently the case. Thanks for the features you've added so far; I hope that adding more accessibility features is a high priority for Articulate.
Its almost 3 years now I had posted accessibility support in Rise query.
Rise has been improved a lot till now. Many new features and templates make it more useful.Along with Storyline 360, it's been a really fast development tool I have worked on.
It would be really good if the plans shared by Articulate team to make Rise output comply with Accessibility standards should have some fixed timeline now.
Hi Mayuresh,
While we can’t share more specifics on timing and the order of features yet, our end goal is to get Rise 360 output WCAG 2.1 compliant by the end of 2020.
As we have more details and updates, we'll pass along that information to you!
Sorry just to check you are saying Rise won't be accessible for another 12 months?
Hi Jemma,
Our target timeframe for WCAG 2.1 compliance is by the end of 2020, but of course we'll let you know if we reach our goal sooner than that.
WCAG 2.1 AA?
Hi there, Carrie. Level AA is the goal! We'll keep you updated on the level of conformance for each of the WCAG criteria as we get closer to full support.
Is there information about how the upcoming enforcement of new UK legislation on the requirement to meet WCAG 2.1 AA will impact the improvements of Rise's accessibility standards?
https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction
As we have Rise based modules available to the general public if we are not able to meet WCAG guidelines this will have big implications for your e-Learning provision.
I’m sorry I don’t have a more specific update for you, Theodore. We are considering the impact on our UK customers as well.
Question relevant to this thread for planning purposes. Is the intent with the update to automate features or flag to attention anything in an existing course that needs to be updated to align with AA standard or will it be incumbent on each Rise user/author to go through all material to seek and rebuild those pieces?
Just want to be thoughtful about this as the year moves on so we aren't building to have to rebuild from scratch for things that will have more accessible options pending.
Hi Sarah,
We don’t have plans to include an accessibility auditing tool on courses that are already built. I don’t have more detail on the accessibility features coming to Rise 360 right now, but you’re in the right place to be notified of any updates we share in this discussion.
Just jumping in here to be kept in the loop.
Brian, I know this is an older thread, but I just wanted to confirm if Rise now has the capability for screen readers to detect language as you mention above. (I couldn't find this feature listed in the RISE 360 Version History...) Please advise. Thanks!
Hi Morton,
Screen reader support is coming to Rise 360, but it's not ready just yet. I don't have specific dates to share, but our end goal is to get Rise 360 output WCAG 2.1 compliant by the end of 2020. As we have more details and updates, we'll pass along that information to you!
Are there any updates (or a timeline) for WCAG 2.1 AA being met in Rise360?
Hi Kristopher,
I'm really sorry I don't have any details or timelines to share right now, but we promise to keep you updated as we know more.
The update I shared previously in this discussion is the latest information:
Hello from Finland!
We need to change the course language <html lang="en"> to fin or sv. If the language is en, screen readers try to read Finnish as if it was English and that doesn't work. Language should be something we'd be able to change in course settings along with colors etc.
We tried to change the course package language after exporting it into html, but there is something in the Rise script that prevents the language change afterwards.
Any ideas of workarounds before there is full accessibility in any language? Thank you!
Also, would it be possible to quickly fix some of the "seems to be an easy task" issues in accessibility, such as poor contrast in quizz feedback?
I suppose you have a (long) list of accessibility issues and also prioritized them. Is it available somewhere?
Hello, Tuire!
Rise 360 doesn't have full screen reader support just yet, but we're working on it! If you use a screen reader on a Rise 360 course now, you may find that it doesn't perform well.
We don't have a public list of accessibility improvements coming to Rise 360, but we'll share as much as we can as new information is available!
Hi Alyssa, in light of the COVID-19 crisis, I was wondering if there are any updates on Articulate's 2020 time frame for WCAG compliance. Are you still planning to be compliant this year, or are you expecting any delays? Thanks!
Thanks for asking, Nathan! Our goal is still to get Rise 360 output WCAG 2.1 compliant by the end of 2020. If we get new information that will be helpful to you, we'll let you know!