Fri 20 May 2011
I am a minimalist. I believe that simple solutions are better. So, when it comes to tabindex, I rarely invite “him” to the accessibility party. Why? Because if you will just write the source code in the same order you need the items for the visual presentation, then tabindex is not necessary. But there are two decent reasons for using tabindex.
- tabindex = “0” to add something that is not a link or a form field to the tab order.
When you specify the tab index on visible elements, remember the following:
- Elements with tabIndex=0 are ordered based on the source
- Any element with tabIndex>0 appears before all elements with tabIndex=0
- Any elements with the same tabIndex are ordered based on the source order