-
Notifications
You must be signed in to change notification settings - Fork 22
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
Input with multiple explicit label elements associated #249
Comments
This is defined in html aam I have a pr open now that cleans up the language a bit, but the current text is:
|
Thank you @scottaohara! I've missed it. Opening WPT if not already existing. |
i "think" @adampage or @rahimabdi might have worked on wpts for this? i might be wrong. i can't check myself right now - but maybe look for PRs from them before starting up a new one? |
Ha. I didn’t even remember I made that… |
Related to this: #108
What should happen if multiple
label
elements have the samefor
value?Example:
Browsers handle the calculation of the accessible name for the input inconsistently:
The accessible name algorithm relies on the host language "return that alternative in the form of a flat string as defined by the host language." However, the host language is not clear on this, and browser behavior is inconsistent.
Should we address this inconsistency? Should we request that the HTML specifications clarify this?
Once a decision is made, it might be useful to create a WPT issue to test the behavior (I can take care of this).
The text was updated successfully, but these errors were encountered: