{"id":4723,"date":"2024-02-29T08:00:41","date_gmt":"2024-02-29T08:00:41","guid":{"rendered":"http:\/\/localhost:10054\/?p=4723"},"modified":"2025-03-11T14:06:33","modified_gmt":"2025-03-11T14:06:33","slug":"articulate-rise-accessibility","status":"publish","type":"post","link":"https:\/\/maestrolearning.com\/blogs\/articulate-rise-accessibility\/","title":{"rendered":"Articulate Rise Accessibility: An Up-to-Date List of Accessible Components in Rise"},"content":{"rendered":"

Curious about Articulate Rise accessibility? You’re in the right place. At Maestro, we\u2019re dedicated to creating\u2014and helping you create\u2014meaningful learning experiences. Part of that goal is ensuring that all learners are able to utilize and enjoy the courses we design. To help achieve that goal, we\u2019ve made a list of the Articulate Rise components that are currently accessible so you can quickly identify and use them to better serve all of your learners.<\/p>\n

Read on for our Articulate Rise accessibility assessment and to view our up-to-date list of accessible components.<\/p>\n

Is Articulate Rise accessible?<\/h2>\n

We believe that learning should meet people where they are<\/a>, no matter where they are or who they are. And, because up to 1 in 4 adults in the U.S. has a disability<\/a>, it\u2019s crucial that the learning experiences we design meet accessibility standards. One way to meet these standards is by using eLearning authoring tools like Articulate Rise that include a11y in its mission.<\/p>\n

A11y<\/a> is a numeronym that means accessibility and is most often used in reference to digital design. Articulate has identified accessibility as a \u201ccritical part of [their] roadmap,\u201d and stated that they \u201cwant all learners to interact as fully as possible with the courses you create in Rise 360.\u201d So, is Articulate Rise accessible? Well, while they\u2019ve made a lot of progress, and it\u2019s possible to create AA-compliant learning in Rise, there are still some limits to watch out for when designing (we\u2019ll cover that in the list below).<\/p>\n

When it comes to accessibility, all components must be readable with a screen reader<\/a>. While Rise does support screen readers such as NVDA, JAWS, Talkback, and VoiceOver, they\u2019re not fully supported. For example, screen readers aren\u2019t able to read text within or underneath images. Additionally, although some components are accessible by keyboard, not all interactions allow learners to use a keyboard instead of using a mouse, which means that they aren\u2019t fully accessible. Currently, functions like drag-and-drops, sorting activities, and some matching knowledge checks aren\u2019t keyboard accessible. So, what components are accessible in Rise?<\/p>\n

Articulate Rise accessibility<\/h2>\n

To determine whether or not a component is accessible, consider whether the component can be fully accessed by a screen reader and keyboard navigation. If it passes those two tests, it\u2019s considered an accessible component. To be sure that the components in our list are accessible via a screen reader, we tested each of them using four different screen readers: NVDA, JAWS, Chrome extension, and VoiceOver.<\/p>\n

Based on our assessments, the components that are currently screen reader and keyboard accessible are:<\/p>\n