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

Jump to bottom

In Outlook, context menu items that have the submenus are not read with NVDA KEY+UP ARROW, instead NVDA announces "blank" #3052

Closed
nvaccessAuto opened this issue Mar 6, 2013 · 3 comments
Closed

In Outlook, context menu items that have the submenus are not read with NVDA KEY+UP ARROW, instead NVDA announces "blank" #3052

nvaccessAuto opened this issue Mar 6, 2013 · 3 comments
Labels
app/microsoft-office bug close/worksforme

Comments

@nvaccessAuto
Copy link

Reported by sumandogra on 2013-03-06 12:02
Outlook 2010
The menu items of the context menu that have the submenus are not read with NVDA KEY+UP ARROW. Instead NVDA announces “blank”. One has to navigate away and come back to the menu item in order to know the menu item again. This can be observed with follow up, quick steps etc.
Steps to reproduce:

  1. In a message folder, press Applications KEY.
  2. Move with UP/DOWN ARROW in the context menu.
  3. On the menu items that have the submenu items press NVDA KEY+UP ARROW.
  4. NVDA announces “blank”. This is not observed with the menu items that do not have the submenus.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2013-03-06 22:27
Pressing NVDA+upArrow is usually more common in text controls. The more common way to query the focused control is NVDA+tab.

@ehollig
Copy link
Collaborator

ehollig commented Jul 20, 2017

Performing the steps described in #3052 (comment), pressing NVDA+Up arrow or NVDA+Tab reads the menu item as expected in Outlook 2016.

@ehollig
Copy link
Collaborator

ehollig commented Nov 8, 2017

For me, using Outlook 2016, the menu items, "follow up" and "quick steps" both report that they have a submenu. Closing this as worksforme, but if someone can reproduce this issue on Outlook 2010, we can reopen this issue.

@ehollig ehollig closed this as completed Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
app/microsoft-office bug close/worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nvaccessAuto @ehollig