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.
Bumping this. Any updates with WCAG compliance? Alternatively, a list of what IS currently meeting standards and what ISNT would be a workaround for users in the meantime.
This is exactly the problem that I've just come up against (no heading structure in Rise). Admittedly, I haven't read the following thread, but has this been rectified, as far as you know?
In Brian's reply from 3/27/17, he states "We will add the ability for a screen reader to detect language in late Q2."
I would have expected from that response that by 2019 this would be in place, however, according to the Articulate website it states: "Rise 360 courses don't fully support screen readers yet. We're currently working on screen reader support. Stay tuned!"
I'm confused, if not "fully supported," how do Rise courses currently work with screen readers? Please advise.
I have the same question. I've completed quite a lot of screen reader testing and ive noticed that the continue block button and side navigation is quite finicky when it comes down to screen reader tests
Screen reader is not fully supported at the time being because it is still a work in progress. However you should find that headings are searchable, menus are readable, and we have landmarks, regions, and groups in place.
Hope this information helps a little. It is a work in progress so you'll definitely find pieces that aren't ready for primetime (e.g. the finicky stuff that Stephanie found).
We were initially excited about the Keyboard Accessible Navigation article published January 22. Having published a course or two in Rise prior to that, we noticed that the functionality was acceptable but could be improved. After conducting a few tests with JAWS today, I have to say that the functionality is actually worse than before.
Adding features to allow more customization to course components would be so helpful! Our agency loves the modern look and ease of use of Rise, but the bottom line is we can't use it at all if all of our learners can't access it.
I'm sorry to hear you're not happy with the way keyboard accessibility works in Rise. The only changes we've made recently were to add keyboard accessibility to the new blocks. The rest has been the same since we released the keyboard accessibility feature. If you're seeing new issues, please let our support team know.
In regards to your request for further customization, would you be up for logging a feature request to tell us more about your specific needs? Accessibility is top of mind for us and we'd love to hear from you about how we can make creating accessible courses easier for you.
In the meantime, if there’s anything else I can do to help, please let me know!
I'm finding accessibility options very limited with Rise and our new Instructional Designer does not recommend the tool for that reason. In Ontario, Canada, legislation requires that by 2025 all employers be up to standard on this. We are using Rise for some things at the moment but will need to rebuild/migrate to other platforms if accessibility standards can't be met with this tool. I really hope that Rise prioritizes this! It is a handy, quick, and easy tool that is a better fit for quick deployment than Storyline... but the value is hindered by the knowledge that some learners are being left out.
Hey, Sarah. Thank you for your input and we definitely hear you when it comes to accessibility in Rise 360. We want as many learners as possible to enjoy the amazing courses you're creating!
We know that we still have work to do when it comes to accessibility in Rise 360 courses and we want to get to the point where no one is left out.
Would you be willing to take a minute and log a feature request and tell us more about your specific needs? Every feature request we get helps us prioritize and focus in on what's going to help you the most.
Thanks again! Please let me know if there’s anything else I can help you with.
I just added this question to the Rise 360 Forum, but wanted to post here as well..
I am testing Rise files with JAWS. After almost every sentence, JAWS reads out "clickable" even when there are no links associated within the paragraph. This has occurred in Chrome, IE/Edge and Firefox. Has anyone else experienced this in their testing? Is there anything we can do about it so our JAWS users don't think everything is clickable?
I too would appreciate some information on the progress on making Rise compliant with accessibility standards? The EU Web Accessibility Directive requires its member states to meet WCAG 2.1 level AA standards for all new web content published after September 23, 2018. The effective date is September 23, 2019.
I appreciate that there has been progress here, but without being fully accessible to these standards we cannot recommend Rise as a suitable authoring tool for many of our public sector clients.
Are Articulate aiming to meet the new 2.1 WCAG standard rather than 2.0?
Rise 360 does not currently fully support screen readers, but we're working on it. Our ultimate goal is to meet Web Content Accessibility Guidelines (WCAG). So far, we’ve added these accessibility features:
Hi there, Neeraj. I hear the impact this improvement would have on your work, and we don't mean to sound redundant. We don't have a solid timeline for full accessibility support with Rise 360. I'll let you know as new features are released.
342 Replies
Looking for accessibility updates as well.
Thanks so much for sharing this information Ashley. It's very helpful.
Is there an update on keyboard navigation within Storyline blocks in Rise? Thanks!
Hi Brian,
Continuing to work towards getting Rise in line with WCAG guidelines is high on our priority list.
I don't have any updated timelines to share, but as soon as there are, we definitely will!
Bumping this. Any updates with WCAG compliance? Alternatively, a list of what IS currently meeting standards and what ISNT would be a workaround for users in the meantime.
Hi Stephanie,
I don't have any updates to share here yet. A list is a great idea, I'll pass that on to our team. :)
Hi Andrew,
This is exactly the problem that I've just come up against (no heading structure in Rise). Admittedly, I haven't read the following thread, but has this been rectified, as far as you know?
TIA
In Brian's reply from 3/27/17, he states "We will add the ability for a screen reader to detect language in late Q2."
I would have expected from that response that by 2019 this would be in place, however, according to the Articulate website it states: "Rise 360 courses don't fully support screen readers yet. We're currently working on screen reader support. Stay tuned!"
I'm confused, if not "fully supported," how do Rise courses currently work with screen readers? Please advise.
I have the same question. I've completed quite a lot of screen reader testing and ive noticed that the continue block button and side navigation is quite finicky when it comes down to screen reader tests
Hi Vanessa, Morton and Stephanie,
Screen reader is not fully supported at the time being because it is still a work in progress. However you should find that headings are searchable, menus are readable, and we have landmarks, regions, and groups in place.
Hope this information helps a little. It is a work in progress so you'll definitely find pieces that aren't ready for primetime (e.g. the finicky stuff that Stephanie found).
Hey Marvie,
Thanks for getting back to us.
We wait with excited anticipation :)
We were initially excited about the Keyboard Accessible Navigation article published January 22. Having published a course or two in Rise prior to that, we noticed that the functionality was acceptable but could be improved. After conducting a few tests with JAWS today, I have to say that the functionality is actually worse than before.
Adding features to allow more customization to course components would be so helpful! Our agency loves the modern look and ease of use of Rise, but the bottom line is we can't use it at all if all of our learners can't access it.
Please correct this soon.
Hi Elizabeth, out of interest, how is it worse than before?
Hi Elizabeth,
I'm sorry to hear you're not happy with the way keyboard accessibility works in Rise. The only changes we've made recently were to add keyboard accessibility to the new blocks. The rest has been the same since we released the keyboard accessibility feature. If you're seeing new issues, please let our support team know.
In regards to your request for further customization, would you be up for logging a feature request to tell us more about your specific needs? Accessibility is top of mind for us and we'd love to hear from you about how we can make creating accessible courses easier for you.
In the meantime, if there’s anything else I can do to help, please let me know!
I'm finding accessibility options very limited with Rise and our new Instructional Designer does not recommend the tool for that reason. In Ontario, Canada, legislation requires that by 2025 all employers be up to standard on this. We are using Rise for some things at the moment but will need to rebuild/migrate to other platforms if accessibility standards can't be met with this tool. I really hope that Rise prioritizes this! It is a handy, quick, and easy tool that is a better fit for quick deployment than Storyline... but the value is hindered by the knowledge that some learners are being left out.
Hey, Sarah. Thank you for your input and we definitely hear you when it comes to accessibility in Rise 360. We want as many learners as possible to enjoy the amazing courses you're creating!
We know that we still have work to do when it comes to accessibility in Rise 360 courses and we want to get to the point where no one is left out.
Would you be willing to take a minute and log a feature request and tell us more about your specific needs? Every feature request we get helps us prioritize and focus in on what's going to help you the most.
Thanks again! Please let me know if there’s anything else I can help you with.
Sure thing. Will do so now. Thanks.
Hi can you please give us a timeline on when Rise will be fully compliant, as this is holding us back in creating our online course.
Hi Neeraj,
I wish I could give you an exact ETA, but unfortunately I don't have one at this time. We'll share updates here as they're available.
Thanks for your understanding and patience as we work on these features!
Hi All,
I just added this question to the Rise 360 Forum, but wanted to post here as well..
I am testing Rise files with JAWS. After almost every sentence, JAWS reads out "clickable" even when there are no links associated within the paragraph. This has occurred in Chrome, IE/Edge and Firefox. Has anyone else experienced this in their testing? Is there anything we can do about it so our JAWS users don't think everything is clickable?
Hi,
I too would appreciate some information on the progress on making Rise compliant with accessibility standards? The EU Web Accessibility Directive requires its member states to meet WCAG 2.1 level AA standards for all new web content published after September 23, 2018. The effective date is September 23, 2019.
I appreciate that there has been progress here, but without being fully accessible to these standards we cannot recommend Rise as a suitable authoring tool for many of our public sector clients.
Are Articulate aiming to meet the new 2.1 WCAG standard rather than 2.0?
Thanks,
Ross
Hi Ross,
Rise 360 does not currently fully support screen readers, but we're working on it. Our ultimate goal is to meet Web Content Accessibility Guidelines (WCAG). So far, we’ve added these accessibility features:
Keep an eye on our "What's New" page and the Rise 360 release notes for details.
Hi Allison this is the answer you gave 4 months ago is there a timeline on being fully compliant as this is making a impact on out process of design
Hi there, Neeraj. I hear the impact this improvement would have on your work, and we don't mean to sound redundant. We don't have a solid timeline for full accessibility support with Rise 360. I'll let you know as new features are released.
https://www.insidehighered.com/news/2018/12/10/fifty-colleges-sued-barrage-ada-lawsuits-over-web-accessibility