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 issue when using p-dropdown inside accordian #14905

Closed
priyam-shah-hiwi opened this issue Feb 29, 2024 · 2 comments
Closed

Accessibility issue when using p-dropdown inside accordian #14905

priyam-shah-hiwi opened this issue Feb 29, 2024 · 2 comments
Labels
Component: Accessibility Issue or pull request is related to WCAG or ARIA Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@priyam-shah-hiwi
Copy link

Describe the bug

primngbugreport.mp4

When using dropdown inside accordian tab, the keyboard accessibility like tab, arrow-down arrow-up does not work. The arrow-up event changes the focus from the dropdown to the accordian. As seen from the video when i move the focus to payment type and the arrow keys move the focus to the parent element ie arrodian.

Environment

Angular 17.0.7
PrimeNg 17.8.0

Reproducer

No response

Angular version

17.0.7

PrimeNG version

17.8.0

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

v18.16.1

Browser(s)

Chrome, Edge

Steps to reproduce the behavior

  1. Create dropdown inside accordian tab
  2. press tab to move on the dropdown
  3. press enter / space to open the options
  4. press arrow-up / arrow-down
    focus changes to accodian

Expected behavior

Focus should stay on the dropdown and the options should be accessed using key-up and key-down
(issue got introduced in primeng 17, does not occur in ngprime 13)

@priyam-shah-hiwi priyam-shah-hiwi added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 29, 2024
@mehmetcetin01140 mehmetcetin01140 added Component: Accessibility Issue or pull request is related to WCAG or ARIA and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Mar 4, 2024
Copy link

github-actions bot commented Jul 3, 2024

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Jul 3, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Accessibility Issue or pull request is related to WCAG or ARIA Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response
Projects
None yet
Development

No branches or pull requests

2 participants