Tab key navigation should be limited to interactive elements.
Adding tabIndex to non-interactive elements creates unnecessary stops in the tab order and can confuse users relying on keyboard navigation.
Non-interactive elements can use tabIndex="-1" if they need to be programmatically focused, but should not be in the natural tab order.
If you have specific requirements for keyboard navigation that require non-interactive elements to be in the tab order, you may need to disable this rule.