Missing Keyboard Navigation Support Blocks Non-Mouse Interaction

[Tushar15769]

📌 Description

Interactive controls do not support expected keyboard interaction patterns.

Current behavior:

Tabs do not support ArrowLeft navigation
Tabs do not support ArrowRight navigation
Toggles do not respond to Space key activation
Toggles do not respond to Enter key activation
No roving tabindex implementation exists
Keyboard-only navigation is incomplete

Because keyboard interaction handlers are missing, users cannot fully operate the interface without a pointing device.

As a result:

Keyboard-only users are blocked
Accessibility requirements are not satisfied
Navigation efficiency is reduced
Interactive components become difficult to use
User inclusivity is negatively impacted

🎯 Expected Behavior

Components should support standard keyboard interactions
Arrow keys should navigate tab interfaces
Space and Enter should activate controls
Focus management should follow accessibility patterns
Full application functionality should be keyboard accessible

[singhtrivendra]

Please add screenshots of the bug and provide a simpler explanation.

Some issues appear to be AI-generated or lack sufficient details, so I am closing a few of them for now. For the remaining issues, please update the description with:

• Relevant screenshots
• Clear reproduction steps
• A short and concise explanation written in your own words

After the required information is added, I can review and reopen the issue if appropriate.

[github-actions]

This issue is stale because it has been open 30 days with no activity.