Re: SC 1.3.4 - to keep or not?

Lisa,

This SC helps, or the autocomplete functionality itself (which already
exists in HTML)?

** katie **

*Katie Haritos-Shea*
*Principal ICT Accessibility Architect *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did,
but people will never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.

On Wed, Feb 21, 2018 at 12:27 PM, lisa.seeman <lisa.seeman@zoho.com> wrote:

> My 2 cents is that SC 1.3.4  should stay in the guidelines.
>
>  It helps users avoid making mistakes, which was one of our proposed SC's.
> This is a really good
>  technique for that, and helps with filling out forms a lot , making it
> easier and helping the user avoid errors.
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
>