#32340: Usability issues with Django form fields expecting specific patterns
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: accessibility, | Triage Stage: Accepted
usability, forms |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Comment (by Thibaud Colas):
See PR [Accessibility guidelines for all contributors #17338
https://github.com/django/django/pull/17338] for the next step on adding
accessibility docs in Django. After this, I believe [Add guidelines for
accessibility in documentation #17340
https://github.com/django/django/pull/17340] will be a good step in adding
accessibility considerations in documentation.
After _that_, I think we’ll be in an excellent place for someone to pick
up this ticket and write the right docs. We don’t necessarily need all of
this to be merged though if someone wants to already take a look. A good
first step would be to identify where in Django’s documentation we could
document what’s discussed in this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/32340#comment:6>
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/0107018d18f9f682-9575ce8f-48f9-4f71-9c6e-1f319e7f8a5f-000000%40eu-central-1.amazonses.com.
