Missing input labels (WCAG2.1)

[Johannes Maron]

Howdy,

I noticed Django sometimes replaces the label with a fieldset tag. However, input labels are required as of WCAG 2.1; see also: ​https://www.w3.org/TR/WCAG21/#labels-or-instructions

Since Django must be WCAG2.2 AAA compliant, we might even want to patch all supported versions. However, this would mean shipping a rendering change in a bugfix.

My current impulse would be to enforce labels for WCAG compliance in 6.1, since shipping a rendering change within a bug fix release might result into more issues for users.

Cheers!
Joe

[Youngkwang Yang]

This looks similar to #36724 (fixed in PR ​https://github.com/django/django/pull/20080).
could you check which version you're testing with?

[Johannes Maron]

Thanks! Yes, that does resolve half of the issue. We have correct HTML, but the WCAG violation remains.

[Antoliny]

Thank you, Joe :)

Could you share an example of where the issue shows up?

My guess is that you’re referring to ClearableFileInput, which was recently switched to use a fieldset. When using the ClearableFileInput widget and an initial value is present, it appears that the input for changing the value does not have an associated label.

Since the original label was replaced by a legend, it seems that this part (the “changed” input) should now have an associated label.

Is this the case you had in mind?