#31617: Improve overall admin accessibility.
-------------------------------------+-------------------------------------
     Reporter:  Gustavo Siñovsky     |                    Owner:  Saugat
                                     |  Rajbhandari
         Type:  New feature          |                   Status:  assigned
    Component:  contrib.admin        |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  accessibility, ui,   |             Triage Stage:
  ux, admin                          |  Someday/Maybe
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  1
-------------------------------------+-------------------------------------

Comment (by Thibaud Colas):

 👋 I’ve finally been able to spend a bit of time looking at the
 accessibility of the Django admin, after spending most of my time on
 forms. I’ve opened
 
[https://code.djangoproject.com/query?status=assigned&status=new&keywords=~accessibility&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id
 three bug reports and a feature request].

 My initial assessment is that there are _a lot_ of issues with the admin
 as-is. This raises a few questions for me:

 1. Having a ticket so broad in scope as this one doesn’t seem very
 helpful. It’d take tens of hours just to report the issues, let alone
 agree on fixes and delivering them. If we want to have a long-term
 "umbrella" place to track many issues, would there be a better place than
 this ticket? Within the GitHub issues / PR paradigm I would normally be
 looking for a Projects board for this.
 2. It’s unclear to me how helpful it is to report issues as tickets as I
 uncover them. My time might be better spent making a more traditional
 audit, which could then be broken up into more meaningful tickets.

 I could make a spreadsheet (Google Sheets), reusing a
 
[https://docs.google.com/spreadsheets/d/1l7tnpEyJiC5BWE_JX0XCkknyrjxYA5T2aee5JgPnmi4/edit
 template I have from Wagtail] This is simple but is quite specialized and
 lacks a few basic features (screenshots). We could use a service like
 [https://beinclusive.app/ Be Inclusive], whose founder let me know they
 would be interested to sponsor Django with free access to their service if
 the need arrives. Perhaps Django has other organisational tools in place
 to consider?

 ---

 On the issues, to give a bit more information, at a high level:

 - There are almost no landmark regions. This needs to be introduced for
 all pages throughout the admin
 - There is surprisingly little usage of ARIA roles and attributes compared
 to the number of bespoke interactive elements in the admin. This suggests
 a lot of those elements are implemented in a way that only works for
 sighted users (and potentially keyboard users too). For example,
 InlineModelAdmin seems like something that ought to use ARIA.
 - I can find a lot of contrast issues, particularly in dark mode.
 - A lot of the admin seems to be overusing `title` attributes to provide
 basic tooltips. This means the contents of those tooltips is only
 available to mouse users and screen reader users, leaving keyboard and
 touch screen users out.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31617#comment:17>
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/01070180deb8ec17-4b13b0b7-24bd-4a8e-b004-e21a82570abb-000000%40eu-central-1.amazonses.com.

Reply via email to