ACR for Totara 18

Name of Product/Version

Totara 18: Learn, Perform, and Engage

Report Date

November 2023

Product Description

Enterprise workplace learning management system (LMS), learning experience platform (LXP), and performance management system

Contact Information

enquiry@totaralearning.com

Evaluation Methods Used

• Design reviews using WCAG POUR framework

• Automated linting and testing in the codebase

• Peer review of front-end code for accessibility compliance

• Browser extensions to test rendered code in the browser: Deque's aXe; The Paciello Group's ARC Toolkit

• Manual assessment of WCAG Success Criteria, partially facilitated by Microsoft's Accessibility Insights

• Functional testing with Screen Readers: VoiceOver on MacOS, NVDA on Windows, Orca on Ubuntu

Relied upon technologies

HTML5, XHTML 1.0, CSS, WAI-ARIA, ECMAScript 5, SVG

Desktop browsers

• Chrome, Microsoft Edge: The latest stable release

• Firefox: The latest stable release

• Safari 14

Mobile browsers

• iOS Safari 13

• Android browser: The latest stable release

• Chrome for Android: The latest stable release

Screen readers

• NVDA

• Jaws

• VoiceOver

• Orca

Web Content Accessibility Guidelines 2.0

Level A

Level AA

Web Content Accessibility Guidelines 2.1

Level A

Level AA

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

Yes

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.1.1 (2019-11)

Yes

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.

1.1.1 Non-text Content

Also applies to EN 301 549 Criteria - 9.1.1.1 (Web)

Supports

Totara 18 uses alternative text or visually hidden text to provide text alternatives for all images and icons.

Authoring Tool: the Weka editor allows content creators to add alternative text for uploaded images.

1.2.1 Audio-only and Video-only (Prerecorded)

Also applies to EN 301 549 Criteria - 9.1.2.1 (Web)

Supports

Totara 18 does not include any pre-recorded audio or video content.

Authoring Tool: content creators can add audio and video content. The Weka editor allows content creators to add audio and video transcripts.

1.2.2 Captions (Prerecorded)

Also applies to EN 301 549 Criteria - 9.1.2.2 (Web)

Supports

Totara 18 does not include any audio content.

Authoring Tool: content creators can add audio and video content. The Weka editor allows content creators to add captions.

1.2.3 Audio Description or Media Alternative (Prerecorded)

Also applies to EN 301 549 Criteria - 9.1.2.3 (Web)

Supports

Totara 18 does not include any video content.

Authoring Tool: content creators can add audio content as an alternative to time-based media.

1.3.1 Info and Relationships

Also applies to EN 301 549 Criteria - 9.1.3.1 (Web)

Supports

Totara 18 uses semantic HTML (including headings and labels) and ARIA (including landmarks and roles) to provide structure and relationship to its content.

Authoring Tool: the Weka editor allows content creators to add HTML headings and lists.

1.3.2 Meaningful Sequence

Also applies to EN 301 549 Criteria - 9.1.3.2 (Web)

Supports

The reading order (source order) of page content in Totara 18 matches the visual presentation order.

1.3.3 Sensory Characteristics

Also applies to EN 301 549 Criteria - 9.1.3.3 (Web)

Supports

Totara 18 provides text instructions for using and understanding components and does not solely use sensory characteristics such as size, shape, or location.

1.4.1 Use of Color

Also applies to EN 301 549 Criteria - 9.1.4.1 (Web)

Supports

Totara 18 does not solely use colour to provide instructions; text, icons, outlines, borders, and line weight changes are used in addition.

1.4.2 Audio Control

Also applies to EN 301 549 Criteria - 9.1.4.2 (Web)

Supports

Totara 18 does not include any audio content.

Authoring Tool: the Weka editor embeds audio using the HTML5 audio element, including the relevant controls.

2.1.1 Keyboard

Also applies to EN 301 549 Criteria - 9.2.1.1 (Web)

Supports

The majority of Totara 18’s functionality is available from a keyboard, with no timing requirements. Standard HTML elements are used and ARIA Authoring Practices are followed for widgets such as accordions and modals.

2.1.2 No Keyboard Trap

Also applies to EN 301 549 Criteria - 9.2.1.2 (Web)

Supports

There are no keyboard traps in Totara 18, except when following standards in modal components.

2.2.1 Timing Adjustable

Also applies to EN 301 549 Criteria - 9.2.2.1 (Web)

Partially Supports

Only notifications have a time limit in Totara 18. This time limit can't be extended or turned off, but only supplemental and non-essential information is displayed in the notifications.

2.2.2 Pause, Stop, Hide

Also applies to EN 301 549 Criteria - 9.2.2.2 (Web)

Supports

Totara 18 does not contain any content that moves, blinks, scrolls, or auto-updates for longer than five seconds.

2.3.1 Three Flashes or Below Threshold

Also applies to EN 301 549 Criteria - 9.2.3.1 (Web)

Supports

Totara 18 does not contain any elements that flash.

2.4.1 Bypass Blocks

Also applies to EN 301 549 Criteria - 9.2.4.1 (Web)

Supports

Each repeated block of content in Totara is preceded by a link that lets the user skip over the block. ARIA landmarks are used to identify regions of the page. Some pages use accordions to allow bypassing of lengthy pieces of content.

2.4.2 Page Titled

Also applies to EN 301 549 Criteria - 9.2.4.2 (Web)

Partially Supports

The majority of pages in Totara 18 have descriptive titles, identifying the contents of the page and its broader context. The remainder are titled for the section they are, with page-level headings providing extra context.

2.4.3 Focus Order

Also applies to EN 301 549 Criteria - 9.2.4.3 (Web)

Supports

All interactive elements on a page are focusable and follow a logical and meaningful order. Buttons that trigger dialogs or menus are immediately adjacent to the content they trigger. Focus order is not adjusted from the logical order of the content of the page.

2.4.4 Link Purpose (In Context)

Also applies to EN 301 549 Criteria - 9.2.4.4 (Web)

Supports

Where the purpose of a link is not clear from its text, either the text around the link provides the necessary context or additional (visually hidden) text is provided for assistive technologies.

3.1.1 Language of Page

Also applies to EN 301 549 Criteria - 9.3.1.1 (Web)

Supports

The language of each page of Totara 18 is marked up using the HTML lang attribute.

3.2.1 On Focus

Also applies to EN 301 549 Criteria - 9.3.2.1 (Web)

Supports

No interface components in Totara 18 initiate a change of content on focus.

3.2.2 On Input

Also applies to EN 301 549 Criteria - 9.3.2.2 (Web)

Supports

No interface components in Totara 18 initiate a change of content on focus without explicitly advising the user in the (accessible) name of the control or the surrounding text.

3.3.1 Error Identification

Also applies to EN 301 549 Criteria - 9.3.3.1 (Web)

Partially Supports

Totara 18 uses text descriptions for all errors, ARIA attributes to provide additional information to users of assistive technology, and client-side validation and alerts. It is possible some areas of Totara 18 provide error messages without additional ARIA attributes. These will continue to be resolved as they are identified.

3.3.2 Labels or Instructions

Also applies to EN 301 549 Criteria - 9.3.3.2 (Web)

Partially Supports

Every form control has a name and every group of controls has a name. In many places, additional help text is provided, and in most places this additional text has ARIA attributes to programmatically link it to the form control. It is possible some areas of Totara 18 are not fully supported. These will continue to be resolved as they are identified.

4.1.2 Name, Role, Value

Also applies to EN 301 549 Criteria - 9.4.1.2 (Web)

Supports

In most places, Totara 18 uses standard HTML controls that have accessible names, roles, and values built in. Wherever necessary, Totara 18 applies ARIA attributes to provide names, roles, values, and states of custom UI components.

1.2.4 Captions (Live)

Also applies to EN 301 549 Criteria - 9.1.2.4

Supports

Totara 18 does not include any live audio content.

Authoring Tool: content creators can add audio and video content. The Weka editor allows content creators to add captions.

1.2.5 Audio Description (Prerecorded)

Also applies to EN 301 549 Criteria - 9.1.2.5

Supports

Totara 18 does not include any audio or video content.

Authoring Tool: content creators can add audio content that includes audio descriptions.

1.4.3 Contrast (Minimum)

Also applies to EN 301 549 Criteria - 9.1.4.3

Supports

All text in Totara 18 has a contrast ratio of at least 4.5:1.

1.4.4 Resize text

Also applies to EN 301 549 Criteria - 9.1.4.4

Supports

All content and functionality in Totara 18 is available when zoomed in 200%.

1.4.5 Images of Text

Also applies to EN 301 549 Criteria - 9.1.4.5

Supports

No images of text are used in Totara 18.

2.4.5 Multiple Ways

Also applies to EN 301 549 Criteria - 9.2.4.5

Supports

Totara 18 provides multiple ways to navigate all of its pages, including navigation menus, breadcrumbs, and search functionality.

2.4.6 Headings and Labels

Also applies to EN 301 549 Criteria - 9.2.4.6

Supports

All headings and labels in Totara 18 accurately and clearly describe the content they relate to.

