You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by csm120 on 2015-10-01 23:32
I've seen this behavior in Excel 2010, 2013, and 2016.
In Excel make 3 columns from a1 to c3.
Type data starting in a3.
Use NVDA+Shift+c on a1.
Reading of columns is spotty or not happening unless you delete the blank row at a2.
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:
Comment 1 by jteh on 2015-10-02 09:16
This is because Excel defines a blank row or column to indicate a new region. In order to facilitate headers for different regions, NVDA honours this and only reports headers within the region.
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
The region support is useful in some situations. We might "extend" the search for headers to regions left/above of the current region if the current region doesn't define headers? This might be what users expect and still allows for per region headers. That being said, this is just from a functional perspective and I don't know if there are any technical issues preventing this.
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:
If one defines two sets of headers, the first set will be read as the headers when moving over the second set of headers. For example, if a1 and c1 are set as column headers, a1 will be read as a header when moving from c2 to c1. We shouldn't search for a header in the same axis for a cell which is a header in that axis itself.