WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.1 - 1.3.5 - How to capture a violation?

for

From: Jonathan Avila
Date: Jul 25, 2018 10:38AM

> I'm still really confused by what you are suggesting. Again, where does this success criterion state or suggest that accessible name (e.g., <label>, aria-label, etc.) cannot be used to convey the purpose?

From what I understand the goal of the criterion was to ensure that there was a machine readable way to know exactly what the purpose of the field was and therefore allow a user agent, assistive technology, or other tool provide an icon, or other identifier to help users with cognitive and learning disabilities know what content to put in the field. The actual autocompleting of the form field is a side benefit but was not the original intent of the criterion. The name of a field and the purpose can and often will be different for various reasons.

I'd suggest that you log an issue on the github repository for WCAG with what you think would help clarify this in the understanding documents of WCAG 2.1

Best Regards,

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
<EMAIL REMOVED>
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.