2.4.7 Focus Visible

Also applies to EN 301 549 Criteria - 9.2.4.7

Supports

The item that has the current keyboard focus is always visible. In some cases using the browser default styles, in others using custom, clearer, focus styles.

3.1.2 Language of Parts

Also applies to EN 301 549 Criteria - 9.3.1.2

Not Applicable

All of Totara 18’s pages are in one language.

3.2.3 Consistent Navigation

Also applies to EN 301 549 Criteria - 9.3.2.3

Supports

Main navigation is identical across pages as it uses the same core module. Other navigation uses standard components for consistency.

3.2.4 Consistent Identification

Also applies to EN 301 549 Criteria - 9.3.2.4

Supports

A central source of UI text is used to ensure consistency of component names across pages.

3.3.3 Error Suggestion

Also applies to EN 301 549 Criteria - 9.3.3.3

Supports

Error messages are clear and succinct, specifying which fields are required and what any input format requirements are.

3.3.4 Error Prevention (Legal, Financial, Data)

Also applies to EN 301 549 Criteria - 9.3.3.4

Supports

All destructive actions in Totara 18 require a second confirmation action before proceeding. Some areas provide a review step.

2.1.4 Character Key Shortcuts

Also applies to EN 301 549 Criteria - 9.2.1.4 (Web)

Supports

Totara 18 does not use single-character key shortcuts.

Authoring Tool: the Weka editor uses common key shortcuts for formatting text that includes non-printing characters.

2.5.1 Pointer Gestures

Also applies to EN 301 549 Criteria - 9.2.5.1 (Web)

Supports

All of Totara 18 can be operated with a single pointer; no path-based or multipoint gestures are required.

2.5.2 Pointer Cancellation

Also applies to EN 301 549 Criteria - 9.2.5.2 (Web)

Supports

Totara 18 executes functions at the end of single-pointer actions, including touch. Where drag-and-drop actions are used, they can be cancelled.

2.5.3 Label in Name

Also applies to EN 301 549 Criteria - 9.2.5.3 (Web)

Supports

In most cases, the visible name and accessible name of interface components are identical. When they aren’t, the visible name is included in the accessible name.

2.5.4 Motion Actuation

Also applies to EN 301 549 Criteria - 9.2.5.4 (Web)

Supports

Totara 18 does not use any device motion or user motion to operate user interface components.

1.3.4 Orientation

Also applies to EN 301 549 Criteria - 9.1.3.4 (Web)

Supports

Totara 18 does not lock the display orientation.

1.3.5 Identify Input Purpose

Also applies to EN 301 549 Criteria - 9.1.3.5 (Web)

Supports

All fields relating to information about the user are marked up in accordance with the HTML 5 Autofill standards.

1.4.10 Reflow

Also applies to EN 301 549 Criteria - 9.1.4.10 (Web)

Supports

Totara 18 uses a range of CSS features (such as Flexbox and media queries) to allow reflow of content across different screen sizes and avoid scrolling in two dimensions.

1.4.11 Non-text Contrast

Also applies to EN 301 549 Criteria - 9.1.4.11 (Web)

Supports

UI components and icons in Totara 18 have a colour contrast ratio of at least 3:1.

1.4.12 Text Spacing

Also applies to EN 301 549 Criteria - 9.1.4.12 (Web)

Supports

Setting the line height, paragraph spacing, letter spacing, and word spacing to the values in the Success Criteria do not result in any loss of functionality or content.

1.4.13 Content on Hover or Focus

Also applies to EN 301 549 Criteria - 9.1.4.13 (Web)

Supports

All content in Totara 18 that is behind a hover action is dismissible, hoverable, and stays until removed or dismissed.

4.1.3 Status Messages

Also applies to EN 301 549 Criteria - 9.4.1.3 (Web)

Supports

Status messages in Totara use the correct ARIA roles. Only important and urgent messages use role="alert" or aria-live="assertive".

302.1 Without Vision

Not applicable

Technical Standards Fully supported

302.2 With Limited Vision

Not applicable

Technical Standards Fully supported

302.3 Without Perception of Color

Not applicable

Technical Standards Fully supported

302.4 Without Hearing

Not applicable

Technical Standards Fully supported

302.5 With Limited Hearing

Not applicable

Technical Standards Fully supported

302.6 Without Speech

Not applicable

Technical Standards Fully supported

302.7 With Limited Manipulation

Not applicable

Technical Standards Fully supported

302.8 With Limited Reach and Strength

Not applicable

Technical Standards Fully supported

302.9 With Limited Language, Cognitive, and Learning Abilities

Not applicable

Technical Standards Fully supported