Hey all, I've been looking at the couple of tickets open to improve accessibility of the forms and checkbox/radio widgets. [1][2]
While changing the layout is _fairly_ straight forward I'm unsure how to transition to the new way. I'm focusing this change in changing the widget templates until the patch for template based rendering of forms is merged. I think the options are: 1) Just make the change and have a breaking change. 😬 2) Introduce the new template and deprecate use of the old template. This is really horrid as _everyone_ will have to add boiler plate template over rides to point at the new template. We'd then probably want to change the name again at the end of the depreciation period. 3) Change the default template and package the old template, folk can then over ride their template if they still want the old behaviour. We can then deprecate the old template, and folk can include it their selves if they want it longer term. While a breaking change there would be a _simple_ solution. I hope this is enough to get your creative juices going! I'm hoping there is a better way than what I can think of. My gut reaction would be to go for option 3. We don't have any data on how well used the default templates are used, I'm guessing it's not used that much... Appreciate your thoughts. Kind Regards David [1]https://code.djangoproject.com/ticket/32338 [2]https://code.djangoproject.com/ticket/32339 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0f1b752b-fd69-4d22-939e-867cc17e7819n%40googlegroups.com.
