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

Outlook 2010 Calendar: Tab Only Reads First Appointment Automatically In Month View #3366

Closed
nvaccessAuto opened this issue Jul 16, 2013 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by jhomme on 2013-07-16 12:36
To reproduce, do the following.

Open Outlook 2010.

Press Control + 2 to go to the calendar.

Make sure that you have more than one appointment for the current day.

Press Alt + Control + 4 to go to Month view.

Note, you may need to go out of and back into the calendar, or out of and back into Outlook, just as long as you shift focus away from and then back to the calendar.

Press Tab. NVDA reads the first appointment for the day.

Press Tab again. NVDA doesn't read the next one.

From here on in, whether you press Tab or Shift + Tab, NVDA does not read appointments. You have to use NVDA + Tab to read the appointment you are on.

Expected behavior: NVDA would read each appointment.

@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2014-05-30 02:36
Hi,
Try the latest next snapshot to see if this problem is fixed.

@LeonarddeR
Copy link
Collaborator

cc @jhomme: Can you still reproduce this?

@Adriani90
Copy link
Collaborator

@jhomme could you please thest if you can reproduce it?
I will try to test this tomorrow.

@Adriani90
Copy link
Collaborator

@LeonarddeR I cannot reproduce this particular issue in Outlook 2010 in month view on Windows 8.1 with NVDA 2017.3. However, in month view it seems that not all appointments are included in the tab order. some appointments are ignored. I don't know exactly on what Parameters the tab order on month view is based. All other views (day and week view) work properly. But the tab order is another issue.
So I suggest closing this one. We can reopen it if someone can reproduce it.

@ehollig
Copy link
Collaborator

ehollig commented Dec 8, 2018

Thank you @Adriani90 for testing. Closing

@ehollig ehollig closed this as completed Dec 8, 2018
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

4 participants