Report sulla conformità dell'accessibilità di Reach 360

Last Updated March 26, 2026

Product Information
WCAG 2.2 Report
Revised Section 508 Report
EN 301 549 Report

Reach 360 is designed to support accessible, engaging, and effective training experiences for all learners. This report describes how the Reach 360 user interface aligns with the Web Content Accessibility Guidelines (WCAG). This evaluation is limited to the navigational elements of the learning experience.

Accessibility is an ongoing focus for Reach 360. We continue to improve the user interface to support a wide range of needs and preferences. For updates on recent enhancements, see our Feature Roadmap and What’s New page.

This is a living document and is updated as enhancements are released. Known accessibility considerations are documented in the Reach 360 Accessibility Maturity Plan. If you encounter an accessibility issue, please let us know. We’re committed to improving the experience over time.

Need a PDF version of this report? Download it here.

Based on VPAT^® Version 2.5 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 (user interface for navigational elements of the learning experience; excludes hosted training content)

Report Date: March 26, 2026

Product Description: Deliver Articulate 360 training to all learners with Reach 360.

Contact Information: [email protected]

Notes: This report is based on the March 26, 2026 build of Reach 360.

Evaluation Methods Used: We evaluated the Reach 360 user interface using a combination of automated accessibility tools and manual testing conducted by internal QA team members and accessibility specialists.

Testing was performed on desktop computers running current versions of Windows and macOS, as well as mobile devices running current versions of iOS and Android. We tested using common web browsers, including Chrome, Edge, Firefox, and Safari.

Evaluation included keyboard-only navigation to assess use without a mouse. We also tested with assistive technologies such as JAWS, NVDA, Narrator, and Magnifier on Windows; VoiceOver on macOS and iOS; and TalkBack on Android.

Applicable Standards/Guidelines: This report covers the degree of conformance with these accessibility standards/guidelines.

Standard/Guideline

Included in Report

Web Content Accessibility Guidelines 2.0

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Web Content Accessibility Guidelines 2.1

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Web Content Accessibility Guidelines 2.2

Level A (Yes)
Level AA (Yes)
Level AAA (Yes)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

Sì

EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11) AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

Sì

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.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG Level AAA.

WCAG 2.2 Report

Tables 1 and 2 also document conformance with:

EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.

Note: When reporting on conformance with the WCAG 2.2 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: This table describes how the Reach 360 user interface supports WCAG 2.2 Level A success criteria. This evaluation is limited to the navigational elements of the learning experience.

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

