Reach 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 Reach 360 to support Web Content Accessibility Guidelines (WCAG), as described in this report. We continue to refine Reach 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: Reach 360 (navigational elements of the learning experience, not the hosted training content)
Report Date: April 4, 2023
Product Description: Deliver Articulate 360 training to all learners with Reach 360.
Contact Information: a11y@articulate.com
Notes: This report is based on the April 4, 2023 build of Reach 360.
Evaluation Methods Used: We tested the Reach 360 learner experience with automated accessibility checkers and manual testing by accessibility specialists. We used desktop computers running the latest versions of Windows and macOS, plus mobile devices running the latest versions of iOS and Android. We evaluated multiple web browsers, including the latest versions of Google Chrome, Microsoft Edge, Firefox, and Safari. We performed screen reader tests with JAWS 2022, NVDA 2022, VoiceOver in macOS and iOS, and TalkBack for Android. 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.1 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
|
Supports |
Non-text items have alternative text. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to Revised Section 508
|
Not Applicable |
The Reach 360 learner experience doesn’t have audio or video content. For conformance information on audio and video content included in project files from Articulate 360, please see our reports for Rise 360 and Storyline 360. |
|
1.2.2 Captions (Prerecorded) (Level A) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn't have audio content. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn't have video content. |
|
1.3.1 Info and Relationships (Level A) Also applies to Revised Section 508
|
Partially Supports |
Information can be programmatically determined throughout the learner experience with some exceptions in the library sidebar. |
|
1.3.2 Meaningful Sequence (Level A) Also applies to Revised Section 508
|
Partially Supports |
The reading order is correct, with some minor exceptions where the screen reader may not properly announce disabled content. |
|
1.3.3 Sensory Characteristics (Level A) Also applies to Revised Section 508
|
Not Applicable |
Instructions within the Reach 360 learner experience do not rely on sensory characteristics. |
|
1.4.1 Use of Color (Level A) Also applies to Revised Section 508
|
Supports |
Color alone isn't used to convey information within the user interface. |
|
1.4.2 Audio Control (Level A) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn't have audio content. |
|
2.1.1 Keyboard (Level A) Also applies to Revised Section 508
|
Partially Supports |
Most of the learner experience is keyboard accessible, with the exception of some tooltips. |
|
2.1.2 No Keyboard Trap (Level A) Also applies to Revised Section 508
|
Supports |
Navigating the learner experience in Reach 360 doesn’t cause a keyboard trap. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Reach 360 doesn’t have keyboard shortcuts. |
|
2.2.1 Timing Adjustable (Level A) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn’t use timed content. |
|
2.2.2 Pause, Stop, Hide (Level A) Also applies to Revised Section 508
|
Not Applicable |
Reach 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 |
Reach 360 doesn’t have flashing content. |
|
2.4.1 Bypass Blocks (Level A) Also applies to Revised Section 508
|
Supports |
The learner experience in Reach 360 has a skip to main content link. |
|
2.4.2 Page Titled (Level A) Also applies to Revised Section 508
|
Supports |
Reach 360 has a descriptive page title. |
|
2.4.3 Focus Order (Level A) Also applies to Revised Section 508
|
Partially Supports |
The Reach 360 learner experience has a meaningful focus order, with a few exceptions. For instance, hidden elements may still be read by screen readers. |
|
2.4.4 Link Purpose (In Context) (Level A) Also applies to Revised Section 508
|
Supports |
Reach 360 provides meaningful link phrases. |
|
2.5.1 Pointer Gestures (Level A 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
Reach 360 doesn’t have 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 |
Interface elements in the learning experience 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 |
Reach 360 doesn’t have motion controls. |
|
3.1.1 Language of Page (Level A) Also applies to Revised Section 508
|
Supports |
Reach 360 includes programmatically identified language of pages. |
|
3.2.1 On Focus (Level A) Also applies to Revised Section 508
|
Supports |
Reach 360 doesn’t change context when learners change focus. |
|
3.2.2 On Input (Level A) Also applies to Revised Section 508
|
Supports |
When interacting with the Reach 360 interface, users do not experience any unexpected changes in context. |
|
3.3.1 Error Identification (Level A) Also applies to Revised Section 508
|
Partially Supports |
The Reach 360 learner experience informs learners of input errors through text. However, there is one minor exception: the email validation error on the login form is not announced. |
|
3.3.2 Labels or Instructions (Level A) Also applies to Revised Section 508
|
Partially Supports |
Labels are provided in Reach 360 when content requires input, with some minor exceptions where the screen reader may not properly announce disabled content. |
|
4.1.1 Parsing (Level A) Also applies to Revised Section 508
|
Supports |
Reach 360 provides well-formed HTML that is compatible with assistive technology. |
|
4.1.2 Name, Role, Value (Level A) Also applies to Revised Section 508
|
Partially Supports |
Reach 360 provides the correct name, role, and value throughout the learner experience with some exceptions in the library. |
Table 2: Success Criteria, Level AA
Notes: 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 |
Reach 360 doesn't have audio content. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn't have video content. |
|
1.3.4 Orientation (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Content automatically reflows and works beautifully in landscape and portrait modes. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Not Applicable |
There are no 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 |
Reach 360 interface elements that meet the minimum contrast guidelines. |
|
1.4.4 Resize text (Level AA) Also applies to Revised Section 508
|
Supports |
Text can be resized up to 200% without any loss of content or functionality. |
|
1.4.5 Images of Text (Level AA) Also applies to Revised Section 508
|
Not Applicable |
The Reach 360 learning experience doesn’t include images of text. |
|
1.4.10 Reflow (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Content will reflow as learners zoom in, so they will never need to scroll horizontally. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Partially Supports |
The Reach 360 learner experience meets non-text contrast guidelines, except for the favorite button and green checkmarks that indicate when the password requirement has been met. |
|
1.4.12 Text Spacing (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Supports |
Use browser tools and extensions to adjust text properties, such as spacing. |
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Partially Supports |
Most pointer hovers on tooltips are visible within Reach 360 until dismissed. However, we would like to improve the tooltips on the create button and user badge. |
|
2.4.5 Multiple Ways (Level AA) Also applies to Revised Section 508
|
Supports |
Reach 360 provides multiple ways of locating content within the application. |
|
2.4.6 Headings and Labels (Level AA) Also applies to Revised Section 508
|
Supports |
The headings and labels in Reach 360 are descriptive. |
|
2.4.7 Focus Visible (Level AA) Also applies to Revised Section 508
|
Partially Supports |
When learners use keyboard navigation, a rectangle highlights the object that currently has focus. However, the default focus rectangle is not consistently used and we would like to improve this. |
|
3.1.2 Language of Parts (Level AA) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn’t have any text with a change in language. |
|
3.2.3 Consistent Navigation (Level AA) Also applies to Revised Section 508
|
Supports |
Reach 360 has consistent navigation mechanisms across the learner experience. |
|
3.2.4 Consistent Identification (Level AA) Also applies to Revised Section 508
|
Supports |
Similar components within the learner experience are identified consistently. |
|
3.3.3 Error Suggestion (Level AA) Also applies to Revised Section 508
|
Supports |
The Reach 360 learner experience provides suggestions for resolving input errors when they are detected. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to Revised Section 508
|
Not Applicable |
Reach 360 doesn’t have any legal commitments or financial transactions. |
|
4.1.3 Status Messages (Level AA 2.1 only) Doesn't apply to Revised Section 508 |
Partially Supported |
Status messages for Reach 360 only appear when there is a change in context, and they are accessible to assistive technology. However, there might be minor exceptions where the screen reader might not properly announce results after input.. |
Revised Section 508 Report
Notes: Reach 360 supports applicable Revised Section 508 accessibility guidelines, as described in the following tables.
Chapter 3: Functional Performance Criteria (FPC)
Notes: The learner experience in Reach 360 supports or partially supports all applicable criteria in the following table.
Chapter 4: Hardware
Notes: This chapter isn’t applicable to Reach 360 since it doesn’t have hardware components.
Chapter 5: Software
Notes: The learning experience in Reach 360 supports most applicable criteria in the following table.
|
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. We provide a list of supported browsers. | |
|
Supports |
Reach 360 doesn’t cause a disruption of 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. We provide a list of supported browsers. | |
|
Not Applicable |
This criterion applies to platform software, such as Microsoft Windows and Google Chrome. We provide a list of supported browsers. | |
|
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 |
Reach 360 doesn’t have an alternative interface that functions as assistive technology. All learners use the same interface, which supports assistive technologies like screen readers and magnifiers. | |
|
See 503.4.1-5.3.4.2 |
| |
|
Not Applicable |
Reach 360 doesn’t have audio or video content | |
|
Not Applicable |
Reach 360 doesn’t have audio content. | |
|
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 |
Not Applicable |
Reach 360 isn’t an authoring tool. |
|
Not Applicable |
Reach 360 isn’t an authoring tool and doesn’t produce PDFs. | |
|
Not Applicable |
Reach 360 isn’t an authoring tool and doesn’t have a mode of operation that prompts. | |
|
Not Applicable |
Reach 360 doesn’t have templates. |
Chapter 6: Support Documentation and Services
Notes: Reach 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 Reach 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 |
Reach 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 the Reach 360 Learn platform, 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. |