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

Hidden skip link is itself skipped when NVDA is running #5230

Closed
nvaccessAuto opened this issue Jul 17, 2015 · 4 comments
Closed

Hidden skip link is itself skipped when NVDA is running #5230

nvaccessAuto opened this issue Jul 17, 2015 · 4 comments
Labels
bug close/duplicate

Comments

@nvaccessAuto
Copy link

Reported by hhillen on 2015-07-17 09:04
Scenario:

Using the following test case (also attached)

A skip link is the first tab stop on the page. It is hidden visually using Bootstrap's sr-only class (which uses clipping to hide the element), so the link is still perceivable by AT, focusable, and part of the tab order, A CSS :focus pseudo selector is used to make the link become visible when it receives focus, i.e. when a keyboard user tabs to it.

Problem:
In Firefox, When NVDA is running in browse mode, NVDA will skip over the link when tabbing through the page. NVDA does correctly focus the link when shift tabbing. The issue only occurs in with the Firefox/NVDA combination, and only in browse mode.
@nvaccessAuto
Copy link
Author

Attachment hidden_skiplink.html added by hhillen on 2015-07-17 09:04
Description:

@nvaccessAuto
Copy link
Author

Comment 1 by hhillen on 2015-07-17 09:06
The issue only happens if the hidden link is the first tab stop on the page. The test case contains a second hidden link following the "tab stop 1" link, and NVDA correctly focuses that one.

@jcsteh jcsteh removed the Untriaged label Nov 13, 2015
@hidanielle hidanielle mentioned this issue Sep 7, 2016
Open
@jcsteh
Copy link
Contributor

jcsteh commented Sep 7, 2016

On a newly loaded page, the browse mode cursor is placed at the top of the page. The link is at the top of the page. Thus, the browse mode cursor is right on the link. Tabbing therefore moves to the next link because the user is already on the first link. If we changed this, the user would never be able to move past a link the cursor is placed within.

@jcsteh
Copy link
Contributor

jcsteh commented Sep 7, 2016

Note that while it makes sense that tab doesn't focus the first link as explained above, the first link should get focus when browse mode is initialised because the cursor lands on the link. That's covered by #3575.

@jcsteh jcsteh closed this as completed Sep 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jcsteh @nvaccessAuto