Kaltura v2 Accessibility and Usability Information

Last evaluated in 2020

Get help

• Kaltura MediaSpace is part of the Learn@UW suite of learning technologies. For accessibility or usability assistance with Kaltura, contact learnuwsupport@wisc.edu.

• Contact the DoIT Help Desk for general technical assistance. Instructors and instructional staff can also request a consultation with a DoIT Academic Technology consultant to discuss using Kaltura MediaSpace.

• For additional support documentation, refer to the additional Kaltura Knowledgebase articles.

Accessibility and usability barriers

Limitations of Kaltura v2 player

Note: As of 2024, there are two versions of Kaltura available at UW: the original version (v2) and the new Kaltura (v7). This document describes barriers found in the original v2 version of Kaltura; there is a separate document for Kaltura v7.

Currently, only the v7 media player in Kaltura supports displaying extended audio descriptions for accessibility. The older v2 media player does not support the display of extended audio descriptions. To update to the Kaltura v7 player, please re-embed your older video content from 2024 and earlier.

Kaltura MediaSpace v2

The following are accessibility barriers that may be experienced by the end-user in Kaltura MediaSpace v2 while viewing and navigating videos.

People who are blind or low vision and navigating via screen reader may have difficulty

The following barriers exist which will impact users who are blind or low vision and are navigating via screen reader on Kaltura MediaSpace.

• Several images on the website homepage are missing any alternative text which allows screen readers to read their description.

• Some labels are missing in some form inputs, buttons, and links making it difficult to search or use these functions.

• Some heading levels are skipped or missing in the page content.

People who are colorblind or have low vision may have difficulty

Some text in MediaSpace fails color contrast accessibility which may pose a barrier to people who are colorblind or have low vision. Some labels including video descriptions, “like” counts, and “play” counts may be difficult for some users to read. 

Additionally, the active transcript widget contains some color contrast accessibility barriers including the “Hide transcript” button, which is too light and hard to read. Also, the highlight color created when the user highlights transcript text is too light to read at times.

Kaltura MediaSpace v2 (administrative experience)

The following are barriers which may be experienced by the user when uploading and managing video content.

Keyboard accessibility barriers may impact people who are blind or have motor disabilities

The “publish” button in the MediaSpace video authoring experience is not reachable via keyboard. To publish, the button can alternatively be reached by clicking on the “Actions” menu and finding “Publish” in the “Actions” dropdown via keyboard.

The “My Media” button is not reachable via keyboard. The button can alternatively be reached by navigating through the “Related Media” dropdown via keyboard.

Additionally, when the user is uploading captions, they see a pop-up appear asking for file, language, and more information about captioning appears. The user is not able to select options in the pop-up list for “language” via keyboard. Options can be alternatively selected if they manually type their options in order to get results. This required navigation is not intuitive and may not be discoverable for some users.

Kaltura Capture

The following are accessibility barriers that may be experienced by the end-user in Kaltura Capture while recording and editing videos.

People who are colorblind or low vision may have difficulty

Some users may have difficulty with the “suggest” and “suggest a new document” buttons at the bottom of the page due to low color contrast accessibility causing the labels to be hard to read.

People who are blind or low vision and navigating via screen reader may have difficulty

Some form inputs in Capture are missing the required HTML attribute which allows users navigating via a screen reader to know which fields are required.