#32820: Fields’ errors should be programmatically associated with fields.
-------------------------------------+-------------------------------------
Reporter: Thibaud Colas | Owner: Demetris
| Stavrou
Type: Bug | Status: assigned
Component: Forms | Version: 3.2
Severity: Normal | Resolution:
Keywords: accessibility, ui, | Triage Stage: Accepted
forms |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Thibaud Colas):
Note based on recent research for PR #15036
(https://github.com/django/django/pull/15036#issuecomment-1008738687):
- I still think this is a _Bug_ (WCAG 2.1 conformance fail) as Django
stands currently, however if/when ticket #32819 is tackled, we should mark
this ticket as a _New feature_, as contrary to what I thought `aria-
invalid="true"` isn’t required for conformance when `aria-describedby`
already points to an error message. If the error message can’t be
identified as such, then the bug to fix would be to make the error
messages unambiguous, which is a different issue.
- Even though I would expect fixing this to be a straightforward
improvement for almost all Django implementers, it’ll change how forms are
announced to screen reader users, so it would be valid to consider this as
a breaking change.
--
Ticket URL: <https://code.djangoproject.com/ticket/32820#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.796d7bd99035179e6f1ad17728594398%40djangoproject.com.
