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

Header row issue in complex tables designed in word. #5926

Closed
derekriemer opened this Issue May 6, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@derekriemer
Collaborator

derekriemer commented May 6, 2016

Download this document and open it. Disable protected mode for good measure and consistency. Now go to row 1 col one.
Press NVDA+shift+r to enable row headers.
Go to row 3.
Come back up to row 2, but on column 2 or 3.
Error sound plays.
Now repeat the same procedure. Disable row headers first.
There is also a browse mode issue with NVDA, I'm going to explain that in a separate ticket.

Table overview:

This table has a complex layout. column one has a merged vertical cell, as if a1-a2 were merged. a2-a3 are merged. a4-a5 are merged. a6-7 is like a1-2.
Row two has two sub-headers for what b-e have.
If you need a more real world example, I can send privately a lab from ebio that I don't want to post publicly so I don't share answers with students of future classes who are too resourceful for their own good.

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh
Contributor

jcsteh commented May 25, 2016

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto commented May 25, 2016

Incubated in 74785a3.

@derekriemer

This comment has been minimized.

Show comment
Hide comment
@derekriemer

derekriemer May 27, 2016

Collaborator

Closing 5563 since this fixed rows as well.

Collaborator

derekriemer commented May 27, 2016

Closing 5563 since this fixed rows as well.

@nvaccessAuto nvaccessAuto removed the incubating label Jul 8, 2016

@jcsteh jcsteh added this to the 2016.3 milestone Aug 5, 2016

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