Kaltura v7 Accessibility and Usability Information
Get help
-
Contact the DoIT Help Desk for general assistance. Reach the Help Desk by phone at 608.264.4357, email at help@doit.wisc.edu or visit their KnowledgeBase.
-
For accessibility or usability assistance for Kaltura, please contact learnuwsupport@wisc.edu.
Additional resources
-
Kaltura Overview, UW-Madison (KnowledgeBase document)
Accessibility and usability barriers
Note: As of 2024, Learn@UW supports the latest version of Kaltura, called v7. This accessibility KB document is for v7. The older version is still available on campus, and still has its own accessibility KB document.
The following information is provided to help people with disabilities know what potential barriers may exist and to help people who support them. This is not a comprehensive list of barriers. Our team evaluates common user flows, looking for patterns of barriers. We do not evaluate the entire application.
Keyboard navigation color contrast barriers may limit access for people with motor disabilities and people with low vision.
Some keyboard focus indicators are missing a top, bottom, left, or right side. Some keyboard focus indicators do not have strong contrast, which makes it difficult to follow the keyboard navigation. See Figure 1.
Figure 1 caption: The dark blue keyboard focus around the black playlist background does not meet color contrast standards.
Unexpected keyboard navigation might create barriers for some users.
Keyboard navigation requires some unexpected interactions, such as accessing volume controls, where a keyboard-user tabs to a button labeled mute (which is different conceptually). See Figure 2.
Figure 2
Magnification and reflow barriers exist, creating barriers for people with low vision.
At 300% and higher magnification, the controls for the video player are not visible, when it is embedded in Canvas. Additionally, part of the screen is cut off. See Figure 3.
Figure 3
Screen reader barriers might limit access for some users who are blind or who otherwise use assistive technology to navigate.
When a screen reader first enters the web area for any of the frames (playlist, dual video, and quiz each had their own frame in the test environment) the focus would land on the play button, but the screen reader wouldn’t announce the play button until a user navigates away and then back to the button.