-
Notifications
You must be signed in to change notification settings - Fork 295
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
[PWA Builder]: Nested Interactive Controls Unannounced by Screen Readers. #4758
Comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
17 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
1 similar comment
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
What happened?
There are nested interactive controls (such as buttons or links) within another interactive control (like a dropdown menu or modal dialog).
How do we reproduce the behavior?
Repro Steps:
What do you expect to happen?
Interactive controls should not be nested within each other to ensure they are properly announced and accessible to screen readers and other assistive technologies.
What environment were you using?
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461)
Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit)
URL: https://www.pwabuilder.com/reportcard?site=https://webboard.app
Tool: AI4W
Additional context
Element path:
app-index,app-report,#todo-detail,#header
Snippet:
How to fix:
Fix any of the following:
Element has focusable descendants
User Impact:
When interactive controls are nested, screen readers may not announce them correctly or users may experience difficulties in navigating and interacting with these controls using assistive technologies.
WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/name-role-value
Attachments:
The text was updated successfully, but these errors were encountered: