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
{{ message }}
This repository has been archived by the owner on Mar 2, 2022. It is now read-only.
Currently the id attribute value for many elements is derived from the value of the field or field option. Without any formatting it is possible for an ID to contain spaces (and presumably other non-spec characters).
This does violate the HTML spec, but a more pragmatic issue is that it prevents the label being associated with the button in the NVDA screenreader.
Perhaps we could add an id attribute to the options objects created in lib/template-mixins.js which stripped out illegal chars and formatted to an appropriate case (kebab case)?
This may be an issue with other elements, but so far we've only had issues with option groups.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the
id
attribute value for many elements is derived from thevalue
of the field or field option. Without any formatting it is possible for an ID to contain spaces (and presumably other non-spec characters).You can see this in action on the Electronic Visa Waiver form flow:
This does violate the HTML spec, but a more pragmatic issue is that it prevents the label being associated with the button in the NVDA screenreader.
Perhaps we could add an
id
attribute to the options objects created inlib/template-mixins.js
which stripped out illegal chars and formatted to an appropriate case (kebab case)?This may be an issue with other elements, but so far we've only had issues with option groups.
The text was updated successfully, but these errors were encountered: