Hi Thibaud,

thanks for the follow up. +1 on basically everything you wrote!

On 15/06/2021 02.59, Thibaud Colas wrote:
This distinction between "sites built with Django" and the "Django admin" highlights an important point, which is that for lots of sites the Django admin would be what accessibility standards call an authoring tool. There is a separate standard for authoring tools that builds upon WCAG 2.1: ATAG 2.0. I think we should also explicitly aim for compliance with ATAG 2.0 wherever possible, as it has a lot of useful guidelines we could follow for the Django admin. For Django itself, there might be very little to do to implement those guidelines, but for the wider ecosystem of CMS-like features in Django it would make a clear difference if Django was clearly defined as an authoring tool. WCAG itself is a very thin baseline as standards go, so anything that goes beyond it is well worth considering in my opinion.

I am not completely sure about the definition of an "authoring tool", but it might make sense to consider django as a whole as such an authoring tool, not just the Django admin. ATAG A. (Make the authoring tool user interface accessible) would then only apply to Django admin, but ATAG B. (Support the production of accessible content) would apply to everything.

  * *Which automated or semi-automated testing tools to use when testing
    changes to Django*. My go-to is anything Axe
    <https://www.deque.com/axe/>-based, as it’s ubiquitous, and has very
    few false positives. In particular with the Accessibility Insights
    <https://accessibilityinsights.io/> browser extension.

AFAIK the accessibility checker in chrome's lighthouse is also based on Axe. As it is already built into a very popular browser this might lower the threshold for testing even further.

tobias

--
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/7756471f-bfd0-42c4-3811-d355d5d6d0d4%40posteo.de.

Reply via email to