#36828: Django form fields render into invalid HTML
-------------------------------------+-------------------------------------
     Reporter:  Johannes Maron       |                    Owner:
                                     |  Youngkwang Yang
         Type:  Bug                  |                   Status:  assigned
    Component:  Forms                |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  accessibility        |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Johannes Maron:

Old description:

> Howdy,
>
> Django 6 introduced unannounced changes to the default form rendering.
> Forms render with a fieldset, not a label, by default now.
>
> 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
>
> Furthermore, the use of a fieldset/legend replaces the `label`-tag.
> However, input labels are required as of WCAG 2.1.
>
> 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.
>
> 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
>
> Cheers!
> Joe

New description:

 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

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36828#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019b5b9a4a12-80a8704c-2f95-4b2b-ba73-7460f7324f23-000000%40eu-central-1.amazonses.com.

Reply via email to