Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Letter Navigation not working on Trees & Lists #19930

Closed
jmwmusic opened this issue Nov 4, 2023 · 2 comments
Closed

Initial Letter Navigation not working on Trees & Lists #19930

jmwmusic opened this issue Nov 4, 2023 · 2 comments
Assignees
Labels
accessibility Issues related to accessibility UI Visual issues affecting the UI (not notation)

Comments

@jmwmusic
Copy link

jmwmusic commented Nov 4, 2023

Issue type

UI bug

Bug description

It is usual for keyboard navigation with a screen reader to be able to quickly jump to specific items in a list by typing the first letter/s of item. This isn't working.

Steps to reproduce

  1. From the File menu choose New or press Ctrl+N.
    The New Score wizard appears.

  2. Press Tab to move to the Category list (General, Choral, Chamber, Solo, ...)

  3. Press initial letter(s) of a category.

Expected behaviour, the focus should move to corresponding item in the list. e.g. pressing S should move to "Solo". or typing CHA should select Chamber.

Actual behaviour: no response. Focus remains stationary.

Another example would be selecting a palette by first letters.

Screenshots/Screen recordings

No response

MuseScore Version

4.1

Regression

I don't know

Operating system

Windows 10 with NVDA

Additional context

No response

@muse-bot muse-bot added the UI Visual issues affecting the UI (not notation) label Nov 4, 2023
@cbjeukendrup cbjeukendrup added the accessibility Issues related to accessibility label Nov 4, 2023
@cbjeukendrup
Copy link
Contributor

Duplicate of #16508

@cbjeukendrup cbjeukendrup marked this as a duplicate of #16508 Nov 4, 2023
@cbjeukendrup cbjeukendrup closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2023
@MarcSabatella
Copy link
Contributor

FWIW, I'm not sure the palette would be covered by the other issue - might or might not be, depending on how it's implemented. Could be worth updating the other issue to clarify that palettes should be included, or repurpose this issue for the palettes if it seems separate.

BTW, @jmwmusic - don't forget about the palette search facility. It already greatly simplifies finding palette elements, even basically working the same way - typing first few letters of palette item name, then navigating with cursor from there. So for example, you can get to "Swing" in only a handful of keystrokes (type "sw", tab to reach the first result which is the tempo palette, right to reach the expand button, down to enter the palette).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility UI Visual issues affecting the UI (not notation)
Projects
None yet
Development

No branches or pull requests

5 participants