- 🇦🇺Australia acbramley
This is still valid on HEAD, tested with the default options checkboxes on the NodeTypeForm. AFAICT there is still no solution for this in raw HTML.
The checkboxes element provided by core does not apply the `required` attribute to the generated <input>
elements. Instead the required attribute is applied to the wrapping <fieldset>
.
There are two issues with this:
<input>
s for checkboxes. If the attribute is not present on the <input>
, then the required state will not be communicated to the screen reader user.<fieldset>
, thus causing the page to fail W3C validation.To reproduce this, create a form that uses the Checkboxes element. Notice that the required attribute is attached to the wrapping <fieldset>
and not the <input>
elements.
@mfairchild365 created a hacky module to fix the issue. It might be helpful in diagnosing and fixing the issue in core: https://github.com/mfairchild365/a11yformsfix/blob/master/readme.md
Evaluate impact on templates - does this qualify as a bugfix which can go in Stable theme?
Write a patch.
Tests?
Markup changes to:
None.
none.
Active
11.0 🔥
render system
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is still valid on HEAD, tested with the default options checkboxes on the NodeTypeForm. AFAICT there is still no solution for this in raw HTML.