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: John Foliot
Date: Nov 2, 2018 4:41PM

Hmmm... neither is SC 1.1.1 in terms of 'value' of the alt text.

We can certainly test to see if the input has @autocomplete, while still
debating which token value is most appropriate, ya?

JF


On Fri, Nov 2, 2018, 3:33 PM Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> On 02/11/2018 19:55, John Foliot wrote:
> >> 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?
> >
> > Hey Patrick,
> >
> > do as you would do <grin>. Obviously at this early stage, we have some
> > basic education required, so think of this as a teachable moment - fail
> or
> > not is your call, not mine.
>
> Doesn't sound like something that is unambiguously testable though, does
> it? ;)
>
> 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
> > > > >