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
When NVDA is set to read columns in Excel columns aren't read if there is separation between column headers and data. #5396
Comments
Attachment NVDA Columns.xlsx added by csm120 on 2015-10-01 23:33 |
Comment 1 by jteh on 2015-10-02 09:16 That said, this seems to be causing a lot of confusion and I wonder whether we need to drop the region support. The reality is that regardless of whether Excel defines these as new regions, users (rightly or wrongly) don't seem to care. |
Comment 2 by bramd on 2015-10-26 22:34 |
This was incubated months ago in b283199, but the automated script didn't catch it for some reason. There are a couple of additional things that are needed for this:
|
Incubated in c7ec64c. |
Incubated in 6637f7f. |
Reported by csm120 on 2015-10-01 23:32
I've seen this behavior in Excel 2010, 2013, and 2016.
Steps:
I have tried this with NVDA 2015.3, and with latest snaps.
I need the columns to be read even if there is separation between the column headers and the data. I'm attaching a file.
The text was updated successfully, but these errors were encountered: