WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.1 SC 1.3.5 Identify Input Purpose - Testing Methodology

for

From: Isabel Holdsworth
Date: Sep 26, 2018 2:05AM

Wow! My interpretation of this contentious subject is that if a form
element has a type that uniquely describes the required input (email,
tel, password, etc), and there's only one field of each type in the
form, this would be enough to identify its purpose programmatically.
But that if more complex data such as a street address is being
captured, autocomplete might be the only way of making each field
programmatically determinable.

It'll be interesting to see how the Understanding document mutates.

On 25/09/2018, glen walker < <EMAIL REMOVED> > wrote:
> If you have a couple of hours, read the discussion on this topic from July.
>
> "WCAG 2.1 - 1.3.5 - How to capture a violation?" -
> https://webaim.org/discussion/mail_thread?thread=8864
> > > > >