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

Word table selection keys aren't read #5961

Closed
Qchristensen opened this Issue May 18, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@Qchristensen

Qchristensen commented May 18, 2016

Aside from NVDA's table navigation keys (control+alt+arrows), Word includes some of its own:

alt+home (move to first cell in row)
alt+end (move to first last in row)
alt+page up (move to first cell in column)
alt+page down (move to last cell in column)

Plus, add SHIFT to select (eg alt+home then alt+shift+end to select current row)

also alt+shift+up to select the row above and alt+shift+down arrow to select the row below (I probably wouldn't recommend these as if you are already in the top or bottom row they actually separate that row from the rest of the table - which is arguably even more important to know when you've done it).

Pressing any of these keys results in the cursor moving as expected, but NVDA does not announce anything.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto commented May 24, 2016

Incubated in dd7013c.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto commented May 24, 2016

Incubated in 8af1ac0.

@michaelDCurran

This comment has been minimized.

Show comment
Hide comment
@michaelDCurran

michaelDCurran May 24, 2016

Contributor

Due to a deficiency in the MS Word object model, alt+shift+pageUp and alt+shift+pageDown will read more text than they should when reading the selection. I.e. If selecting down the middle column of a 3 column table, it will also include row 1 column 3, row 2 column 1, row 2 column 3 and row 3 column 1, as the MS Word object model cannot give back noncontiguous ranges. In the long-term we may consider some kind of special selection reading code for MS Word tables, but as this affects not just these particular commands, we should worry about it in another issue.

Contributor

michaelDCurran commented May 24, 2016

Due to a deficiency in the MS Word object model, alt+shift+pageUp and alt+shift+pageDown will read more text than they should when reading the selection. I.e. If selecting down the middle column of a 3 column table, it will also include row 1 column 3, row 2 column 1, row 2 column 3 and row 3 column 1, as the MS Word object model cannot give back noncontiguous ranges. In the long-term we may consider some kind of special selection reading code for MS Word tables, but as this affects not just these particular commands, we should worry about it in another issue.

@jcsteh jcsteh closed this in 6658ca9 Jun 24, 2016

@jcsteh jcsteh added this to the 2016.3 milestone Jun 24, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment