-
-
Notifications
You must be signed in to change notification settings - Fork 653
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
MS Teams: [Calendar grid]: Unable to navigate to the meeting grids/scheduled meetings in browse mode #10529
Comments
Could you reproduce this in MS Teams on the web? Also, what makes you think that this is an issue in NVDA? |
Same is reproducible on Chrome. This issue does not reproduce on Win32+JAWS, Chrome+JAWS, Mac+VoiceOver. |
This is not gonna work unless you also give the grid a role="document" or so. Giving a role="document" additionally to role="application" tells the screen reader to interpret the desktop like content of role="application" as a web document. After that NVDA can handle the grid in browse mode as well. However, in case JAWS and other screen readers can build the virtual document without the need of role="document", then it should be discussed if NVDA needs to adapt to that behavior or not. |
@HarishTerala are you still having this issue with NVDA 2024.4 and the new MS Teams, or while using the browsers last version? |
Steps to reproduce:
Actual behavior:
If role="application" is defined to the grids then user is unable to navigate to the meeting grids/scheduled meetings in browse mode using down/up arrow keys.
Expected behavior:
User should be able to navigate to the meeting grids/scheduled meetings in browse mode using down/up arrow keys.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2019.2.1
Windows version:
Win10 1903
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?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
The text was updated successfully, but these errors were encountered: