#32339: Accessibility issues with Django forms as_table, as_ul, as_p rendering
helpers
-------------------------------------+-------------------------------------
     Reporter:  Thibaud Colas        |                    Owner:  David
                                     |  Smith
         Type:  Bug                  |                   Status:  assigned
    Component:  Forms                |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  accessibility,       |             Triage Stage:  Accepted
  forms, wcag                        |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  1
-------------------------------------+-------------------------------------

Comment (by Carlton Gibson <carlton@…>):

 In [changeset:"fde946daffbb007a7d033945677cc8e9e475d516" fde946da]:
 {{{
 #!CommitTicketReference repository=""
 revision="fde946daffbb007a7d033945677cc8e9e475d516"
 Refs #32339 -- Restructured outputting HTML form docs.

 In the topic doc, promoted the Reusable form templates section.

 In the reference, re-grouped and promoted the default __str__()
 rendering path, and then gathered the various as_*() helpers
 subsequently.

 Thanks to David Smith for review.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32339#comment:16>
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 on the web visit 
https://groups.google.com/d/msgid/django-updates/010701808e7cef14-0f4db7b3-0954-450b-90c7-941f297db79e-000000%40eu-central-1.amazonses.com.

Reply via email to