musescore / musescore/MuseScore

Timeline not accessible

Open
#28,351 0 comments 1 reaction 2 assignees View on GitHub

@jessjwilliamson is already working on this.

Since Jun 13, 2025.

accessibility needs design
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Accessibility issue (e.g. for keyboard-only or screen reader users)

Description with steps to reproduce

The timeline is not accessible by keybaord - there is no way (that I can find) to navigate into it. You can get the focus to the title bar and the "..." menu but not into the content area.

Supporting files, videos and screenshots

Image

It also doesn't display well on my system using xcb - presumably an artifact of the high DPI scaling - but ignore that. I'll hope it is improved with wayland and/or Qt 6.9

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-251620322, revision: github-musescore-musescore-4870d00

Regression

No.

Operating system

Debian 12, Windows 11

Additional context

The timeline could potentially be especially useful for blind users for getting a quick overivew of the score that would otherwise require a visual scan, as well as doing things like jumping from one rehearsal to the next, etc.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.