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 sites in the django github organization, and defining its role, membership, etc. - Deciding on a CI process - An outline of current issues and how to solve them. If anyone can think of anything else, please let me know. If/when there's a consensus I'll start writing a draft. Mariusz, I mentioned this in the original post, but https://www.w3.org/WAI/policies/ has a good overview of laws and EU directives in this area. From my browsing through, it seems that they all either, have their own national standard, or are using WCAG 2.0/2.1 AA. Since we probably don't want to define our own standard, I think AA is the way to go. This seems to also be the recommendation I hear from people in the accessibility field working on regular websites. AAA seems to be more suited for very specialist sites that explicitly target disabled people. Most of AAA is completely feasible for us, but there are some reasons it would be difficult: - All language needs to be at a lower secondary education level, or have an alternative that is. This doesn't seem feasible, for e.g. the documentation. - Users that are logged out need to be able to resume their session where they left off after logging in, with all form fields filled, etc. There are others that are difficult, but I don't think any apply to us currently. Cheers, Tom On Mon, 25 May 2020 at 11:09, Mariusz Felisiak <felisiak.mari...@gmail.com> wrote: > 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 concerned WCAG > is quite massive. Moreover if we want to make changes in CI we should > discussed available tools, etc. We can change colors but what next? We will > be not able to guarantee that the contrast of all elements remains > appropriate, we cannot do this manually. > > Best, > Mariusz > > -- > 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/be97c4e7-f961-4d46-998f-693ca6076f09%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/be97c4e7-f961-4d46-998f-693ca6076f09%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAHoz%3DMaG5C7hHJ%3DJZaLZ8DNsevZzr8hmJ%3Dd4S%3D1mmTsXkiyPZw%40mail.gmail.com.
