A11y Code Sprint Berlin: Success Criterion 9.2.4.6 - remove redundant fieldsets from forms

[SarahEdding]

Feature Request

Description

In the contact form, fields are currently grouped into two fieldsets, neither of which is labelled. This is based on the form's layout and is confusing to screen reader users, because the grouping is not related to structure and/or content of the form.
Fieldset in login form is also redundant.

Solution

Removing both fieldsets will result in a concise and clear contact form that is structured in a way users are accustomed to.

Alternative

If removing the fieldsets is not possible, adding legends to both of them may help users to understand the form better.

[schmigotzki]

@alexakressmann Please assign to me

[schmigotzki]

@SarahEdding How about this solution?
Adding a label (/legend) to each fieldset would be easier.

[schmigotzki]

Fieldsets in the felogin forms are unnecessary and could be removed. This is not optimal from an accessibility point of view, but according to @SarahEdding it can be tolerated. This would be a core change and can be implemented on occasion.

[benjaminkott]

We introduce a new element that needs to be used to avoid fieldsets. The form served by the bootstrap_package is already adjusted. If the introduction package uses a different one the fieldset needs to be replaced with grid column.

See change here: 9132b04#diff-a51f3921d8ba07c03befce1d404f530f7a8991d3d59df8d52d5ea6e88d823e63