WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Jared Smith
Date: Jul 25, 2018 7:15AM

Jonathan -

The normative success criterion text does not require the autocomplete
attribute. It simply requires that the purpose of the field be
programmatically determined if it collects user information. While there is
a sufficient technique (which is non-normative) that allows you to meet
this SC by using the autocomplete attribute, this is not required - and
therefore it would not be a failure if autocomplete is not present in these
cases, so long as the purpose is programmatically identified with the field.

Of course 1.3.1 requires that the field information be programmatically
determined anyway, so 1.3.5 really just adds a SUGGESTION that you use
autocomplete, which does improve the user experience for those using form
fillers.

> The accessible name cannot be used to communicate the purpose

Why couldn't it? I see no suggestion from the normative text that the
accessible name could not be used. In fact, if you didn't use the
accessible name, then you'd likely fail 2.5.3.

Jared