Hi Tom,
It’s exciting to see this getting started! To me a DEP would be highly
beneficial, because there is a lot to this that goes beyond finding and
fixing individual issues – it’s more about detailing the a process for
parts of Django to stay accessible over time. Here are things I’d
Week ending May 24, 2020.
*Triaged:*
https://code.djangoproject.com/ticket/31598 - Broken link in Django 1.4
docs. (invalid)
https://code.djangoproject.com/ticket/31599 - Improve the performance of
the autoreloader by ignoring third party packages. (wontfix)
Hi,
Thanks for the feedback. I had thought about a DEP when I was writing up
the original post actually, I just wasn't sure what it should contain. Here
are my thoughts, based on the feedback so far:
- Defining a standard to target.
- Forming an a11y team that covers the django admin and all
Hi Tobias,
I'm not a WCAG expert, and it's not clear to me what steps we would like
to take. In the ticket we have only steps describes as *"very basics which
should include"*, so I can imagine that's not all we need to do to be WCAG
2.1 compliant on AAA, AA or A level. As far as I'm
Hi,
felixxm proposed in https://code.djangoproject.com/ticket/31617 to add a
DEP for this. The more I think about it, the less I agree.
There is no DEP for security, usability, developer ergonomics or
anything like that, so why should there be one for accessibility?
Like with any of the other
