[Accessibility] Configure embedded video player to generate spoken output from captions

Open
  • Is something wrong?
#6,460 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
accessibility, frontend

Research direction

Start by locating the embedded video player and how DSpace loads uploaded MP4 and VTT files; the issue does not name relevant files, tests, or a player entry point. Review the cited accessibility criterion and compare the current player with Able Player. Done means users can access captions with screen readers and enable spoken caption output, verified with an MP4, VTT transcript, and a screen reader.

Written by the indexing model from the issue text.

Description

accessibility bug component: viewer help wanted

Describe the bug

According to 301 559, Section 7.1.5: Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

The embedded video player in DSpace currently does not allow users to generate or provide spoken output of the available captions. The video player also doesn't allow screen readers to access captions or caption files.

To Reproduce

Upload a video file (mp4) and a transcript file (.vtt) to DSpace and play them. Test with screen reader, such as through the Silktide plugin.

Expected behavior

The video player should allow users to generate spoken output of available captions. Ideally, deliver the audio file with spoken subtitles in a separate audio track and allow for mixing in the end user's device. See also Notes 1-4 for this criterion (https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf).

Consider switching to a more accessibility-friendly player, such as the Able player.

Dominant language
TypeScript
Stars
180
Forks
577
Avg merge
1d 23h
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DSpace/dspace-angular

All issues in DSpace/dspace-angular

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.