Field comp stops using div element inside the label #2166
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The a11y audit gives errors about placing
divs
insidelabel
elements.It seems that the HTML spec says that a
div
cannot go inside alabel
(which will only accept "Phrasing content").Doing so cause automated HTML validators, such as https://validator.w3.org/nu/, to throw errors.
This PR fixes this, for most cases* by using a
span
element instead of thediv
.*However components that feature select/dropdown elements e.g. issuerLists, or Address comps with country selectors, will still contain
divs
(since that is how the dropdowns are built). This will need to be addressed in a future PRTested scenarios
Components without dropdowns no longer have a
div
inside theirlabel
elementFixed issue: partially fixes a11y issue with instanceID=2047874661