E-mail List Archives
Re: "Error feedback MUST be programmatically-associated with the appropriate element"
From: Mallory
Date: Sep 30, 2020 5:16AM
- Next message: Lucy GRECO: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message: Birkir R. Gunnarsson: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Next message in Thread: None
- Previous message in Thread: Sailesh Panchang: "Re: "Error feedback MUST be programmatically-associated with the appropriate element""
- View all messages in this Thread
I tend to mention them under 1.3.1. There is a visual relationship between an error message and its invalid field, and it is possible to programmatically associate it, so when someone doesn't, I tend to make a ticket.
cheers,
On Fri, Sep 25, 2020, at 10:35 PM, Jeremy Echols wrote:
> Looking over that checklist, I came to the same conclusion Jared just
> stated: showing error messages is required, and making sure they're
> clear is required. But they aren't required to be associated with a
> specific input programmatically unless they are associated visually.
>
> I get the annoyance of not having these things easily identified, and I
> need to improve my form design for sure in some ways, but I also need
> to know when I can actually cite a failure as opposed to stating that
> something is a best practice.
>
>
- Next message: Lucy GRECO: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Previous message: Birkir R. Gunnarsson: "Re: Screen Readers And Code Inspection Within Browser Dev Tools"
- Next message in Thread: None
- Previous message in Thread: Sailesh Panchang: "Re: "Error feedback MUST be programmatically-associated with the appropriate element""
- View all messages in this Thread