#32339: Accessibility issues with Django forms as_table, as_ul, as_p rendering
helpers
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: accessibility, | Triage Stage: Accepted
forms, wcag |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Tom Carrick):
I think the easiest / quickest / least trouble-causing thing to do here is
to put a big warning in the docs along the lines of "These methods are
suitable only for quickly testing forms and shouldn't be used in
production code because, x, y and z" along with perhaps a note on the role
attr as a quick fix for old code.
I agree we probably can't remove them, but we could at least do this as a
first step, along with making them more accessible where possible.
In the future? I'm not sure, I defer to Carlton, and I think his
suggestion re: the form templates is good. Also perhaps a system check
might work? e.g. complain if you use the methods, but it's easy enough for
people to disable.
One more extreme thought: perhaps we can do as we did with the old `{%
trans %}` and co tags -- de-document them but leave them there for old
code to use, perhaps to be removed in some far future date (or not).
--
Ticket URL: <https://code.djangoproject.com/ticket/32339#comment:4>
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/070.81dabef9fbe1c6b17d08bc25c8514271%40djangoproject.com.
