[Feature Request]: Keyboard Focus Tabs enhancement

[hngan]

Description

In the Tabs component, for accessibility concerns, we have customers who only use the keyboard to navigate through the tab menu. However, once we press the arrow keys to traverse the tabs, the tab automatically be considered "Active", and in our case, due to the things rendered within the content, it would cause the focus on the tab menu to drop.

Is there a way we can use keyboard navigation to traverse the list of tabs without their contents from rendering?

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate requests

[jperals]

Hi,

As discussed offline, changing the behavior as described would contradict w3c reccomendations. I would recommend to change the app logic on your end to prevent the automatic focus change.

[hngan]

Spoke with my team, and we decided to try to make some changes on our application, based on the link you sent, what we need is the ability to use tabs with manual activation. The content of our tabs do take a while to load and hinders users' ability to navigate efficiently across the tab list