#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 Thibaud Colas): Thank you Carlton, that makes complete sense to me. [https://code.djangoproject.com/ticket/31026 #31026] sounds very promising to solve this, particularly the "Use this template to restore the previous behavior" scenario. I’ll take a look and see whether I can provide a more detailed proposal. Re whether the breakage is worth it or not – I think it’s worth me expressing more nuance between the different methods: - `as_p` isn’t something I would recommend, and isn’t something I think Django should recommend, but it’s not actively causing big issues for end users that Django could solve by removing it. All the removal would achieve is increased awareness of how to implement forms better, but it’s not like that can’t be achieved otherwise, and `as_p` being gone doesn’t guarantee better patterns will be used. - `as_table` on the other hand results in forms that are confusing for screen reader users, and would fail an accessibility audit. - `as_ul` is somewhere in-between. --- For `role=presentation` – as far as I understand this would be a documentation change only. Is this something you think we could be doing right now? If so I might also spend more time reviewing other potential accessibility improvements to code snippets in the documentation. -- Ticket URL: <https://code.djangoproject.com/ticket/32339#comment:3> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/070.aa73b9fc0f212d2c2f1b5d964f9373e3%40djangoproject.com.