Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Player: speed button's accessible name doesn't include its visible text

Open Beginner friendly
#6,021 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Dante-dan is already working on this.

Since Oct 21, 2026.

  • #6032 by @Dante-dan — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
77/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript

Research direction

Start in @hyperframes/player by locating the playback speed button and checking how its visible rate and aria-label are set and updated. Verify the accessible name contains the displayed rate as it changes, and confirm axe-core no longer reports label-content-name-mismatch for the button.

Written by the indexing model from the issue text.

Description

In @hyperframes/player (checked in 0.8.107, 0.8.181 and 0.8.183), the playback speed button shows "1x" but has aria-label="Playback speed". Because the aria-label replaces the visible text, its accessible name doesn't contain "1x". That fails WCAG 2.5.3 Label in Name, and axe-core reports it as label-content-name-mismatch (serious). A voice-control user who says "click 1x" can't press it.

Suggested fix: include the shown rate in the name and keep it updated when the rate changes, e.g. aria-label="Playback speed: 1x". Or drop the aria-label and add the words with visually hidden text.

Dominant language
TypeScript
Stars
54.1k
Forks
4.9k
Avg merge
9h 46m
Merged PRs (30d)
652

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 heygen-com/hyperframes

All issues in heygen-com/hyperframes

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.