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

Rules not read when navigating "Rules and Alerts" dialog in Outlook 2016 #8597

Closed
Qchristensen opened this issue Aug 6, 2018 · 3 comments
Closed

Comments

@Qchristensen
Copy link
Member

  1. In Outlook, open the Rules and Alerts window: ALT+H, R, R, L
  2. Tab to the list of rules (is there a hotkey for that?)
  3. Arrow through the list.

Expected behaviour, the screen reader should read the name of each rule (and whether it is active, and actions etc) as the focus moves.
Actual behaviour, nothing is read.

Press NVDA+up arrow (NVDA+L in Laptop layout) to read the current line, and it reads the first rule, no matter what rule actually currently has focus. It DOES read the correct information about the active state and actions (for the first rule).

If I alt+tab out of the window and back, and then read the current line, it reads the rule that has focus (If I use the arrow keys to select a different rule and then read the current line, NVDA still reports the rule that was focussed when I alt+tabbed.

This is using the current version of Outlook 2016 / 365: 1807 build 10325.20082 Click to run, on the latest Windows fast insider 1803, build 17730.1000 and NVDA Version: alpha-15781,d58e1cd4

The behaviour is the same when using NVDA 2018.2.1.

Narrator also can't read the individual rules in the dialog, which leads me to believe it's likely an Outlook issue?

Steps to reproduce:

Actual behavior:

Expected behavior:

System configuration:

NVDA Installed/portable/running from source:

NVDA version:

Windows version:

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions:

Does the issue still occur after restarting your PC?

Have you tried any other versions of NVDA?

@Brian1Gaff
Copy link

Brian1Gaff commented Aug 6, 2018 via email

@Qchristensen
Copy link
Member Author

Just testing this issue in the current version of Office 365 (16.0.11001.20093) - This now works (tested with NVDA 2018.4beta 2 and also with 2018.2.1 since that was what I reported the error with).

While this is presumably a change Microsoft have made in Office 365, can anyone please confirm whether this is still an issue in the latest version of Office 2016 (or any other Office version) or whether this issue can be closed?

@ehollig
Copy link
Collaborator

ehollig commented Nov 29, 2018

This now correctly works for me in Outlook 2016. Closing as worksforme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants