Will It Vibe?Positive tabindex value
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A tabindex/tabIndex greater than zero pulls that element out of the natural document order and to the FRONT of the tab sequence, so keyboard users jump there first regardless of where it sits visually. It also forces every other positive value in the page into a fragile, hand-maintained order. Use tabindex="0" to make an element focusable in its natural place, or remove tabindex entirely on elements that are already focusable.
Why it matters
A tabindex greater than zero yanks that element to the very front of the tab sequence regardless of where it sits on the page, so keyboard users hit it first, then get thrown back to wherever document order resumes. Once one positive value exists, every other interactive element on the page effectively needs its own number to stay in a sane order, which turns tab order into a maintenance liability that breaks the moment someone adds a new field.
How to fix it
Change the value to tabindex="0" so the element becomes focusable in its natural position in the document, and reorder the actual DOM/JSX if the visual order needs to change instead of faking it with tabindex numbers. If the element is already natively focusable (a button, a link, a form field), remove the tabindex entirely.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo