WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose"

for

From: Patrick H. Lauke
Date: Nov 2, 2018 1:44PM

On 02/11/2018 18:30, John Foliot wrote:

> Having a dual-value input has some issues, however from the perspective of
> SC 1.3.5, I think we discussed that the page author could chose either of
> the values for the metadata attachment (i.e. you could use
> autocomplete="email" or autocomplete="username" in this use-case), and I
> would argue that the slightly better choice would be "username", simply
> because the spec also notes the following for the token term:

What if the author decides that that's not the correct /
all-encompassing semantic meaning of that field, and decides not to add
any autocomplete? Do we fail? Seems a tad harsh, based on "you didn't
boil down this multi-purpose field to only one of the autocomplete values".

P
--
Patrick H. Lauke

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