Rise 360 Accessibility Conformance Report
Article Last Updated
This article applies to:
We want to empower all learners to have accessible, compelling, and enjoyable e-learning experiences. With that goal in mind, we built Rise 360 to support Web Content Accessibility Guidelines (WCAG), as described in this report. We continue to refine Rise 360 so the courses you create go beyond technical compliance with these guidelines to become truly accessible to everyone. Keep an eye on our feature roadmap for all the latest enhancements in development.
Need a PDF version of this report? Download it here.
Based on VPAT® Version 2.4 International Edition
Voluntary Product Accessibility Template® and VPAT® are registered service marks of the Information Technology Industry Council (ITI).
Product Information
Name of Product/Version: Rise 360 (published output)
Report Date: March 3, 2023
Product Description: Use Rise 360 to create inherently responsive e-learning courses that work beautifully on every device.
Contact Information: a11y@articulate.com
Notes: This report is based on the March 3, 2023 build of Rise 360.
Evaluation Methods Used: We tested Rise 360 output with automated accessibility checkers and manual testing by accessibility specialists. We used desktop computers running Windows 11 and macOS 13 and mobile devices running iOS 16.1 and Android 13. We evaluated multiple web browsers, including Google Chrome 108, Microsoft Edge 108, Firefox 107, and Safari 16. We performed screen reader tests with JAWS 2022, NVDA 2022, VoiceOver in macOS 13 and iOS 16, and TalkBack 9.1. We also completed keyboard-only tests.
Applicable Standards/Guidelines: This report covers the degree of conformance with these accessibility standards/guidelines.
|
Standard/Guideline |
Included in Report |
|
Level A (Yes) | |
|
Level A (Yes) | |
|
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 |
Yes |
Terms: We use the following terms to define conformance levels for accessibility criteria.
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.1 Report
When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes: We'll update this conformance report as enhancements are released.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.1.1 Non-text Content (Level A) Also applies to Revised Section 508
|
Partially Supports |
Give learners text-based alternatives for non-text content. Use alt text to describe images. Use text blocks or interactive markers to provide expanded descriptions for complex images, such as charts and maps. For audio and video blocks, use the caption field to describe the purpose of the media. Scenario blocks don’t currently support alt text. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to Revised Section 508
|
Supports |
Give learners text-based alternatives for audio-only and video-only content. For audio, use a text block or an accordion interaction with a single tab to display a transcript. If the transcript is short, you can even use the caption field for the audio block. For videos that don't have narration, you can offer a text description of what happens in the video. Use a text block or the caption field. You also have the option of using an audio block to narrate the video. |
|
1.2.2 Captions (Prerecorded) (Level A) Also applies to Revised Section 508
|
Partially Supports |
Import closed captions for videos that have narration. Rise 360 doesn't currently support captions for audio blocks. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to Revised Section 508
|
Supports |
Give learners a separate audio track or a detailed text-based alternative to describe video content that can’t be heard in the audio—e.g., on-screen text, character actions, and scene changes. |
|
1.3.1 Info and Relationships (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 output is semantically formatted for easy screen reader navigation. |
|
1.3.2 Meaningful Sequence (Level A) Also applies to Revised Section 508
|
Partially Supports |
Rise 360 follows a logical navigation order for all content, except matching drag-and-drop questions. |
|
1.3.3 Sensory Characteristics (Level A) Also applies to Revised Section 508
|
Partially Supports |
Provide text-based instructions for content that can only be understood by shape, size, visual location, orientation, or sound. Matching drag-and-drop questions and sorting activities aren’t fully accessible yet. We’re working on these block types now. |
|
1.4.1 Use of Color (Level A) Also applies to Revised Section 508
|
Supports |
Provide alternatives when color is used to convey important information or instructions. Learners with color blindness might not see the differences in your color choices. Here are a couple of ways to meet this criterion:
|
|
1.4.2 Audio Control (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 doesn’t autoplay audio. |
|
2.1.1 Keyboard (Level A) Also applies to Revised Section 508
|
Partially Supports |
Much of the learning experience is already keyboard accessible, but we plan to optimize keyboard navigation for these block types:
Provide keyboard-accessible alternatives for the blocks listed above. |
|
2.1.2 No Keyboard Trap (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 courses don’t trap keyboard focus in subsections of content. Learners can use keyboard navigation without getting stuck. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Rise 360 output doesn’t use keyboard shortcuts. |
|
2.2.1 Timing Adjustable (Level A) Also applies to Revised Section 508
|
Not Applicable |
Rise 360 doesn’t use timed content. |
|
2.2.2 Pause, Stop, Hide (Level A) Also applies to Revised Section 508
|
Not Applicable |
Rise 360 doesn’t have auto-updating info or content that moves, scrolls, or blinks for more than five seconds. |
|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to Revised Section 508
|
Supports |
Don’t use videos or animations that flash or blink more than three times per second. Here’s a helpful tool that analyzes videos for content that might cause seizures. |
|
2.4.1 Bypass Blocks (Level A) Also applies to Revised Section 508
|
Supports |
Learners can skip repetitive sidebar navigation elements to access lesson content immediately when tabbing through a course with a screen reader. The skip-navigation feature is automatically enabled in all courses. |
|
2.4.2 Page Titled (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 automatically gives each lesson in your course a page title that follows this format: CourseTitle - Lesson Title | Rise 360. Titles appear on the browser tab, and screen readers announce them as learners navigate through the course. |
|
2.4.3 Focus Order (Level A) Also applies to Revised Section 508
|
Supports |
The navigation order of focusable elements, such as links and form controls, is logical and intuitive. |
|
2.4.4 Link Purpose (In Context) (Level A) Also applies to Revised Section 508
|
Supports |
Use meaningful text for every link so learners know what each one does. |
|
2.5.1 Pointer Gestures (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Rise 360 doesn't use touchscreen gestures. |
|
2.5.2 Pointer Cancellation (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Click events happen when learners release the mouse button, not when they press the mouse button down. This helps learners recover if they accidentally click the wrong target. They can move the mouse away from the target before releasing the button if they don’t want to activate the target. |
|
2.5.3 Label in Name (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Rise 360 interface elements have accessible names that match the visible labels. |
|
2.5.4 Motion Actuation (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Rise 360 doesn’t support motion controls. In other words, learners can’t control courses by moving their tablets or smartphones. |
|
3.1.1 Language of Page (Level A) Also applies to Revised Section 508
|
Supports |
Set the course language in your text labels, and screen readers will use that language to properly pronounce the interface elements and course content. |
|
3.2.1 On Focus (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 courses don’t change context when learners change focus. |
|
3.2.2 On Input (Level A) Also applies to Revised Section 508
|
Supports |
Learners can select form controls, such as radio buttons, and enter info in text-entry fields, but Rise 360 doesn't change context when they do. |
|
3.3.1 Error Identification (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 communicates errors when they occur. |
|
3.3.2 Labels or Instructions (Level A) Also applies to Revised Section 508
|
Partially Supports |
Rise 360 provides instructions for interactions, except sorting activities and matching drag-and-drop questions. Use a text block to provide instructions if you use these interactive blocks. |
|
4.1.1 Parsing (Level A) Also applies to Revised Section 508
|
Supports |
Rise 360 generates well-formed HTML output. |
|
4.1.2 Name, Role, Value (Level A) Also applies to Revised Section 508
|
Partially Supports |
Rise 360 uses distinct semantic groups, ARIA landmarks, and structured controls that follow a consistent order and hierarchy. There are a few exceptions. We're making improvements to these block types:
|
Table 2: Success Criteria, Level AA
Notes: Rise 360 doesn't support 1.2.5 Audio Description or 3.1.2 Language of Parts. We'll update this conformance report as enhancements are released.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) Also applies to Revised Section 508
|
Not Applicable |
Rise 360 doesn’t use real-time broadcasts. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to Revised Section 508
|
Does Not Support |
Audio descriptions must be created in a separate app, then imported into Rise 360. For example, sync audio descriptions with a video in Storyline 360, and then publish the slide as a video file. |
|
1.3.4 Orientation (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Content automatically reflows and works beautifully in both landscape and portrait modes. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Rise 360 doesn’t have input fields for learners' personal info, such as phone numbers, addresses, birthdays, or payment methods. |
|
1.4.3 Contrast (Minimum) (Level AA) Also applies to Revised Section 508
|
Supports |
Rise 360 interface elements meet minimum contrast guidelines. Be sure to use a contrast ratio of 4.5:1 or higher for on-screen text so learners with low vision can read it. Here’s a helpful contrast checker to determine your contrast ratio. |
|
1.4.4 Resize text (Level AA) Also applies to Revised Section 508
|
Supports |
Rise 360 courses are inherently responsive, so content scales and reflows as needed when learners interact with their browser zoom features. |
|
1.4.5 Images of Text (Level AA) Also applies to Revised Section 508
|
Supports |
Rise 360 interface elements don't rely on images of text. Be sure to use text blocks to convey important information rather than importing images of text, which can’t be read by assistive tools. |
|
1.4.10 Reflow (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Rise 360 content reflows as learners zoom in so they never need to scroll horizontally. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Rise 360 interface elements meet non-text contrast guidelines. Be sure your Rise 360 accent color and block background color have a 3:1 contrast ratio or higher. Here’s a helpful contrast checker to determine your contrast ratio. |
|
1.4.12 Text Spacing (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Partially Supports |
Most text content in Rise 360 responds to learners' custom styling, such as increased font size and line spacing. We plan to optimize all text (e.g., the continue block) to give learners full control over styling. |
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Content that appears only when an element has focus (e.g., a tooltip) is dismissible, hoverable, and persistent. |
|
2.4.5 Multiple Ways (Level AA) Also applies to Revised Section 508
|
Supports |
Rise 360 courses have a cover page with an interactive outline, sidebar navigation features, and a search field for finding content. |
|
2.4.6 Headings and Labels (Level AA) Also applies to Revised Section 508
|
Supports |
Built-in controls are properly labeled and identified. For lesson content, authors can use heading blocks to organize and label content. |
|
2.4.7 Focus Visible (Level AA) Also applies to Revised Section 508
|
Supports |
A rectangle highlights the object that currently has focus when learners use keyboard navigation. |
|
3.1.2 Language of Parts (Level AA) Also applies to Revised Section 508
|
Does Not Support |
Rise 360 doesn’t support different screen reader languages for different text blocks in the same course. |
|
3.2.3 Consistent Navigation (Level AA) Also applies to Revised Section 508
|
Supports |
Built-in navigation elements always appear in the same location. |
|
3.2.4 Consistent Identification (Level AA) Also applies to Revised Section 508
|
Supports |
Rise 360 consistently identifies built-in components. When you use an object or interaction more than once, be sure to identify it the same way each time. For example, if you use button blocks to jump to other locations, label them consistently throughout your course. |
|
3.3.3 Error Suggestion (Level AA) Also applies to Revised Section 508
|
Supports |
Give learners feedback or instructions so they know what’s expected when they respond incorrectly to quiz questions and knowledge checks. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to Revised Section 508
|
Not Applicable |
Rise 360 doesn't cause legal commitments or financial transactions to occur. |
|
4.1.3 Status Messages (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Partially Supported |
Status messages don’t appear without a change in context, except for matching drag-and-drop interactions and sorting activities. |
Revised Section 508 Report
Notes: Rise 360 output supports applicable Revised Section 508 accessibility guidelines, as described in the following tables.
Chapter 3: Functional Performance Criteria (FPC)
Notes: There are a few block types (listed below) that need keyboard optimization and while Rise 360 supports closed captions for videos, captions aren't supported for audio blocks yet.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
Partially Supports |
Rise 360 output supports screen readers and keyboard navigation. We plan to optimize keyboard navigation for these block types:
Provide keyboard-accessible alternatives for the blocks listed above. | |
|
Supports |
Rise 360 output uses accessible contrast for built-in elements. As an author, you should use accessible contrast for content you add to Rise 360. Here’s a helpful contrast checker to determine your contrast ratio. Rise 360 courses are inherently responsive, so content scales and reflows as learners interact with their browser zoom features. Links and buttons have visible focus and hover states. | |
|
Supports |
Authors can create content that’s understood by learners who don’t perceive color. | |
|
Partially Supports |
Import closed captions for videos that have narration. Rise 360 doesn't currently support captions for audio blocks. Authors can also provide transcripts for multimedia using text or interactive blocks in Rise 360. | |
|
Partially Supports |
Import closed captions for videos that have narration. Rise 360 doesn't currently support captions for audio blocks. Authors can also provide transcripts for multimedia using text or interactive blocks in Rise 360. | |
|
Supports |
Rise 360 doesn’t require speech input. | |
|
Partially Supports |
Use only keyboard-accessible features in your course. Most Rise 360 blocks are easy to navigate with a keyboard. We plan to optimize keyboard navigation for these block types:
Provide keyboard-accessible alternatives for the blocks listed above. | |
|
Supports |
Courses can be navigated via mouse, keyboard, and touchscreen. Authors can create content that’s suitable for learners with limited reach and strength. | |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
Create content that’s easily accessible for learners with limited language, cognitive, and learning abilities. For example, use visual elements rather than text to tell your story when it makes sense to do so. Write content as clearly and simply as possible. It should require no more than eight years of school to read and understand. If your course has difficult or complex text, such as scientific information or medical data, provide a summary or supplemental content that’s easier to understand. Tip: If you have Microsoft Word, you can test the readability of your text. |
Chapter 4: Hardware
Notes: This chapter isn’t applicable to Rise 360 output since it doesn’t have hardware components.
Chapter 5: Software
Notes: Rise 360 supports most applicable criteria in the following table. However, Rise 360 doesn't have audio description controls, export accessible PDFs, or prompt authors to create accessible content.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
See information in the WCAG 2.1 section above. | ||
|
See 502.2.1-502.2.2 |
| |
|
Not Applicable |
This criterion applies to platform software, such as Microsoft Windows and Google Chrome, rather than the HTML output that Rise 360 publishes for these platforms. Click here for a list of operating systems and web browsers that are supported with Rise 360 output. | |
|
Supports |
Courses don’t disrupt platform accessibility features in the learner’s operating system or web browser. | |
|
Not Applicable |
Criteria 502.3.1-502.3.14 apply to platform software, such as Microsoft Windows and Google Chrome, rather than the HTML output that Rise 360 publishes for these platforms. Click here for a list of operating systems and web browsers that are supported with Rise 360 output. | |
|
Not Applicable |
This criterion applies to platform software, such as Microsoft Windows and Google Chrome, rather than the HTML output that Rise 360 publishes for these platforms. Click here for a list of operating systems and web browsers that are supported with Rise 360 output. | |
|
See 503.2-503.3 |
| |
|
Supports |
Learners can use platform settings, such as custom stylesheets or browser extensions, to personalize the font face, font size, color, contrast, etc. to meet their needs and preferences. | |
|
Not Applicable |
Rise 360 doesn't have an alternative user interface that functions as assistive technology. All learners use the same interface, which supports assistive technologies, such as screen readers and magnifiers. | |
|
See 503.4.1-5.3.4.2 |
| |
|
Supports |
The built-in video player has a closed captioning button and volume control at the same menu level. | |
|
Does Not Support |
Rise 360 doesn't have built-in controls for audio descriptions. However, you can create a video with audio descriptions in a separate app, then import the video into Rise 360. For example, you can sync audio descriptions with a video in Storyline 360, and then publish the slide as a video file. | |
|
See 504.2-504.4 |
| |
|
See information in the WCAG 2.1 section above. | ||
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Does Not Support |
Accessibility info, such as alt text, isn't preserved when exporting a project to PDF. |
|
Does Not Support |
Rise 360 uses PDF version 1.4 for exported projects. Accessibility info, such as alt text, isn't preserved when exporting a project to PDF. | |
|
Does Not Support |
Rise 360 doesn't have a mode of operation that prompts authors to create accessible content. | |
|
Supports |
Rise 360 templates provide access to accessibility tools, such as alt text and closed captions. |
Chapter 6: Support Documentation and Services
Notes: Rise 360 features are documented electronically, and we strive to support everyone according to their communication needs.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
|
| |
|
See 602.2-602.4 |
| |
|
Supports |
All features are documented in the Rise 360 user guide. Additional knowledge base articles can be found on our support site. | |
|
Supports |
You can find all of our documentation in electronic format at https://articulate.com. See our accessibility policy regarding WCAG conformance. | |
|
602.4 Alternate Formats for Non-Electronic Support Documentation |
Not Applicable |
Rise 360 features are documented electronically. |
|
See 603.2-603.3 |
| |
|
603.2 Information on Accessibility and Compatibility Features |
Supports |
We provide support via emails, live text-based chats, forum discussions, training webinars, user guides, and knowledge base articles. |
|
Supports |
Although this report covers Rise 360 output (not the authoring interface), we strive to accommodate everyone’s communication needs. We can be reached 24/7 via email. Let us know if you have specific communication requirements. |