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
Comments
Comment 1 by jteh on 2013-03-20 22:06
|
Comment 2 by jteh on 2013-03-20 22:06 If this doesn't match the results you're seeing, please provide a test case with exact steps to reproduce. |
Comment 3 by jmkenz on 2013-03-21 12:22 Here are some steps that I'm taking to reproduce the issue:
Thanks! |
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 |
@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. |
CC @jmkenz |
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.
The text was updated successfully, but these errors were encountered: