This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Canvas' conformance with the accessibility standards under Section 508 of the Rehabilitation Act and WCAG 2.1 AA.
Accessibility Statement
Instructure is committed to ensuring its products are inclusive and meet the diverse accessibility needs of our users. Canvas Student and Canvas Teacher mobile applications strive for WCAG 2.1 Level A/AA and Section 508 conformance. Regular testing (both internal and by a third party) is conducted to identify conformance issues, with processes in place for timely remediation of accessibility issues that are identified. Canvas mobile applications are a complex and broad system. The statements below are accurate as of the date indicated.
Canvas Teacher and Student mobile applications on both iOS and Android have been evaluated by Instructure and WebAIM according to WCAG 2.1 standards. Testing is regularly conducted using automated tools, assistive technology (such as screen readers, switches, etc.), and coding best practices. Third party accessibility evaluation occurs regularly with internal audits conducted with each release. Mechanisms are in place for logging and fixing accessibility defects.
Third Party Conformance Statement
WebAIM, an independent authority in web accessibility, has evaluated the Canvas Student and Canvas Teacher Mobile Applications on both iOS and Android platforms and certifies them to be substantially conformant with Level A and Level AA of the Web Content Accessibility Guidelines version 2.1. While not fully conformant, conformance issues that pose a significant barrier for users with disabilities have been addressed in the sample evaluated.
A sample of the frequently used aspects of Canvas’ Teacher and Student Mobile Applications were evaluated in both Student and Instructor roles. This sample includes but was not limited to general navigation, course content, grading, communication, and administration. Visual annotations, as viewable in Canvas Student and editable in Canvas Teacher, are excluded from this conformance statement based on accessibility limitations in the underlying technology.
WebAIM cannot verify the conformance of content outside the scope of the representative sample, or content changed after October 30, 2023. However, based on our interactions with Instructure, WebAIM is confident in its ability and willingness to maintain a substantially conformant LMS.
Canvas Student and Canvas Teacher Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Name of Product: Canvas Student and Canvas Teacher mobile applications
Date: November 2023
Product Description: Mobile applications on both Android and iOS platforms
Contact Information: accessibility@instructure.com
Evaluation Methods Used: Manual and automated testing by Instructure and by WebAIM with supported screen readers and other accessibility technologies.
Applicable Standards/Guidelines: This report covers the degree of conformance for the following accessibility standard/guidelines:
- Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017
- Web Content Accessibility Guidelines 2.1 (Level A/AA)
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.1 Report
This table documents conformance of the Canvas LMS (including web content, electronic documents, software components, and authoring systems) with WCAG 2.1
Table 1: Success Criteria, Level A/AA
Notes: Make sure to have last uploaded date
|
Criteria |
Supports |
Remarks and Explanations |
|
1.1.1 Non-text Content(Level A) |
Partially Supports |
Most non-text content has appropriate text alternatives. Some fields use placeholder text instead of visual labels. An exception also exists with document annotations in the apps. |
|
Not Applicable |
The apps do not contain audio-only or video-only content by default. Users are responsible for accessibility of content they upload. The apps support captions and transcripts, but currently captions must be provided via the Canvas web interface. |
|
|
1.2.2 Captions (Prerecorded) (Level A) |
Not Applicable |
The apps do not contain audio or video by default. Users are responsible for the accessibility of content they upload. The apps support displaying captions, but currently captions must be provided via the Canvas web interface. An exception currently exists affecting some captions. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Not Applicable |
The apps do not contain audio or video by default. Users are responsible for the accessibility of content they upload. |
|
1.2.4 Captions (Live) (Level AA) |
Not Applicable |
The apps do not contain live audio and video functionality. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) |
Not Applicable |
The apps do not contain prerecorded video. Users are responsible for the accessibility of content they upload. |
|
1.3.1 Info and Relationships (Level A) |
Partially Supports |
Most information, structure, and relationships can be programmatically determined or are available in text. Some fields use placeholder text instead of visual labels. |
|
1.3.2 Meaningful Sequence (Level A) |
Supports |
The apps maintain consistent structures allowing correct reading sequences to be programmatically determined. |
|
1.3.3 Sensory Characteristics (Level A) |
Supports |
Instructions do not rely on shape, size, visual location, or sound. |
|
1.3.4 Orientation (Level AA 2.1 only) |
Supports |
Orientation is not restricted to only portrait or landscape. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) |
Supports |
Input field purposes can be programmatically determined. |
|
1.4.1 Use of Color (Level A) |
Supports |
The apps do not convey information by color alone. |
|
1.4.2 Audio Control (Level A) |
Supports |
Prerecorded audio is not provided, and user generated content does not auto-play. |
|
1.4.3 Contrast (Minimum) (Level AA) |
Supports |
The apps provide a minimum of 4.5:1 contrast ratio by default. |
|
1.4.4 Resize text (Level AA) |
Supports |
Text can be resized or zoomed without loss of content or functionality. |
|
1.4.5 Images of Text (Level AA) |
Supports |
Images of text are not provided by default. |
|
1.4.10 Reflow (Level AA 2.1 only) |
Supports |
This criteria applies primarily to web content. The apps support standard mobile OS display sizing settings. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only) |
Supports |
Graphical objects and user interface elements meet or exceed minimum 3:1 contrast. |
|
1.4.12 Text Spacing (Level AA 2.1 only) |
N/A |
Text spacing settings are not applicable to mobile apps in the same manner as web content. |
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) |
Supports |
No additional content is triggered by focusing elements. |
|
2.1.1 Keyboard (Level A) |
Partially Supports |
Navigation is possible with external keyboard, switch control, and screen reader gestures. Exceptions currently exist when annotating an assignment submission through the Teacher app. |
|
2.1.2 No Keyboard Trap (Level A) |
Supports |
Navigation is not trapped when using an external keyboard, switch control, or screen reader. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) |
N/A |
Keyboard shortcuts are not applicable to the apps. |
|
2.2.1 Timing Adjustable (Level A) |
Supports |
Interface elements are not timed out by default. Where time limits are user definable for content like quizzes, the time limits can be modified for specific users via the Canvas web interface. |
|
2.2.2 Pause, Stop, Hide (Level A) |
Supports |
The apps do not contain moving, blinking, scrolling, or auto-updating content. |
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports |
The apps do not contain any blinking content. |
|
2.4.1 Bypass Blocks (Level A) |
Supports |
Navigation elements are not visible by default, and thus do not need to be regularly bypassed. |
|
2.4.2 Page Titled (Level A) |
N/A |
Page titles are not applicable to the apps. |
|
2.4.3 Focus Order (Level A) |
Supports |
The navigation order is logical and intuitive. |
|
2.4.4 Link Purpose (In Context) (Level A) |
Supports |
The purpose of each link is clearly identified by its text. |
|
2.4.5 Multiple Ways (Level AA) |
Supports |
Pages can be navigated in multiple ways, following consistent layouts in global and page navigation. |
|
2.4.6 Headings and Labels (Level AA) |
Partially Supports |
Content has proper heading structures and/or page regions. Some form elements do not have visual labels but have placeholder text. |
|
2.4.7 Focus Visible (Level AA) |
Supports |
Focus is consistently visible throughout the apps. |
|
2.5.1 Pointer Gestures (Level A 2.1 only) |
Supports |
The apps do not require navigation by multipoint or path-based gestures. |
|
2.5.2 Pointer Cancellation (Level A 2.1 only) |
Supports |
No actions in the apps execute on finger-down, and thus can be aborted by moving the finger away from the target before finger-up. |
|
2.5.3 Label in Name (Level A 2.1 only) |
Partially Supports |
Visible and accessible labels match, and any controls that use icons or symbols are given consistent accessible labels. Some form elements do not have visual labels but have placeholder text; these form elements do have accessible labels. |
|
2.5.4 Motion Actuation (Level A 2.1 only) |
Supports |
The apps do not contain any motion operations. |
|
3.1.1 Language of Page (Level A) |
Supports |
Mobile operating systems can programmatically determine the language used by the app, which can be configured through the Canvas web interface. |
|
3.1.2 Language of Parts (Level AA) |
N/A |
Multi-language content is not provided by the apps. Users are responsible for accessibility of content they upload, and user-generated content can be supplemented with appropriate HTML language tags. |
|
3.2.1 On Focus (Level A) |
Supports |
When an element receives focus, it doesn’t result in a substantial change to the page or an unexpected change of focus. |
|
3.2.2 On Input (Level A) |
Supports |
Modifying input fields in the apps do not automatically initiate any action or navigation. |
|
3.2.3 Consistent Navigation (Level AA) |
Supports |
The apps contain consistent navigation patterns across all pages and content. |
|
3.2.4 Consistent Identification (Level AA) |
Supports |
App components behave consistently across the application. |
|
3.3.1 Error Identification (Level A) |
Supports |
Forms in the apps are validated and errors are properly identified and described to the user. |
|
3.3.2 Labels or Instructions (Level A) |
Partially Supports |
Most content requiring user input contains appropriate labels. Exceptions currently exist when creating a calendar event or creating a new inbox message where placeholder text is used. |
|
3.3.3 Error Suggestion (Level AA) |
Supports |
When errors are encountered in the apps, an announcement is made including suggestions for correcting the error. |
|
Supports |
If a user can change or delete legal, financial, or test data, the changes or deletions can be reversed, verified, or confirmed. |
|
|
4.1.1 Parsing (Level A) |
Supports |
The apps are constructed to proper standards. |
|
4.1.2 Name, Role, Value (Level A) |
Supports |
Best practices are followed for UI components to enable assistive technologies. |
|
4.1.3 Status Messages (Level AA 2.1 only) |
Supports |
Updates to content, status changes, and notifications that display visually have corresponding audio announcements for screen readers. |
Section 508 Functional Performance Criteria (FPC)
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
Without Vision |
Supports |
The apps have been optimized to work well with screen readers such as Talkback and VoiceOver. |
|
With Limited Vision |
Supports |
The apps support mobile OS accessibility display settings, such as magnification and text sizing. |
|
Without Perception of Color |
Supports |
The apps do not convey information by color alone. |
|
Without Hearing |
Supports |
The apps do not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content. |
|
With Limited Hearing |
Supports |
The apps do not use any audio for its default operation. Users can upload their own content and are responsible for ensuring the accessibility of the uploaded content. |
|
Without Speech |
Not Applicable |
The apps do not require speech for operation. |
|
With Limited Manipulation |
Supports |
The apps do not require fine motor control or simultaneous actions. They are accessible via alternate input methods such as switch controls. |
|
With Limited Reach and Strength |
Supports |
The apps do not require fine motor control or simultaneous actions. They are accessible via alternate input methods such as switch controls. |
|
With Limited Language, Cognitive, and Learning Abilities |
Supports |
The apps support adaptation of content by end users and provide an easy-to-use interface for users with cognitive or learning disabilities. |