Skip to content
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

Jump to bottom

NVDA doesn't bypass virtual navigation for read-only ARIA grids #5118

Closed
nvaccessAuto opened this issue May 29, 2015 · 7 comments
Closed

NVDA doesn't bypass virtual navigation for read-only ARIA grids #5118

nvaccessAuto opened this issue May 29, 2015 · 7 comments
Labels
bug
Milestone
2015.4

Comments

@nvaccessAuto
Copy link

Reported by kloots on 2015-05-29 06:51
When an item in an ARIA grid receives focus the virtual navigation should be toggled off. In NVDA this is true for editable ARIA grids. However, if the grid has been marked as read only via aria-readonly=true then the virtual navigation remains on.

I raise this as an issue as for twitter.com we're rebuilding the timeline and we're going to express it as a single-column, read-only ARIA grid. The goal is to use this ARIA widget role in the interest of allowing the shortcuts for navigating the timeline (j & k) to automatically pass through once the timeline receives focus. This approach works great in JAWS, but not NVDA. I have attached an example.
@nvaccessAuto
Copy link
Author

Attachment test.html added by kloots on 2015-05-29 06:51
Description:
Repro example.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2015-06-06 05:18
It does seem we're not complying with the spec here. Contrary to my understanding, the spec is very clear about grids being always interactive, even when read-only.
Changes:
Milestone changed from None to 2015.3

@nvaccessAuto
Copy link
Author

Comment 2 by kloots on 2015-06-07 00:47
You mean NVDA "doesn't comply with the spec," right? Just want to make sure we are on the same page.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh (in reply to comment 2) on 2015-06-07 01:00
Replying to kloots:

You mean NVDA "doesn't comply with the spec," right?

Yes. How we're going to do this correctly is an open question which may require discussion with browser vendors, but one way or another, NVDA's current behaviour doesn't comply with the spec.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2015-08-14 05:18
Changes:
Milestone changed from 2015.3 to 2015.4

@nvaccessAuto
Copy link
Author

Comment 5 by Michael Curran <mick@... on 2015-09-21 05:40
In commit ccffc1f:
Merge branch 't5118' into next. Incubates #5118
Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

Comment 6 by Michael Curran <mick@... on 2015-10-06 05:26
In commit 5065469:
Merge branch 't5118'. Fixes #5118
Changes:
Removed labels: incubating
State: closed

@nvaccessAuto nvaccessAuto added this to the 2015.4 milestone Nov 10, 2015
michaelDCurran added a commit that referenced this issue Nov 23, 2015
@michaelDCurran
Merge branch 't5118'. Fixes #5118
5065469
@jcsteh jcsteh marked this as a duplicate of #3743 Jul 19, 2017
@jcsteh jcsteh mentioned this issue Jul 19, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2015.4
Development

No branches or pull requests
1 participant
@nvaccessAuto