Re: Created branch with proposed wording for 1.3.4

Here's the language of both the specific version (Andrew) and the generic
version (Alastair, etc...)


​=======
T​
he meaning of each user-specific input field can be programmatically
determined when:

​     -​
The content is implemented using technologies that support identifying the
expected meaning for form input data; and
​     -​
The input field has a meaning that maps to the HTML 5.2 Autofill field names

=========
The purpose of common user interface components can be programmatically
determined when:

     ​- ​
The content is implemented using technologies that support identifying the
expected purpose for user interface components, and
​     - ​
The Interface component has a purpose that maps to the list of common user
interface components

​=======
Links to github​

http://rawgit.com/w3c/wcag21/1.3.4_autofill_david/
guidelines/#identify-common-purpose
http://rawgit.com/w3c/wcag21/1.3.4_autofill_david-2/
guidelines/#identify-common-purpose

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Mobile:  613.806.9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Wed, Jan 17, 2018 at 12:29 PM, David MacDonald <david@can-adapt.com>
wrote:

> I've put up 2 versions.... one that has Andrew's wording from yesterday
> with "meaning" and "user-specific input field" and links to HTML 5.2
>
> http://rawgit.com/w3c/wcag21/1.3.4_autofill_david/
> guidelines/#identify-common-purpose
>
> and one with the more generic "purpose" and "user interface component"
> that links internally to a list.
>
> http://rawgit.com/w3c/wcag21/1.3.4_autofill_david-2/
> guidelines/#identify-common-purpose
>
>
> I'm fine with either.
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
> Mobile:  613.806.9005 <(613)%20806-9005>
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *  Adapting the web to all users*
> *            Including those with disabilities*
>
> If you are not the intended recipient, please review our privacy policy
> <http://www.davidmacd.com/disclaimer.html>
>
> On Wed, Jan 17, 2018 at 11:55 AM, Alastair Campbell <acampbell@nomensa.com
> > wrote:
>
>> Ach, I’m sorry I mentioned it now, being in a 6-hour meeting made me very
>> talkative on WCAG matters somehow.
>>
>>
>>
>>
>>
>> > Danger, WIll Robinson! That would seem to put us in the very
>> unfortunate situation where someone depending on the name attribute
>> conveying meaning will now be getting incorrect conversions happening.
>>
>>
>>
>> They could get too many, yes. However, if they started using the
>> attributes due to WCAG, that is an unlikely outcome AND it would cause
>> issues with basic usability.
>>
>>
>>
>> We are talking about general browser functionality, so **everyone**
>> (with autofill turned on) would get their name filled in!
>>
>>
>>
>> Cheers,
>>
>>
>>
>> -Alastair
>>
>
>