tabindex global attribute indicates that its element can be focused, and where it participates in sequential keyboard navigation (usually with the Tab key, hence the name).
The source for this interactive example is stored in a GitHub repository. If you'd like to contribute to the interactive examples project, please clone https://github.com/mdn/interactive-examples and send us a pull request.
It accepts an integer as a value, with different results depending on the integer's value:
- A negative value (usually
A negative value is useful when you have off-screen content that appears on a specific event. The user won't be able to focus any element with a negative
tabindexusing the keyboard, but a script can do so by calling the
tabindex="0"means that the element should be focusable in sequential keyboard navigation, after any positive tabindex values and its order is defined by the document's source order.
- A positive value means the element should be focusable in sequential keyboard navigation, with its order defined by the value of the number. That is,
tabindex="4"is focused before
tabindex="0", but after
tabindex="3". If multiple elements share the same positive
tabindexvalue, their order relative to each other follows their position in the document source. The maximum value for
tabindexis 32767. If not specified, it takes the default value 0.
tabindexvalues greater than 0. Doing so makes it difficult for people who rely on assistive technology to navigate and operate page content. Instead, write the document with the elements in a logical sequence.
If you set the
tabindex attribute on a
<div>, then its child content cannot be scrolled with the arrow keys unless you set
tabindex on the content, too. Check out this fiddle to understand the scrolling effects of
Avoid using the
tabindex attribute in conjunction with non-interactive content to make something intended to be interactive focusable by keyboard input. An example of this would be using a
<div> element to describe a button, instead of the
Interactive components authored using non-interactive elements are not listed in the accessibility tree. This prevents assistive technology from being able to navigate to and manipulate those components. The content should be semantically described using interactive elements (
<textarea>, etc.) instead. These elements have built-in roles and states that communicate status to the accessibility that would otherwise have to be managed by ARIA.
BCD tables only load in the browser
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, check out https://github.com/mdn/browser-compat-data and send us a pull request.