Skip to content

Conversation

jpg619
Copy link
Contributor

@jpg619 jpg619 commented Oct 6, 2025

  • Keyboard focus order is not logical for the list items under 'Select CLI Version' button. keyboard focus is moving twice upon the version list items.
Screenshare.-.2025-10-06.10_16_14.AM.mp4

const VariantItem = ({title, shortName, url, active}) => {
return (
<ActionList.Item state={{scrollUpdate: false}} id={shortName} active={active}>
<ActionList.Item state={{scrollUpdate: false}} id={shortName} active={active} tabIndex={null}>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is often more reliable for preventing React components from adding unwanted tabindex attributes.

@jpg619 jpg619 self-assigned this Oct 6, 2025
@jpg619 jpg619 marked this pull request as ready for review October 6, 2025 14:18
@jpg619 jpg619 requested review from leobalter and a team as code owners October 6, 2025 14:18
@jpg619 jpg619 requested review from owlstronaut and Copilot October 6, 2025 14:18
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Fixes accessibility issue with keyboard navigation in the CLI version selector by adding tabIndex attribute to VariantItem components to prevent duplicate focus events.

  • Add tabIndex={null} to ActionList.Item to improve keyboard focus order
  • Resolves issue where keyboard focus was moving twice on version list items

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@jpg619 jpg619 merged commit 4b97e8a into main Oct 6, 2025
9 checks passed
@jpg619 jpg619 deleted the jpg619/fix-accessibility-dorpdown-tab branch October 6, 2025 15:40
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