E-mail List Archives
Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose"
From: Patrick H. Lauke
Date: Nov 2, 2018 2:32PM
- Next message: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- Previous message: Judith Blankman: "Adobe Captivate accessibility"
- Next message in Thread: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- Previous message in Thread: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- View all messages in this Thread
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
- Next message: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- Previous message: Judith Blankman: "Adobe Captivate accessibility"
- Next message in Thread: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- Previous message in Thread: John Foliot: "Re: Dealing with ambiguous form fields when applying the new SC 1.3.5 Identify Input Purpose""
- View all messages in this Thread