On this page

All pages




Totara Learning Solutions Accessibility Conformance Report

International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version

Totara Mobile version 1.0.11 (released 16/06/2021)

Report Date

July 2021

Product Description

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

Contact Information

enquir[email protected]

Evaluation Methods Used

  • Automated testing using Accessibility Engine (axe) for Android
  • Manual assessment of WCAG Success Criteria, partially facilitated by Microsoft's Accessibility Insights
  • Functional testing with Screen Readers: VoiceOver on iOS, TalkBack on Android

Relied upon technologies

React Native and its accessibility API

Accessibility support baseline

Mobile Operating Systems

  • Android version 21 and above
  • iOS version 10 and above

Screen readers

  • TalkBack
  • VoiceOver

Summary

The overall compliance of the Totara mobile is Partially Supports WCAG 2.1 at Level A and AA. The product supports the majority of Success Criteria (SC) at both Level A and AA. The cases where the SC are classified as Partially Supports are either infrequent cases or have no impact on the user. The SC tables in this report include details on the planned improvements to achieve WCAG 2.1 Level AA support.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Terms

The terms used in the Conformance Level information are defined as follows:

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.0 Report

Tables 1 and 2 also document conformance with:

  • EN 301 549: Chapter 9 - Web
  • Revised Section 508

Note: When reporting on conformance with the WCAG 2.x 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: Each Criteria also applies to, except where noted:

  • EN 301 549 Criteria
    • 11.8.2 (Authoring Tool)
  • Revised Section 508
    • 501 (Web) (Software)
    • 504.2 (Authoring Tool)

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content

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

Supports

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

1.2.1 Audio-only and Video-only (Prerecorded)

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

Not Applicable

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

1.2.2 Captions (Prerecorded)

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

Not Applicable

Totara Mobile does not include any audio content.

1.2.3 Audio Description or Media Alternative (Prerecorded)

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

Not Applicable

Totara Mobile does not include any video content.

1.3.1 Info and Relationships

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

Partially Supports

Totara Mobile uses the React Native accessibility API to provide structure and relationship to its content. Exceptions have been logged as high-priority bugs.

1.3.2 Meaningful Sequence

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

Partially Supports

The reading order (source order) of page content in Totara Mobile matches the visual presentation order. Exceptions have been logged as high-priority bugs.

1.3.3 Sensory Characteristics

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

Supports

Totara Mobile 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 Mobile 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 Mobile does not include any audio content.

2.1.1 Keyboard

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

Not Applicable


2.1.2 No Keyboard Trap

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

Not Applicable


2.2.1 Timing Adjustable

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

Supports

No components have a time limit.

2.2.2 Pause, Stop, Hide

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

Supports

Totara Mobile 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 Mobile does not contain any elements that flash.

2.4.1 Bypass Blocks

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

Not applicable

2.4.2 Page Titled

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

Not applicable


2.4.3 Focus Order

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

Partially Supports

All interactive elements on a page are focusable and most follow a logical and meaningful order. The few exceptions have been logged as high-priority bugs.

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)

Not Applicable


3.2.1 On Focus

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

Not Applicable


3.2.2 On Input

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

Not Applicable


3.3.1 Error Identification

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

Supports

Totara Mobile uses text descriptions for all errors.

3.3.2 Labels or Instructions

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

Supports

Every form control has a name and every group of controls has a name. In many places additional help text is provided and has ARIA attributes to programmatically link it to the form control.

4.1.1 Parsing

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

Not Applicable


4.1.2 Name, Role, Value

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

Partially Supports

In most places, Totara Mobile uses standard controls that have accessible names, roles, and values built in. Exceptions have been logged as high-priority bugs.

Table 2: Success Criteria, Level AA

Notes: Each Criteria also applies to, except where noted:

  • EN 301 549 Criteria
    • 11.8.2 (Authoring Tool)
  • Revised Section 508
    • 501 (Web)(Software)
    • 504.2 (Authoring Tool)

Criteria

Conformance Level

Remarks and explanations

1.2.4 Captions (Live)

Also applies to EN 301 549 Criteria - 9.1.2.4

Not Applicable

Totara Mobile does not include any live audio content.

1.2.5 Audio Description (Prerecorded)

Also applies to EN 301 549 Criteria - 9.1.2.5

Not Applicable

Totara Mobile 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 Mobile 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

Partially Supports

Most content and functionality in Totara Mobile is available when zoomed in 200%. Exceptions to this have been logged as high-priority bugs.

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 Mobile.

2.4.5 Multiple Ways

Also applies to EN 301 549 Criteria - 9.2.4.5

Supports

Totara Mobile 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 Mobile 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

Not Applicable


3.1.2 Language of Parts

Also applies to EN 301 549 Criteria - 9.3.1.2

Not Applicable


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.

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 Mobile required a second confirmation action before proceeding. Some areas provide a review step.

WCAG 2.1 Report

Tables 1 and 2 also document conformance with:

  • EN 301 549: Chapter 9 - Web

Note: When reporting on conformance with the WCAG 2.x 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: Each Criteria also applies to, except where noted:

  • EN 301 549 Criteria
    • 11.8.2 (Authoring Tool)

Revised Section 508 – Does not apply.

Criteria

Conformance Level

Remarks and Explanations

2.1.4 Character Key Shortcuts

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

Not Applicable



2.5.1 Pointer Gestures

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

Supports

All of Totara Mobile 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 Mobile 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)

Partially 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. Exceptions to this have been logged as high-priority bugs.

2.5.4 Motion Actuation

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

Supports

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

Table 2: Success Criteria, Level AA

Notes: Each Criteria also applies to, except where noted:

  • EN 301 549 Criteria
    • 11.8.2 (Authoring Tool)

Revised Section 508 – Does not apply to WCAG 2.1.

Criteria

Conformance Level

Remarks and explanations

1.3.4 Orientation

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

Does Not Support

Totara Mobile does lock the display orientation.

1.3.5 Identify Input Purpose

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

Not Applicable


1.4.10 Reflow

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

Partially Supports

Totara Mobile uses a range of styling features to allow reflow of content across different screen sizes and avoid scrolling in two dimensions. Exceptions are logged as high-priority bugs.

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 Mobile 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 does 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 Mobile 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)

Not Applicable


Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Notes:

Criteria

Conformance Level

Remarks and explanations

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

Appendix 1 - Page-level testing list

  • Current Learning navigation item
    • Two views: carousel view and list view
    • Program page
      • Overview tab
      • Courses tab
    • Certification page
      • Overview tab
      • Courses tab
    • Course page
      • Overview tab
      • Activities tab
  • Downloads navigation item
  • Notifications navigation item
    • Notification item
  • Profile page