-
Notifications
You must be signed in to change notification settings - Fork 152
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
FastPass Does Not Associate Labels with Custom Elements #6798
Comments
This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights! |
Looking at this, I suspect that the problem isn't the custom control, but that the custom control is a node inside a shadow DOM, while the label is outside the shadow DOM, even though the shadow DOM is open. Several posts online (including this one from WilcoFiers of the axe team) suggest that it's intentional behavior for an IDREF property to cross a shadow DOM boundary. That's how shadow DOM provides isolation between the contents of multiple (and potentially conflicting) elements within shadow DOMs on the same page. Addendum: I confirmed in the HTML document spec that |
We believe this is by design for the reasons listed above. Please reopen it if you find formal documentation that suggests that the |
Creating form-associated custom elements using the https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals |
For more information, this ticket was elevated to axe-core. |
Describe the bug
When using the ElementInternals API, form-associated custom elements are showing a missing label error when a label is associated with it.
To Reproduce
Steps to reproduce the behavior:
CodePen repro example
https://codepen.io/break-stuff/pen/qBQPGVb?editors=1011
Expected behavior
It should correctly associate the label with the component.
Screenshots
Context (please complete the following information)
Are you willing to submit a PR?
No
Did you search for similar existing issues?
Yes
Additional context
The text was updated successfully, but these errors were encountered: