WebAIM - Web Accessibility In Mind

E-mail List Archives

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


From: Vaughn, Michael
Date: Sep 25, 2020 2:16PM

I agree that the Deque training could be improved by incorporating the SC that applies into the training. Especially if youÂ’re using this training to help improve the ability to conduct WCAG audits.

You might find it helpful to refer to their WCAG checklist<https://dequeuniversity.com/checklists/web/>. So for example searching for the topic finds on page 35 of the PDF version<https://media.dequeuniversity.com/public/en/docs/deque_web_accessibility_checklist.pdf> that it indicates this would fail 3.3.1<https://www.w3.org/WAI/WCAG21/Understanding/error-identification>.

From: WebAIM-Forum < <EMAIL REMOVED> >
Date: Friday, September 25, 2020 at 4:01 PM
Subject: [WebAIM] "Error feedback MUST be programmatically-associated with the appropriate element"
I'm going through the Deque training, and while I have so far found it extremely informative, I wish it would specify things like which SC a requirement falls under, what level, etc. The subject of this email is one that I'm totally unfamiliar with. I knew that errors in forms had to be identified clearly such that a screen reader user could fix any mistakes, but this section of the training talks about associating each error message with a specific form field, for instance via aria-describedby.

What SC would this fall under? What level? Is this a AAA thing? That would explain why I've never run into it. Or am I just ignorant of a requirement I've been failing for years?