9.1.1.1 (Web)
10.1.1.1 (Non-web document)
11.1.1.1.1 (Open Functionality Software)
11.1.1.1.2 (Closed Functionality Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Non-text elements in the Reach 360 user interface include text alternatives where needed.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

9.1.2.1 (Web)
10.1.2.1 (Non-web document)
11.1.2.1.1 (Open Functionality Software)
11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include audio-only or video-only media.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

9.1.2.2 (Web)
10.1.2.2 (Non-web document)
11.1.2.2 (Open Functionality Software)
11.1.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include prerecorded audio or video.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

9.1.2.3 (Web)
10.1.2.3 (Non-web document)
11.1.2.3.1 (Open Functionality Software)
11.1.2.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include prerecorded video.

1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

9.1.3.1 (Web)
10.1.3.1 (Non-web document)
11.1.3.1.1 (Open Functionality Software)
11.1.3.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Partially Supports

Information is programmatically determinable in most areas of the Reach 360 user interface. Some elements, such as those in the library sidebar, may not fully convey this information.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

9.1.3.2 (Web)
10.1.3.2 (Non-web document)
11.1.3.2.1 (Open Functionality Software)
11.1.3.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Partially Supports

Content is presented in a meaningful reading order in most areas of the Reach 360 user interface. In some cases, screen readers may not correctly convey the sequence for disabled content.

1.3.3 Sensory Characteristics (Level A)

Also applies to:

EN 301 549 Criteria

9.1.3.3 (Web)
10.1.3.3 (Non-web document)
11.1.3.3 (Open Functionality Software)
11.1.3.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface does not rely solely on sensory characteristics such as shape, color, or sound to convey information.

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

9.1.4.1 (Web)
10.1.4.1 (Non-web document)
11.1.4.1 (Open Functionality Software)
11.1.4.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Color is not used as the only means of conveying information in the Reach 360 user interface. Additional visual cues, such as text labels or icons, are used where needed.

1.4.2 Audio Control (Level A)

Also applies to:

EN 301 549 Criteria

9.1.4.2 (Web)
10.1.4.2 (Non-web document)
11.1.4.2 (Open Functionality Software)
11.1.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include audio that plays automatically.

2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

9.2.1.1 (Web)
10.2.1.1 (Non-web document)
11.2.1.1.1 (Open Functionality Software)
11.2.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface supports keyboard navigation.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

9.2.1.2 (Web)
10.2.1.2 (Non-web document)
11.2.1.2 (Open Functionality Software)
11.2.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface does not trap keyboard focus.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.2.1.4 (Web)
10.2.1.4 (Non-web document)
11.2.1.4.1 (Open Functionality Software)
11.2.1.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

Reach 360 does not include single-character keyboard shortcuts.

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

9.2.2.1 (Web)
10.2.2.1 (Non-web document)
11.2.2.1 (Open Functionality Software)
11.2.2.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface does not include time limits.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:

EN 301 549 Criteria

9.2.2.2 (Web)
10.2.2.2 (Non-web document)
11.2.2.2 (Open Functionality Software)
11.2.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Too

Supports

The Reach 360 user interface does not include content that moves, blinks, or auto-updates.

2.3.1 Three Flashes or Below Threshold (Level A)

Also applies to:

EN 301 549 Criteria

9.2.3.1 (Web)
10.2.3.1 (Non-web document)
11.2.3.1 (Open Functionality Software)
11.2.3.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface does not include flashing content.

2.4.1 Bypass Blocks (Level A)

Also applies to:

EN 301 549 Criteria

9.2.4.1 (Web)
10.2.4.1 (Non-web document) – Does not apply
11.2.4.1 (Open Functionality Software) – Does not apply
11.2.4.1 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Supports

The Reach 360 user interface provides a mechanism to bypass repeated content.

2.4.2 Page Titled (Level A)

Also applies to:

EN 301 549 Criteria

9.2.4.2 (Web)
10.2.4.2 (Non-web document)
11.2.4.2 (Open Functionality Software) - Does not apply
11.2.4.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Pages in the Reach 360 user interface include descriptive titles.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

9.2.4.3 (Web)
10.2.4.3 (Non-web document)
11.2.4.3 (Open Functionality Software)
11.2.4.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Partially Supports

The Reach 360 user interface provides a logical focus order. In some cases, visually hidden elements may still be announced by screen readers, which can affect navigation.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:

EN 301 549 Criteria

9.2.4.4 (Web)
10.2.4.4 (Non-web document)
11.2.4.4 (Open Functionality Software)
11.2.4.4 (Closed Software
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Links and interactive elements in the Reach 360 user interface have a meaningful purpose.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.2.5.1 (Web)
10.2.5.1 (Non-web document)
11.2.5.1 (Open Functionality Software)
11.2.5.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports interaction without requiring complex pointer gestures. Interactions can be completed using simple actions such as clicking or tapping.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.2.5.2 (Web)
10.2.5.2 (Non-web document)
11.2.5.2 (Open Functionality Software)
11.2.5.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Interactive elements activate on mouse release rather than mouse press. This allows users to move the pointer away from a target before completing the action.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.2.5.3 (Web)
10.2.5.3 (Non-web document)
11.2.5.3.1 (Open Functionality Software)
11.2.5.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Interface elements include accessible names that match visible labels.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.2.5.4 (Web)
10.2.5.4 (Non-web document)
11.2.5.4 (Open Functionality Software)
11.2.5.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

Reach 360 does not support motion-based input.

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

9.3.1.1 (Web)
10.3.1.1 (Non-web document)
11.3.1.1.1 (Open Functionality Software)
11.3.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Reach 360 includes a programmatically identified page language.

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

9.3.2.1 (Web)
10.3.2.1 (Non-web document)
11.3.2.1 (Open Functionality Software)
11.3.2.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Changing focus in Reach 360 does not trigger a change of context.

3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

9.3.2.2 (Web)
10.3.2.2 (Non-web document)
11.3.2.2 (Open Functionality Software)
11.3.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Changing input in Reach 360 does not trigger a change of context.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not applicable

Reach 360 does not include built-in help mechanisms.

3.3.1 Error Identification (Level A)

Also applies to:

EN 301 549 Criteria

9.3.3.1 (Web)
10.3.3.1 (Non-web document)
11.3.3.1.1 (Open Functionality Software)
11.3.3.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Reach 360 provides text-based feedback to identify input errors where input is required.

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

9.3.3.2 (Web)
10.3.3.2 (Non-web document)
11.3.3.2 (Open Functionality Software)
11.3.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Reach 360 provides labels or instructions where input is required.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not applicable

Reach 360 does not require users to enter the same information multiple times.

4.1.1 Parsing (Level A)

Applies to:

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

EN 301 549 Criteria

9.4.1.1 (Web)
10.4.1.1 (Non-web document)
11.4.1.1.1 (Open Functionality Software)
11.4.1.1.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

9.4.1.2 (Web)
10.4.1.2 (Non-web document)
11.4.1.2.1 (Open Functionality Software)
11.4.1.2.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

User interface components in Reach 360 provide programmatically determinable names, roles, and values.

Table 2: Success Criteria, Level AA

Notes: This table describes how the Reach 360 user interface supports WCAG 2.2 Level AA success criteria. This evaluation is limited to the navigational elements of the learning experience.

Criteria

Conformance Level

Remarks and Explanations

1.2.4 Captions (Live) (Level AA)

Also applies to:

EN 301 549 Criteria

9.1.2.4 (Web)
10.1.2.4 (Non-web document)
11.1.2.4 (Open Functionality Software)
11.1.2.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not support live audio or video streaming.

1.2.5 Audio Description (Prerecorded) (Level AA)

Also applies to:

EN 301 549 Criteria

9.1.2.5 (Web)
10.1.2.5 (Non-web document)
11.1.2.5 (Open Functionality Software)
11.1.2.5 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include prerecorded video.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.3.4 (Web)
10.1.3.4 (Non-web document)
11.1.3.4 (Open Functionality Software)
11.1.3.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports both landscape and portrait orientations and does not restrict content to a single orientation.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.3.5 (Web)
10.1.3.5 (Non-web document)
11.1.3.5.1 (Open Functionality Software)
11.1.3.5.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not include input fields that collect personal user information requiring programmatic identification of input purpose, as described in this criterion.

1.4.3 Contrast (Minimum) (Level AA)

Also applies to:

EN 301 549 Criteria

9.1.4.3 (Web)
10.1.4.3 (Non-web document)
11.1.4.3 (Open Functionality Software)
11.1.4.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Text and interface elements in the Reach 360 user interface meet minimum contrast requirements.

1.4.4 Resize text (Level AA)

Also applies to:

EN 301 549 Criteria

9.1.4.4 (Web)
10.1.4.4 (Non-web document)
11.1.4.4.1 (Open Functionality Software)
11.1.4.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Text in the Reach 360 user interface can be resized up to 200% without loss of content or functionality.

1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

9.1.4.5 (Web)
10.1.4.5 (Non-web document)
11.1.4.5.1 (Open Functionality Software)
11.1.4.5.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface uses text rather than images of text to present information.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.4.10 (Web)
10.1.4.10 (Non-web document)
11.1.4.10 (Open Functionality Software)
11.1.4.10 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

Content in the Reach 360 user interface reflows as the viewport is resized or zoomed, without requiring horizontal scrolling.

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.4.11 (Web)
10.1.4.11 (Non-web document)
11.1.4.11 (Open Functionality Software)
11.1.4.11 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

User interface components in Reach 360 meet non-text contrast requirements in most areas. Some elements, such as the favorite button and status indicators (e.g., password-requirement checkmarks), may not meet contrast requirements.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.4.12 (Web)
10.1.4.12 (Non-web document)
11.1.4.12 (Open Functionality Software)
11.1.4.12 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports text spacing adjustments via browser settings and assistive technologies without loss of content or functionality.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.1.4.13 (Web)
10.1.4.13 (Non-web document)
11.1.4.13 (Open Functionality Software)
11.1.4.13 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Content that appears on hover or focus in the Reach 360 user interface is generally visible and can be dismissed. Some elements, such as tooltips associated with the create button and user badge, may not fully meet these requirements.

2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

9.2.4.5 (Web)
10.2.4.5 (Non-web document) – Does not apply
11.2.4.5 (Open Functionality Software) – Does not apply
11.2.4.5 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Supports

The Reach 360 user interface provides multiple ways to locate content, such as navigation menus and search.

2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

9.2.4.6 (Web)
10.2.4.6 (Non-web document)
11.2.4.6 (Open Functionality Software)
11.2.4.6 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

Headings and labels in the Reach 360 user interface are descriptive and identify the purpose of content and controls.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

9.2.4.7 (Web)
10.2.4.7 (Non-web document)
11.2.4.7 (Open Functionality Software)
11.2.4.7 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Partially Supports

A visible focus indicator is provided for interactive elements in the Reach 360 user interface. In some cases, the focus indicator is not consistently displayed.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Partially Supports

In most cases, focused elements in the Reach 360 user interface remain visible. In mobile view, the browse library filter sidebar may remain open and obscure focused elements when navigating by keyboard.

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not applicable

The Reach 360 user interface does not require dragging movements for interaction.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Interactive elements in the Reach 360 user interface meet minimum target size requirements or are spaced sufficiently to prevent accidental activation.

3.1.2 Language of Parts (Level AA)

Also applies to:

EN 301 549 Criteria

9.3.1.2 (Web)
10.3.1.2 (Non-web document)
11.3.1.2 (Open Functionality Software) – Does not apply
11.3.1.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include content with multiple language changes within a page.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

9.3.2.3 (Web)
10.3.2.3 (Non-web document) – Does not apply
11.3.2.3 (Open Functionality Software) – Does not apply
11.3.2.3 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Supports

Navigation mechanisms in the Reach 360 user interface are presented consistently across pages.

3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

9.3.2.4 (Web)
10.3.2.4 (Non-web document) – Does not apply
11.3.2.4 (Open Functionality Software) – Does not apply
11.3.2.4 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Supports

Components with the same functionality in the Reach 360 user interface are identified consistently.

3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

9.3.3.3 (Web)
10.3.3.3 (Non-web document)
11.3.3.3 (Open Functionality Software)
11.3.3.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Supports

The Reach 360 user interface provides suggestions for resolving input errors when they are detected.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

EN 301 549 Criteria

9.3.3.4 (Web)
10.3.3.4 (Non-web document)
11.3.3.4 (Open Functionality Software)
11.3.3.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Not Applicable

The Reach 360 user interface does not include interactions that involve legal commitments, financial transactions, or submission of user-controlled data.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports password managers and does not rely on cognitive function tests for authentication.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

9.4.1.3 (Web)
10.4.1.3 (Non-web document)
11.4.1.3 (Open Functionality Software)
11.4.1.3 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Partially Supports

Status messages in the Reach 360 user interface are programmatically determinable and, in most cases, exposed to assistive technologies. In some situations, screen readers may not announce updates after user input.

Table 3: Success Criteria, Level AAA

Notes: This table describes how the Reach 360 user interface supports WCAG 2.2 Level AAA success criteria. This evaluation is limited to the navigational elements of the learning experience.

Criteria

Conformance Level

Remarks and Explanations

1.2.6 Sign Language (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not include prerecorded audio or video.

1.2.7 Extended Audio Description (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not include prerecorded video.

1.2.8 Media Alternative (Prerecorded) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not include prerecorded audio or video.

1.2.9 Audio-only (Live) (Level AAA)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not support live audio.

1.3.6 Identify Purpose (Level AAA 2.1 and 2.2)

EN 301 549 Criteria– Does not apply

Revised Section 508 – Does not apply

Supports

Regions and user interface components in Reach 360 have programmatically determinable purposes.

1.4.6 Contrast (Enhanced) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Text and interface elements in Reach 360 meet enhanced contrast requirements.

1.4.7 Low or No Background Audio (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Applicable

The Reach 360 user interface does not include audio.

1.4.8 Visual Presentation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports user control of text presentation, including adjustments to size, spacing, and contrast, through browser and assistive technology settings.

1.4.9 Images of Text (No Exception) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses text rather than images of text to present information.

2.1.3 Keyboard (No Exception) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Keyboard interaction in the Reach 360 user interface does not require specific timing for keystrokes.

2.2.3 No Timing (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface does not include time limits.

2.2.4 Interruptions (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface does not include auto-updating or interruptive content.

2.2.5 Re-authenticating (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Evaluated

2.2.6 Timeouts (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not Evaluated

2.3.2 Three Flashes (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface does not include content that flashes more than three times per second.

2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface does not include motion or animation triggered by user interaction.

2.4.8 Location (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface provides information about the user’s location within the application, such as the current page or folder.

2.4.9 Link Purpose (Link Only) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Links in the Reach 360 user interface have descriptive text that identifies their purpose.

2.4.10 Section Headings (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses section headings to organize content and support navigation.

2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Partially Supports

In most cases, focused elements in the Reach 360 user interface remain visible and are not obscured. In mobile view, the browse library filter sidebar may remain open and obscure focused elements when navigating by keyboard.

2.4.13 Focus Appearance (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Partially Supports

In most areas, the focus indicator in the Reach 360 user interface meets enhanced visibility requirements. In some areas, such as course or learning path overview pages and during course playback, the focus indicator may not fully meet these requirements.

2.5.5 Target Size (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Partially Supports

Most interactive elements in the Reach 360 user interface meet target size requirements. Some elements, such as the favorite button, may not meet the minimum target size.

2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports interaction using a mouse, keyboard, and touch input without requiring a specific input method.

3.1.3 Unusual Words (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses clear, familiar language and avoids unexplained, unusual words.

3.1.4 Abbreviations (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses clear language and avoids unexplained abbreviations.

3.1.5 Reading Level (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses clear, simple language to support understanding.

3.1.6 Pronunciation (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface uses clear language and avoids words where pronunciation is needed to understand meaning.

3.2.5 Change on Request (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

Changes in the Reach 360 user interface occur in response to user interaction rather than automatically.

3.3.5 Help (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface provides guidance and instructions where needed.

3.3.6 Error Prevention (All) (Level AAA)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface provides information and suggestions to help users correct input errors where input is required.

3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Supports

The Reach 360 user interface supports accessible authentication and does not rely on cognitive function tests.

Revised Section 508 Report

Notes: This section describes how the Reach 360 user interface supports applicable Revised Section 508 accessibility requirements. This evaluation is limited to the navigational elements of the learning experience.

Chapter 3: Functional Performance Criteria (FPC)

Notes: This section describes how the Reach 360 user interface supports applicable Functional Performance Criteria. Support may vary by feature.

Criteria

Conformance Level

Remarks and Explanations

302.1 Without Vision

Partially Supports

The Reach 360 user interface supports use with screen readers and keyboard navigation in most areas. Some elements may not be fully accessible to screen reader users.

302.2 With Limited Vision

Partially Supports

The Reach 360 user interface supports use with limited vision through zoom, text resizing, and sufficient contrast in most areas. Some interface elements may not fully support these features.

302.3 Without Perception of Color

Supports

The Reach 360 user interface supports use without color perception by conveying information through text, labels, and other visual indicators.

302.4 Without Hearing

Supports

The Reach 360 user interface does not rely on audio for operation.

302.5 With Limited Hearing

Supports

The Reach 360 user interface supports use with limited hearing and does not rely on audio for operation.

302.6 Without Speech

Supports

The Reach 360 user interface supports use without speech and does not require speech input.

302.7 With Limited Manipulation

Partially Supports

The Reach 360 user interface supports use with limited manipulation in most areas. Some interface elements may require precise interaction or may not be fully operable using alternative input methods.

302.8 With Limited Reach and Strength

Supports

The Reach 360 user interface supports use with limited reach and strength and allows interaction via mouse, keyboard, and touch.

302.9 With Limited Language, Cognitive, and Learning Abilities

Partially Supports

The Reach 360 user interface supports use by individuals with limited language, cognitive, and learning abilities through a clear, consistent interface across most areas. Some elements may not fully support these needs.

Chapter 4: Hardware

Notes: This chapter is not applicable because Reach 360 does not include hardware components.

Chapter 5: Software

Notes: This section describes how the Reach 360 user interface supports applicable software requirements. This evaluation is limited to the navigational elements of the learning experience.

Criteria

Conformance Level

Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.2 section

Conformance is addressed in the WCAG 2.2 section of this report. The applicable Level A and AA success criteria are detailed there.

502 Interoperability with Assistive Technology

See 502.2.1-502.2.2

502.2.1 User Control of Accessibility Features

Not Applicable

This criterion applies to platform software that provides accessibility features. Reach 360 runs within supported browsers and does not control platform-level accessibility settings.

502.2.2 No Disruption of Accessibility Features

Supports

The Reach 360 user interface does not disrupt accessibility features provided by the browser or operating system.

502.3 Accessibility Services

Not Applicable

Criteria 502.3.1–502.3.14 apply to platform software that provides accessibility services. Reach 360 runs within supported browsers and does not provide platform accessibility services.

502.4 Platform Accessibility Features

Not Applicable

This criterion applies to platform software that provides accessibility features. Reach 360 runs within supported browsers and does not provide platform accessibility features.

503 Applications

See 503.2-503.3

503.2 User Preferences

Supports

The Reach 360 user interface respects user preferences set at the browser or operating system level, such as font size, color, and contrast.

503.3 Alternative User Interfaces

Supports

The Reach 360 user interface is designed to work with assistive technologies, such as screen readers and magnifiers.

503.4 User Controls for Captions and Audio Description

See 503.4.1-5.3.4.2

503.4.1 Caption Controls

Not Applicable

The Reach 360 user interface does not include video with captions.

503.4.2 Audio Description Controls

Not Applicable

The Reach 360 user interface does not include audio or video with audio description.

504 Authoring Tools

See 504.2-504.4

504.2 Content Creation or Editing

Not Applicable

This report evaluates the Reach 360 user interface. Content creation and editing features are outside the scope of this evaluation.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

This report evaluates the Reach 360 user interface. Format conversion features are outside the scope of this evaluation.

504.2.2 PDF Export

Not Applicable

This report evaluates the Reach 360 user interface. PDF export features are outside the scope of this evaluation.

504.3 Prompts

Not Applicable

This report evaluates the Reach 360 user interface. Authoring prompts and guidance features are outside the scope of this evaluation.

504.4 Templates

Not Applicable

This report evaluates the Reach 360 user interface. Template and content creation features are outside the scope of this evaluation.

Chapter 6: Support Documentation and Services

Notes: Reach 360 documentation is provided electronically. Information about accessibility features is available in product documentation. Support services are available through standard customer support channels.

Criteria

Conformance Level

Remarks and Explanations

601.1 Scope

602 Support Documentation

See 602.2-602.4

602.2 Accessibility and Compatibility Features

Supports

Accessibility and compatibility features of Reach 360 are described in the product documentation and user guides. Additional guidance is available in knowledge base articles on the support site.

602.3 Electronic Support Documentation

Supports

Support documentation for Reach 360 is available electronically on the Articulate website. Accessibility information, including the company’s accessibility policy, is also available online.

602.4 Alternate Formats for Non-Electronic Support Documentation

Not Applicable

Support documentation for Reach 360 is provided electronically. Non-electronic documentation is not offered.

603 Support Services

See 603.2-603.3

603.2 Information on Accessibility and Compatibility Features

Supports

Information about accessibility and compatibility features is available through Reach 360 support services, including email, chat, community forums, webinars, user guides, and knowledge base articles.

603.3 Accommodation of Communication Needs

Supports

Support services for Reach 360 are available through multiple communication channels, including email and text-based chat. Accommodations can be provided to support specific communication needs upon request.

EN 301 549 Report

Notes: This section describes how the Reach 360 user interface supports applicable EN 301 549 accessibility requirements. This evaluation is limited to the navigational elements of the learning experience.

Chapter 4: Functional Performance Statements (FPS)

Notes: This section describes how the Reach 360 user interface supports applicable Functional Performance Statements. This evaluation is limited to the navigational elements of the learning experience.

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Partially Supports

The Reach 360 user interface supports use without vision through screen reader compatibility and keyboard navigation in most areas. Some interface elements may not be fully accessible.

4.2.2 Usage with limited vision

Partially Supports

The Reach 360 user interface supports use with limited vision through zoom, text resizing, and sufficient contrast in most areas. Some interface elements may not fully support these features.

4.2.3 Usage without perception of colour

Supports

The Reach 360 user interface supports use without color perception by conveying information through text, labels, and other visual indicators.

4.2.4 Usage without hearing

Supports

The Reach 360 user interface supports use without hearing and does not rely on audio for operation.

4.2.5 Usage with limited hearing

Supports

The Reach 360 user interface supports use with limited hearing and does not rely on audio for operation.

4.2.6 Usage with no or limited vocal capability

Supports

The Reach 360 user interface supports use without speech and does not require speech input.

4.2.7 Usage with limited manipulation or strength

Partially Supports

The Reach 360 user interface supports use with limited manipulation or strength in most areas. Some interface elements may require precise interaction or may not be fully operable using alternative input methods.

4.2.8 Usage with limited reach

Supports

The Reach 360 user interface supports limited reach and allows interaction via mouse, keyboard, and touch.

4.2.9 Minimize photosensitive seizure triggers

Supports

The Reach 360 user interface is photo-safe and does not include content that flashes more than 3 times per second.

4.2.10 Usage with limited cognition, language or learning

Partially Supports

The Reach 360 user interface supports use by individuals with limited cognition, language, or learning abilities through a clear, consistent interface across most areas. Some elements may not fully support these needs.

4.2.11 Privacy

Supports

The Reach 360 user interface supports user privacy and does not require users to disclose a disability or use accessibility features.

Chapter 5: Generic Requirements

Notes: This chapter is not applicable because Reach 360 operates in standard computing environments and supports the use of platform accessibility features and assistive technologies.

Chapter 6: ICT with Two-Way Voice Communication

Notes: This chapter is not applicable because Reach 360 does not support two-way voice communication.

Chapter 7: ICT with Video Capabilities

Notes: This chapter is not applicable because the Reach 360 user interface does not include video.

Chapter 8: Hardware

Notes: This chapter is not applicable because Reach 360 does not include hardware components.

Chapter 9: Web

Notes: This chapter aligns with WCAG requirements for web content. Conformance details for the Reach 360 user interface are provided in the WCAG 2.2 section of this report.

Chapter 10: Non-Web Documents

Notes: This chapter is not applicable because Reach 360 does not include non-web documents.

Chapter 11: Software

Notes: This chapter is not applicable because it applies to platform software. Reach 360 runs within supported browsers and does not provide platform-level software functionality.

Chapter 12: Documentation and Support Services

Notes: Reach 360 documentation is provided in electronic format. Information about accessibility features is available in product documentation and support resources. Support services are available through standard customer support channels.

Criteria

Conformance Level

Remarks and Explanations

12.1 Product documentation

12.1.1 Accessibility and compatibility features

Supports

Accessibility and compatibility features of Reach 360 are described in the product documentation and user guides. Additional guidance is available in knowledge base articles on the support site.

12.1.2 Accessible documentation

Supports

Reach 360 documentation is available in accessible electronic formats and aligns with applicable WCAG requirements.

12.2 Support Services

12.2.2 Information on accessibility and compatibility features

Supports

12.2.3 Effective communication

Supports

12.2.4 Accessible documentation

Supports

Documentation provided through Reach 360 support services is available in accessible electronic formats and is designed to align with applicable WCAG requirements.

Chapter 13: ICT Providing Relay or Emergency Service Access

Notes: This chapter is not applicable because Reach 360 does not provide relay services or access to emergency services.