In entity forms, fields with cardinality > 1 are rendered in a table with the field's label as the table header. This creates inconsistent HTML between single and multiple value fields. This causes several problems:
Although it kind of makes sense to have the label as a table header as it's already rendered in a table, overall it causes more troubles than benefits. These images illustrate two text fields, one as single value, the other as multi value. The difference is vast both visually and in the DOM.
template_preprocess_field_multiple_value_form() into a <label> just like single value fields.Which will result in something like this:
In entity forms, multiple values will have the field's label rendered the same way as single values. The exception is field's that has its own handling of multi value fields (options.module et.al.)
None AFAICS.
Closed: duplicate
11.0 🔥
user.module
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Given there is no response from #12 in 2017, I think we should close as a duplicate of ✨ Allow multiple field widgets to not use tabledrag Needs work .
Didn't mean to change the component, but thinking it probably belongs here anyway.