Changes between Version 2 and Version 6 of Ticket #36828
- Timestamp:
- Dec 26, 2025, 10:59:56 AM (31 hours ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36828
- Property Owner set to
- Property Status new → assigned
-
Ticket #36828 – Description
v2 v6 1 1 Howdy, 2 2 3 Django 6 introduced unannounced changes to the default form rendering. Forms render with a fieldset, not a label, by default now. 3 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 4 4 5 I just noticed that fields render a `for`-attribute into a `legend`-tag. This isn't valid HTML5 according to spec: https://html.spec.whatwg.org/#the-legend-element 5 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. 6 6 7 Furthermore, the use of a fieldset/legend replaces the `label`-tag. However, input labels are required as of WCAG 2.1. 8 9 Since Django must be WCAG2.2 AAA compliant, we might even want to patch all supported versions. However, this would mean shippping a rendering change in a bugfix. 10 11 My current impulse would be to drop the `for` attribute in all supported versions for valid HTML and to enforce labels for WCAG compliance in 6.1 7 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. 12 8 13 9 Cheers!