ACR for Totara 16
Totara Learning Solutions Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4)
Name of Product/Version | Totara 16: Learn, Perform, and Engage |
Report Date | May 2022 |
Product Description | Enterprise workplace learning management system (LMS), learning experience platform (LXP), and performance management system |
Contact Information | |
Evaluation Methods Used |
|
Relied upon technologies | HTML5, XHTML 1.0, CSS, WAI-ARIA, ECMAScript 5, SVG. |
Accessibility support baseline | |
---|---|
Desktop browsers |
|
Mobile browsers |
|
Screen readers |
|
Summary
The overall compliance of Totara 16: Learn, Perform, and Engage 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:
Standard/Guideline | Included In Report |
---|---|
Level A Level AA | |
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 |
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 criterion 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 |
---|---|---|
Also applies to EN 301 549 Criteria - 9.1.1.1 (Web) | Supports | Totara 16 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 16 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. |
Also applies to EN 301 549 Criteria - 9.1.2.2 (Web) | Supports | Totara 16 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 16 does not include any video content. Authoring Tool: content creators can add audio content as an alternative to time-based media. |
Also applies to EN 301 549 Criteria - 9.1.3.1 (Web) | Supports | Totara 16 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. |
Also applies to EN 301 549 Criteria - 9.1.3.2 (Web) | Supports | The reading order (source order) of page content in Totara 16 matches the visual presentation order. |
Also applies to EN 301 549 Criteria - 9.1.3.3 (Web) | Supports | Totara 16 provides text instructions for using and understanding components and does not solely use sensory characteristics such as size, shape, or location. |
Also applies to EN 301 549 Criteria - 9.1.4.1 (Web) | Supports | Totara 16 does not solely use colour to provide instructions: text, icons, outlines, borders, and line weight changes are used in addition. |
Also applies to EN 301 549 Criteria - 9.1.4.2 (Web) | Supports | Totara 16 does not include any audio content. Authoring Tool: the Weka editor embeds audio using the HTML5 audio element, including the relevant controls. |
Also applies to EN 301 549 Criteria - 9.2.1.1 (Web) | Supports | The majority of Totara 16’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. |
Also applies to EN 301 549 Criteria - 9.2.1.2 (Web) | Supports | There are no keyboard traps in Totara 16, except when following standards in modal components. |
Also applies to EN 301 549 Criteria - 9.2.2.1 (Web) | Partially Supports | Only notifications have a time limit in Totara 16. This time limit can't be extended or turned off, but only supplemental and non-essential information is displayed in the notifications. |
Also applies to EN 301 549 Criteria - 9.2.2.2 (Web) | Supports | Totara 16 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 16 does not contain any elements that flash. |
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. |
Also applies to EN 301 549 Criteria - 9.2.4.2 (Web) | Partially Supports | The majority of pages in Totara 16 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. |
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. |
Also applies to EN 301 549 Criteria - 9.3.1.1 (Web) | Supports | The language of each page of Totara 16 is marked up using the HTML lang attribute. |
Also applies to EN 301 549 Criteria - 9.3.2.1 (Web) | Supports | No interface components in Totara 16 initiate a change of content on focus. |
Also applies to EN 301 549 Criteria - 9.3.2.2 (Web) | Supports | No interface components in Totara 16 initiate a change of content on focus without explicitly advising the user in the (accessible) name of the control or the surrounding text. |
Also applies to EN 301 549 Criteria - 9.3.3.1 (Web) | Partially Supports | Totara 16 uses text descriptions for all errors, ARIA attributes to provide additional information to users of assistive technology, and client-side validation and alerts. Some areas of Totara 16 provide error messages without additional ARIA attributes. These have been logged as bugs. |
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. Bugs have been logged for the exceptions. |
Also applies to EN 301 549 Criteria - 9.4.1.1 (Web) | Partially Supports | While not all pages in Totara 16 pass full HTML validation, the failures do not affect the user’s experience of the page in any way. |
Also applies to EN 301 549 Criteria - 9.4.1.2 (Web) | Supports | In most places, Totara 16 uses standard HTML controls that have accessible names, roles, and values built in. Wherever necessary, Totara 16 applies ARIA attributes to provide names, roles, values, and states of custom UI components. |
Table 2: Success Criteria, Level AA
Notes: each criterion 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 |
---|---|---|
Also applies to EN 301 549 Criteria - 9.1.2.4 | Partially Supports | Totara 16 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 16 does not include any audio or video content. Authoring Tool: content creators can add audio content that includes audio descriptions. |
Also applies to EN 301 549 Criteria - 9.1.4.3 | Supports | All text in Totara 16 has a contrast ratio of at least 4.5:1. |
Also applies to EN 301 549 Criteria - 9.1.4.4 | Supports | All content and functionality in Totara 16 is available when zoomed in 200%. |
Also applies to EN 301 549 Criteria - 9.1.4.5 | Supports | No images of text are used in Totara 16. |
Also applies to EN 301 549 Criteria - 9.2.4.5 | Supports | Totara 16 provides multiple ways to navigate all of its pages, including navigation menus, breadcrumbs, and search functionality. |
Also applies to EN 301 549 Criteria - 9.2.4.6 | Supports | All headings and labels in Totara 16 accurately and clearly describe the content they relate to. |
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 uses custom, clearer, focus styles. |
Also applies to EN 301 549 Criteria - 9.3.1.2 | Not Applicable | All of Totara 16’s pages are in one language. |
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. |
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 16 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 criterion 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 |
---|---|---|
Also applies to EN 301 549 Criteria - 9.2.1.4 (Web) | Supports | Totara 16 does not use single-character key shortcuts. Authoring Tool: the Weka editor uses common key shortcuts for formatting text that include non-printing characters. |
Also applies to EN 301 549 Criteria - 9.2.5.1 (Web) | Supports | All of Totara 16 can be operated with a single pointer: no path-based or multipoint gestures are required. |
Also applies to EN 301 549 Criteria - 9.2.5.2 (Web) | Supports | Totara 16 executes functions at the end of single pointer actions, including touch. Where drag-and-drop actions are used, they can be cancelled. |
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. |
Also applies to EN 301 549 Criteria - 9.2.5.4 (Web) | Supports | Totara 16 does not use any device motion or user motion to operate user interface components. |
Table 2: Success Criteria, Level AA
Notes: each criterion 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 |
---|---|---|
Also applies to EN 301 549 Criteria - 9.1.3.4 (Web) | Supports | Totara 16 does not lock the display orientation. |
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. |
Also applies to EN 301 549 Criteria - 9.1.4.10 (Web) | Supports | Totara 16 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. |
Also applies to EN 301 549 Criteria - 9.1.4.11 (Web) | Supports | UI components and icons in Totara 16 have a colour contrast ratio of at least 3:1. |
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 16 that is behind a hover action is dismissible, hoverable, and stays until removed or dismissed. |
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". |
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
Learn
Existing functionality, tested against new in 2.1 SC
A handful of key learner-facing pages with high traffic.
Dashboard
Catalogue (grid, the default)
Courses (and programs and certifications)
Topics
Single activity
Quizzes
Seminars
Book
Forum
Feedback
Certificate
Formats
Activities
Front page
Record of Learning
Team
LinkedIn Learning
Engage
Library
Library
Resource
Survey
Your resources - create / edit
Your playlists - create / edit
Edit survey
Shared with you
Saved resources
A playlist from Your playlists
Overview tab
Comments tab
A resource
Overview tab
Comments tab
Workspaces
Find workspaces
A workspace
Discuss tab
Library tab
Members tab
Browse files
Dashboard
Recommendation
Perform
Competencies
Competency profile
Charts
Tables
Competency detail for a competency
Rate competencies
Self-assign competencies
Manage competency assignments
Currently assigned users
Create assignments
Performance activities
Performance activities
Your activities
Activities about others
Manage performance activities
General tab
Content tab
Assignments tab
Edit content elements
Report
Completing an activity
Review elements
Evidence bank
Evidence bank
Add evidence item
Add evidence item - details
Manage evidence types
Create