-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Component: Dropdown Accessibility #15155
Closed
WTW-Jacob-Evans opened this issue
Mar 25, 2024
· 0 comments
· Fixed by #15980 · 4 remaining pull requests
Closed
Component: Dropdown Accessibility #15155
WTW-Jacob-Evans opened this issue
Mar 25, 2024
· 0 comments
· Fixed by #15980 · 4 remaining pull requests
Labels
Component: Accessibility
Issue or pull request is related to WCAG or ARIA
PRO Support
Issue was reported by PRO User
Milestone
Comments
WTW-Jacob-Evans
added
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Mar 25, 2024
mehmetcetin01140
added
Component: Accessibility
Issue or pull request is related to WCAG or ARIA
PRO Support
Issue was reported by PRO User
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Jun 26, 2024
cetincakiroglu
added
the
Resolution: Wontfix
Issue will not be fixed due to technical limitations
label
Jun 27, 2024
mehmetcetin01140
removed
the
Resolution: Wontfix
Issue will not be fixed due to technical limitations
label
Jul 8, 2024
mehmetcetin01140
added a commit
that referenced
this issue
Jul 8, 2024
cetincakiroglu
added a commit
that referenced
this issue
Jul 11, 2024
Fixed #15155 - Component: Dropdown Accessibility
This was referenced Aug 16, 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
PRO Support
Issue was reported by PRO User
Describe the bug
When scanning the dropdown component, we are seeing an error relating to "Scrollable region must have keyboard access"
I understand that this is a feature, and that to remove this warning would interfere with your implementation of keyboard navigation. I attempted to implement a suggestion from your team about adding a template "Unfortunately, in this situation, we are unable to intervene in the issue. However, to make the test pass, you can use the templating option to add a hidden focusable element to the first element."; attempting to add this template did not seem to fix the issue, as the issue seems related to the dropdown and not the selected item.
Any further assistance would be appreciated.
Environment
Windows 10
Reproducer
No response
Angular version
17.2.3
PrimeNG version
17.11.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.18.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: