#33620: Accessibility in pipeline
-------------------------------------+-------------------------------------
Reporter: Sarah Abderemane | Owner: Tushar
Type: New feature | Status: assigned
Component: contrib.admin | Version: dev
Severity: Normal | Resolution:
Keywords: accessibility, ux, | Triage Stage: Accepted
ui, admin |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Tushar):
* owner: Sarah Abderemane => Tushar
* status: new => assigned
Comment:
Hey, I was digging into this and was able to get aXe run with the current
testing suite using axe-selenium-python. I am not sure about the scope of
checking the accessibility of the admin panel, and what views and admin
page state are we looking to test.
It could be 0 violations on the first admin landing page and then we might
get violations when we visit a specific group or table or other section of
the admin dashboard.
What I have in my mind is after every selenium test that is run, run the
aXe accessibility test as well by using a decorator probably. Please share
your views on how you would want it.
cc @Carlton Gibson
--
Ticket URL: <https://code.djangoproject.com/ticket/33620#comment:7>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184e7957f40-f8484537-7de6-407b-b2ce-ecc858c821db-000000%40eu-central-1.amazonses.com.
