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

NVDA Stops Reading File Menu's Items After Navigating to Sibling Menus #22883

Open
NinjaNas opened this issue May 17, 2024 · 3 comments
Open
Assignees
Labels
accessibility Issues related to accessibility

Comments

@NinjaNas
Copy link
Contributor

NinjaNas commented May 17, 2024

Issue type

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

Bug description

When using keyboard navigation, NVDA will stop reading menu items after moving to a new file menu.

Steps to reproduce

  1. Alt + F
  2. See that NVDA works
  3. Hit Left Arrow to close the menu
  4. Note that it suddenly says blank when trying to read the file menu
  5. Hit Right Arrow and see that it suddenly is able to read the file menu again
  6. Hit Down Arrow and see that all of the menu items read blank
  7. This now affects all other file menus until focus is lost on the file menu and Alt + F is used again

Screenshots/Screen recordings

2024-05-17.13-45-30.mp4

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.0-241231433, revision: github-musescore-musescore-5f36e74

Regression

I don't know

Operating system

Windows 10

Additional context

Relevant files may include:
src/framework/ui/internal/navigationcontroller.cpp
src/appshell/view/navigableappmenumodel.cpp

src/appshell/qml/platform/AppMenuBar.qml
src/framework/uicomponents/qml/Muse/UiComponents/StyledMenuLoader.qml
src/framework/uicomponents/qml/Muse/UiComponents/internal/StyledMenu.qml

Additional Info:
#20191 (comment)

@muse-bot muse-bot added the accessibility Issues related to accessibility label May 17, 2024
@bkunda bkunda added the needs info More information is required before action can be taken label May 21, 2024
@bkunda
Copy link

bkunda commented May 21, 2024

@zacjansheski please check regression status and whether other parts of the app are similarly affected. Thanks!

@oktophonie
Copy link
Contributor

See also #20732

@zacjansheski
Copy link
Contributor

Not an issue with Narrator or VoiceOver

@zacjansheski zacjansheski removed the needs info More information is required before action can be taken label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility
Projects
Status: One of the next releases
Development

No branches or pull requests

6 participants