Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility Select - Can't navigate to select with keyboard if in initially closed panel #17545

Open
1 of 4 tasks
GitJacek opened this issue Jan 31, 2025 · 0 comments
Open
1 of 4 tasks
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@GitJacek
Copy link

Describe the bug

There is an issue with keyboard accessibility when Select is used inside initially collapsed Panel.
When Panels input collapsed initially is set to false keyboard accessibility works as exptected.

Pull Request Link

No response

Reason for not contributing a PR

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

Other Reason

No response

Reproducer

https://stackblitz.com/edit/uvcatr26?file=src%2Fapp%2Fpanel-toggleable-demo.html,src%2Fapp%2Fpanel-toggleable-demo.ts

Environment

Win11

Angular version

19.0.1

PrimeNG version

v19

Node version

No response

Browser(s)

No response

Steps to reproduce the behavior

  1. Go to https://stackblitz.com/edit/uvcatr26?file=src%2Fapp%2Fpanel-toggleable-demo.html,src%2Fapp%2Fpanel-toggleable-demo.ts,package.json
  2. Expand Panel using + icon.
  3. Try to navigate to Select using 'Tab' key on keyboard.
  4. Unable to navigate to Select.

If you change filterCollapsed value to false:

Image

you will be able to navigate to select using 'Tab' key on keyboard.

For some reason tabindex input of select is ignored in first scenario.

Expected behavior

User should be able to navigate to Select using keyboard even if panel is initially closed.

@GitJacek GitJacek added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

1 participant