> For the complete documentation index, see [llms.txt](https://ebay.gitbook.io/mindpatterns/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ebay.gitbook.io/mindpatterns/antipatterns/tabindexitis.md).

# Tabindex-itis

Do not apply the `tabindex` attribute to *static* text or graphical elements. Doing so will create an unnecessary tabstop for keyboard users.

A common mis-conception amongst developers is that screenreader users will not be able to access and read an element if it is not "tab-able". However, using their own special commands, screen readers *can* focus on *all* elements perfectly well, without the need for the TAB key or the `tabindex` attribute.

A tab stop on a static element will confuse users, because A) it will be interpreted by the screen reader as having a non-interactive role, and B) any attempt to interact with the element (e.g. using SPACE, ENTER or ARROW keys) will be a no-op.

Unnecessary tabstops increase physical discomfort for some users - for example if using a [binary switch](http://en.wikipedia.org/wiki/Switch_Access) rather than a traditional keyboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ebay.gitbook.io/mindpatterns/antipatterns/tabindexitis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.