Using a tabindex of -1 is (in my books) a fairly old trick to try and drop elements out of an existing tabindex order. But I suspect it’s a trick may have outlived its usefulness and may behave inconsistently across different user agents.What are your thoughts/experiences? Do we have more consistent best practice techniques that we can use instead?
Updates from July, 2012 Toggle Comment Threads | Keyboard Shortcuts
@esmi the tabindex attributes are still needed on the toolbar as the HTML for it is outputted at the bottom but it’s shown at the top of the screen. All other tabindex have been removed making “tabbing” flow much better.
There are several new accessibility tickets on trac dealing with the use of “tabindex” and other accessibility enhancements. A few are already committed. It would be good if these can be tested and any substandard/improper behavior fixed while still early in the development cycle for 3.5.