#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* stage: Unreviewed => Accepted
Comment:
Hi Thibaud, thanks for this.
Let's accept, with the proviso that I don't think we can really
remove/deprecate the `as_p()` &co methods — they're just too widely used.
We can steer folks to better methods, improve the markup as best we can,
and add the `role=presentation` I think without issue, but there's just
too much code out there (I think) to remove them.
One issue we have is breaking peoples existing pages if we change the
rendered HTML (so that CSS/JS selectors change for instance).
Can I point you to #31026, which is on my list for early in the 4.0 (i.e.
next) cycle. If we can get that in, then we'd be able to document a ''Use
this template ... to restore the previous HTML'', which then would give us
room to introduce a more significant change.
I hope that makes sense 😀
--
Ticket URL: <https://code.djangoproject.com/ticket/32339#comment:2>
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.b4897637d5482df831227dffd568d560%40djangoproject.com.
