-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Menu is not read out by NVDA #51841
Comments
@sbatten this should be fixed with the new custom menu, correct? Assinging to july for discussion |
Menu titles are read out now using the custom menubar, but I am not sure if this meets the requirement because this does not happen when the menu is launched via mnemonics. That's because the first menu item is focused and NVDA only reads its aria-label. However, pressing the alt-key focuses the menubar and allows you to navigate the menus and learn the shortcuts. In this way, I believe it meets the accessibility requirements. Awaiting more info. |
@sbatten I feel like the menu is still work in progress, thus moving this issue out to August when we can focus on the missing accessibility in the menu. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Let's reopen to give more time to the @AccessibilityTestingTeam-TCS to reply |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Here NVDA is reading only the "Menu Submenu" only but not reading it's name such as if user enter "alt+f,alt+e" then nvda is not announcing what menu get selected such as whether it is "File Menu" or "Edit Menu" etc. |
@AccessibilityTestingTeam-TCS I don't believe this was tested with the new custom menu, but this one was: #17172 and appears to be the same symptoms. My reply there holds for this issue as well. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
@sbatten While we press Alt key, NVDA reads name and shortcuts for all menu items and navigates them using arrow keys, seems this fulfills the needed requirements. |
Awesome, thanks for the feedback. Closing as resolved. |
Environment Details:
VSCode Version : 1.24.1
OS Version : Win10
Additional Details:
ScreenReader/NVDA[2018.2],JAWS[18.0.5038],MAS1.3.1
Repro Steps:
1.Launch VS Code while NVDA is ON.
2.Navigate to "Menu Bar" at top of the screen after login.
3.Using "Alt+F,Alt+E,Alt+S" these keys navigate to menu bar.
3.Observed that, NVDA is not reading selected menu name of menu bar.
Actual:
While using "Alt+F" key then keyboard focus is on the "File" menu of MenuBar.
but NVDA is not reading it's name as "File".
NVDA is reading it as "Menu SubMenu"
Same issue is observed in JAWS
Expected:
NVDA should read the name of selected Menu name.
Here, NVDA should read it like "File Menu" then "Submenu name"
instead of "Menu Submenu"
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
If NVDA is not reading the selected menu name then user will not know which menu is selected and which menu is selected from the menubar.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment For Reference:
[Accessibility]A11y_VSCode_MenuBar_ScreenReader.pptx
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: