You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An HTML validity error detected in Chrome showed that the configuration for the label props was ignoring the fact that the search input id is hardcoded, while the label for attribute is provided by dropshift. They should match.
To Reproduce
Open storybook in Chrome.
Open "Issues" in the dev tools.
Note the error Incorrect use of <label for=FORM_ELEMENT>
The label's for attribute doesn't match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.
To fix this issue, make sure the label's for attribute references the correct id of a form field.
The label is not visible to non screenreader users. It uses the -10000px position absolute technique to be rendered off the page.
It's not a large bug, most users won't be affected at all. But, I believe it's an accessibility issue.
The text was updated successfully, but these errors were encountered:
…js#23463)
The for attribute value was not set to match the hardcoded value
used for the search input id.
plumpNation
changed the title
[Bug]: Incorrect use of label for attribute in search input label.
[Bug]: Incorrect use of label for attribute in search input label (fixes #23463)
Jul 15, 2023
plumpNation
changed the title
[Bug]: Incorrect use of label for attribute in search input label (fixes #23463)
[Bug]: Incorrect use of label for attribute in search input label
Jul 15, 2023
Describe the bug
An HTML validity error detected in Chrome showed that the configuration for the label props was ignoring the fact that the search input
id
is hardcoded, while the labelfor
attribute is provided by dropshift. They should match.To Reproduce
Open storybook in Chrome.
Open "Issues" in the dev tools.
Note the error
Incorrect use of <label for=FORM_ELEMENT>
System
Additional context
The label is not visible to non screenreader users. It uses the -10000px position absolute technique to be rendered off the page.
It's not a large bug, most users won't be affected at all. But, I believe it's an accessibility issue.
The text was updated successfully, but these errors were encountered: