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

Elements with tabindex higher than 0 are pushed to the end of the tab order #3096

Closed
nvaccessAuto opened this issue Mar 20, 2013 · 6 comments

Comments

@nvaccessAuto
Copy link

Reported by jmkenz on 2013-03-20 13:04
When NVDA is turned on, elements with tabindex values of 1,2,3, etc. are pushed to the end of the tab order, rather than the beginning. The W3C specs for tabindex say they’ll be pushed to the beginning with those tabindex values, which is certainly what happens when NVDA is de-activated. For some reason, NVDA wants to push them to the end.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2013-03-20 22:06
There are two cases here:

  1. If your browse mode cursor is already on a focusable object, pressing tab just gets passed through to the browser. In this case, it should honour the tabindex. In other words, if you press tab at least once, from then on, it should honour tabindex.
  2. If your browse mode cursor is not on a focusable object, tab searches for the next focusable object, which might not necessarily honour tabindex. This isn't ideal, but I don't know of an alternative that would work in all browsers.
    Does this explain the results you're seeing?

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2013-03-20 22:06
Also, if you switch to focus mode with NVDA+space, tabindex should always be honoured.

If this doesn't match the results you're seeing, please provide a test case with exact steps to reproduce.

@nvaccessAuto
Copy link
Author

Comment 3 by jmkenz on 2013-03-21 12:22
Thanks for your response jteh,

Here are some steps that I'm taking to reproduce the issue:

  1. Visit http://webdesign.about.com/od/examples/l/bl_aa071105.htm
  2. Go into focus mode in the Search input box - this input has no tabindex defined
  3. Press tab and focus will change to 'Search' button. Tab again and the focus will change to first menu item.
  4. Notice the text boxes labeled 'Field 1', 'Field 2', etc. Those each have tabindex defined. I'm not able to tab into those fields until I have tabbed through the entire page.
  5. Once I am in focus mode in the field with tabindex="1", the tab order for the remaining fields is honoured - it does indeed follow tabindex=1, then 2, 3, 4, rather than following the visual order of those fields. The trouble is, getting to the first field with tabindex=1 to begin with. That should happen first when I tab into the page, not last.

Thanks!

@bhavyashah
Copy link

Using Firefox 54 and NVDA 2017.2, I am getting completely different results than those provided in #3096 (comment) with http://webdesign.about.com/od/examples/l/bl_aa071105.htm. Going into focus mode on the first edit field of the page and then Tabbing lands me into advertisements, links, and what not - nothing close to what jmkenz reported. This may be due to a change in the contents of the sample URL. Thus, unless @jcsteh, @feerrenrut and others suggest otherwise or can provide updated test cases, I suggest closing. @ehollig

@Adriani90
Copy link
Collaborator

Adriani90 commented Dec 5, 2018

@jmkenzm, @jcsteh I am not sure if I can reproduce this issue. Actually when I tab away from search field NVDA says "search", then "computer science" and so on. Is this still the wrong tab order? If I am walking with down arrow in browse mode the order is the same like in focus mode which is actually the right behavior.

@ehollig
Copy link
Collaborator

ehollig commented Dec 8, 2018

CC @jmkenz
I am not able to reproduce this issue either, when performing the steps outlined in #3096 (comment)
Closing, unless this is still an issue.

@ehollig ehollig closed this as completed Dec 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants