#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 Sarah Abderemane):
Hi Tushar,
Sorry for the late reply.
Pa11y seems a good option to me, it's well maintained and Thibaud already
suggested it previously so I think you can go ahead.
> 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.
I think it's a very good idea to re-use the existing test suite rather
than maintaining whole new ones but pa11y should be run on rendered pages
and we may have specific tests case to test correctly accessibility for
the whole page. A small change can affect the rest of the page and we
should be aware of that according to me.
I suggest to use the existing tests if possible, for those when we need a
dedicated test a part, we will add it to an accessibility testing suite.
--
Ticket URL: <https://code.djangoproject.com/ticket/33620#comment:12>
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/01070185e6356294-e2b03052-1716-43ee-8b40-9d4a3b005279-000000%40eu-central-1.amazonses.com.
