#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
-------------------------------------+-------------------------------------
Comment (by Tushar):
pa11y seems to be much better than using axe. pa11y can be called directly
from CLI on URLs, we can use axe-core as a pa11y runner, it can output a
decent formatted result, and have options to customize them even further.
Apart from that, I see pa11y-dashboard as well to visualize results if
needed.
After every UI change, writing a helper function that calls pa11y on the
current selenium instance will not take much effort.
I highly favour using the existing admin tests for accessibility as
compared to writing and maintaining accessibility tests.
One issue that I see with using pa11y as described above is redundancy in
pa11y results because every time we would call pa11y, it would scan the
whole page instead of only the new UI change.
pa11y has an option rootElement to only test a subset of DOM but this
would require the use of "#" id tag to identify the elements that I doubt
might be present on every UI piece of admin.
Other way than writing a whole accessibility testing suite is to iterate
overall the .html files in the project and run pa11y over them to generate
results. This might give us a lot of false positives like missing head tag
or title tags due to .html file being in jinja template format.
Let me know your thoughts on the above points before I go ahead with
something.
--
Ticket URL: <https://code.djangoproject.com/ticket/33620#comment:11>
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/01070185299f66cc-3f3eaa07-abe0-4b3d-8e1e-661aa00bd019-000000%40eu-central-1.amazonses.com.
