-
-
Notifications
You must be signed in to change notification settings - Fork 623
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
NVDA not reading all columns in grid #16496
Comments
Just to add. This happens for me 80% of the time on my work and home PC. It doesn't happen for Telerik at all |
I can reproduce this only when reporting of tables is enabled in document formating settings.
This error appears on every column that cannot be read by NVDA, this seem to be the first two columns. cc: @jcsteh any suggestions? |
I tested in Chrome 124 with NVDA 2024.1. |
Steps to reproduce:
Navigate to https://runner.telerik.io/fullscreen/@anthony2001/OfOkadiY
Click on a cell and use the arrow keys to move around
Actual behavior:
NVDA reads out the 3rd->nth columns but not the first or second
Expected behavior:
It should read all columns
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
2024.1.0.31547
Windows version:
Windows 11
Name and version of other software in use when reproducing the issue:
Latest version of Chrome and Edge have the behaviour
Firefox doesn't
An old version of Chromium doesn't show the behaviour either. This is version 102.0.5002.0
This is using the Telerik grid software. They say they can't reproduce the issue, which may be because of the version of Chrome they are using
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
I don't have any
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The text was updated successfully, but these errors were encountered: