ACR for Totara 19
Totara Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.5)
Name of Product/Version: Totara 19
Report Date: January 2025
Product Description: Learning Management System
Contact Information: enquiry@totara.com
Notes:
The following document captures our conformance levels and testing information for this major release of Totara. For a page-level testing list, see Appendix 1. While the information below is accurate to the best of our current knowledge, due to the size and configurable complexity of our product, not all areas and configurations have been tested. If accessibility is a major concern for an implementation, we recommend that an independent accessibility audit is created. We also encourage raising issues and specification-guided improvements so that we can further improve on our commitment to accessibility. For customisations to Totara, please refer to our release notes, so that you can retest any areas that may be affected during an upgrade.
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
Colour contrast checking
Browser extensions to test rendered code in the browser: Deque's aXe, The Paciello Group's ARC Toolkit, ANDI
Manual assessment of WCAG Success Criteria, partially facilitated by Microsoft's Accessibility Insights
Functional testing with screen readers: VoiceOver on MacOS, NVDA on Windows
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline | Included In Report |
Level A (Yes) Level AA (Yes) Level AAA (No) | |
Level A (Yes) Level AA (Yes) Level AAA (No) | |
Level A (Yes) Level AA (Yes) Level AAA (No) | |
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | (Yes) |
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) | (Yes / No ) |
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.
Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.x 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.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:
Criteria | Conformance Level | Remarks and Explanations |
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: Non-text content supplied with Totara has alternative text content. Authoring Tool: Both Weka and Atto editors encourage non-text content to have text equivalent. |
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Not Applicable Authoring Tool: Supports | Web: No audio or video content is shipped with Totara 19. Authoring Tool: Both Weka and Atto editors encourage audio and video elements to have text equivalent. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Not Applicable Authoring Tool: Supports | Web: No audio or video content is shipped with Totara 19. Authoring Tool: Both Weka and Atto editors encourage audio and video elements to have text equivalent. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Not Applicable Authoring Tool: Supports | Web: No audio or video content is shipped with Totara 19. Authoring Tool: Both Weka and Atto editors encourage audio and video elements to have text equivalent.
|
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Partially supports Authoring Tool: Partially supports | Web: There has been a considerable effort in ensuring correct relationships have been created and maintained, however as with any project the size of Totara, there may be locations that have been missed. Authoring Tool: Basic functionality is supported. |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: Content is displayed in a meaningful sequence. Authoring Tool: While it is possible to create content in a non-meaningful way, the correct order is encouraged. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: Core functionality. Authoring Tool: Content could be created that does not match these criteria. |
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: Colour is not the only means of identifying functionality. Authoring Tool: As with most content authoring tools, content could be made inaccessible. |
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Not applicable Authoring Tool: Supports | Web: No audio or visual content is provided with Totara 19. Authoring Tool: Content can be made to autoplay with both Weka and Atto, however standard audio controls are displayed for a user to control playback. |
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: All content can be accessed via the keyboard only through native integrations. Authoring Tool: All content can be accessed via the keyboard only through native integrations.
|
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: There are no keyboard traps inside the application. Authoring Tool: There are no keyboard traps inside the application. |
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply | Web: Supports Authoring Tool: Supports | Web: Browser keyboard functionality is supported. Authoring Tool: Supports. |
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
| Web: Supports Authoring Tool: Supports | Web: Quizzes and lessons can be set up to require a timed response. Authoring Tool: Content can be created that has a timed requirement to simulate exam-like conditions. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
|