Skip to content

Conversation

@ssherigar-c-eightfold
Copy link

@ssherigar-c-eightfold ssherigar-c-eightfold commented Nov 10, 2025

SUMMARY:

Only the active tab should be focusable using the Tab key, while arrow keys should be used to navigate between non-active tabs.
Solution:
The enableArrowNav property has been added to the Tabs, which is an Octuple component, to allow arrow-key navigation between tabs

GITHUB ISSUE (Open Source Contributors)

NA

JIRA TASK (Eightfold Employees Only):

https://eightfoldai.atlassian.net/browse/ENG-162486

CHANGE TYPE:

  • Bugfix Pull Request
  • Feature Pull Request

TEST COVERAGE:

  • Tests for this change already exist
  • I have added unittests for this change

TEST PLAN:

Navigate to TA Home -> Accounts page
Access the navbar menu via arrowKeys

Expected Result:
Keyboard users can navigate between non-active tabs using the arrow keys, while the Tab key only focuses the currently active tab, ensuring proper and accessible tab navigation.

Screen.Recording.2025-11-10.at.3.44.12.PM.mov

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@ssherigar-c-eightfold ssherigar-c-eightfold changed the title fix(ENG-162486): default value set as true for enableArrowNav to meet accessibility standard for navbar ENG-162486: default value set as true for enableArrowNav to meet accessibility standard for navbar Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants