Changes between Version 14 and Version 16 of Ticket #32338


Ignore:
Timestamp:
Jun 22, 2021, 5:06:13 AM (3 years ago)
Author:
Mariusz Felisiak
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #32338 – Description

    v14 v16  
    88
    991. The fields aren’t semantically grouped, only visually, so the grouping isn’t apparent to assistive technlogies. It’s important that related fields are grouped, and that the group has a label attached to it. If I was auditing this professionally I would classify this as a fail for [https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html SC 1.3.1 - Info and Relationships] of WCAG 2.1, as the grouping and label are somewhat there, just not done with the appropriate semantics.
    10 2. Speaking of label – currently the group of fields is labeled by preceding it with `<label for="id_radio_choice_required_0">Radio choice required:</label>`. This overrides the label of the first field within the group (and only labels the first field, not the whole group). This is a fail for [https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html 3.3.2: Labels or Instructions] and/or SC 1.3.1.
     102. (**fixed in b9e872b59329393f615c440c54f632a49ab05b78**) Speaking of label – currently the group of fields is labeled by preceding it with `<label for="id_radio_choice_required_0">Radio choice required:</label>`. This overrides the label of the first field within the group (and only labels the first field, not the whole group). This is a fail for [https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions.html 3.3.2: Labels or Instructions] and/or SC 1.3.1.
    11113. Wrapping the fields each in their own list item makes the navigation more tedious, as screen readers will first announce list items numbering, and only then their content.
    1212
Back to Top