WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: "Error feedback MUST be programmatically-associated with the appropriate element"

for

From: Patrick H. Lauke
Date: Sep 26, 2020 8:35AM

On 26/09/2020 03:26, Birkir R. Gunnarsson wrote:
> This is part interpretation, part what I would term 4.6.2 (3.3.1 + 1.3.1)
> The text for 3.3.1 says:
>
> "Error Identification: If an input error is automatically detected,
> the item that is in error is identified and the error is described to
> the user in text."
>
> So that is required, both identifying the erronious input and
> describing the error in text.

But it doesn't say when/how this identification/description should
happen. If the error message is a paragraph that comes after an input
but is not associated, you could still say that "the error is identified
and the error is described to the user in text". Just that the user
needs to find that. It doesn't qualify how it should be done, or that it
should be programmatic/automatic.

> Here's where the standard is showing its age, the understanding
> document goes on to say:
>
>
> "The identification and description of an error can be combined with
> programmatic information that user agents or assistive technologies
> can use to identify an error and provide error information to the
> user [...]"

But of course, that part isn't normative, and it's more a
suggestion/best practice of what *can* be done.

So it still feels like for normative fail, 1.3.1 is the best bet.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke