Re: Created branch with proposed wording for 1.3.4

This is a massive change and I don’t think that it will fly. My concerns:


  1.  The SC is scope to input controls, not controls writ large.
  2.  The SC discussion has been about scoping this to information about the user. James raised the very valid point for situations like in an HR tool where there are many first name/last name/etc fields.

In a WCAG 2.2 we can expand the list of input controls without a problem with backward compatibility, and if we can expand beyond input controls then we can add another SC that does that.

I don’t think that the SC is strengthened by making it more general, it will make it more confusing and less likely to pass into CR.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: David MacDonald <david@can-adapt.com>
Date: Wednesday, January 17, 2018 at 08:46
To: Alastair Campbell <acampbell@nomensa.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Created branch with proposed wording for 1.3.4
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Wednesday, January 17, 2018 at 08:45

PS I'm training all day today... so will just check in on breaks.... can we rally around this and make any tweaks as necessary today?

... especially check the definition in the Branch
 which pulls in HTML 5.2

http://rawgit.com/w3c/wcag21/1.3.4_autofill_david/guidelines/#identify-common-purpose<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2F1.3.4_autofill_david%2Fguidelines%2F%23identify-common-purpose&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=%2FeP%2BgKKpZO60LXg1pVivwDhRXYl3Rxl7dtKITZL6WIc%3D&reserved=0>

Feel free to edit the Branch as necessary, if I'm not answering quickly...

Cheers,
David MacDonald



CanAdapt Solutions Inc.
Mobile:  613.806.9005

LinkedIn
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=Z9J%2FVOYbQ%2Fz2%2FXgk3Sr8Pc9bIh8s8EhG%2FTdKr7TKdbs%3D&reserved=0>

twitter.com/davidmacd<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=fW3%2FiUDppLNODRa%2F5ee9u8yvh8kG%2F1ObzWAC%2FYvkSRU%3D&reserved=0>

GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=izkTuFVJUvHBLkkhfO1kc%2FgTK3bYH2sgNX9pho9jp%2Fk%3D&reserved=0>

www.Can-Adapt.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=wJtz9CbC%2FJJ4G1Fc5fysThR5cq4vaQMcDN2PCFA4J2s%3D&reserved=0>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=uCF%2Ffs6hM7pWOgDWLEBch7yRTWcnxJ4cqNwbTjBLldE%3D&reserved=0>

On Wed, Jan 17, 2018 at 8:42 AM, David MacDonald <david@can-adapt.com<mailto:david@can-adapt.com>> wrote:
sure... fixed in Branch

http://rawgit.com/w3c/wcag21/1.3.4_autofill_david/guidelines/#identify-common-purpose<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2F1.3.4_autofill_david%2Fguidelines%2F%23identify-common-purpose&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=%2FeP%2BgKKpZO60LXg1pVivwDhRXYl3Rxl7dtKITZL6WIc%3D&reserved=0>


Cheers,
David MacDonald



CanAdapt Solutions Inc.
Mobile:  613.806.9005<tel:(613)%20806-9005>

LinkedIn
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=Z9J%2FVOYbQ%2Fz2%2FXgk3Sr8Pc9bIh8s8EhG%2FTdKr7TKdbs%3D&reserved=0>

twitter.com/davidmacd<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=fW3%2FiUDppLNODRa%2F5ee9u8yvh8kG%2F1ObzWAC%2FYvkSRU%3D&reserved=0>

GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=izkTuFVJUvHBLkkhfO1kc%2FgTK3bYH2sgNX9pho9jp%2Fk%3D&reserved=0>

www.Can-Adapt.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=wJtz9CbC%2FJJ4G1Fc5fysThR5cq4vaQMcDN2PCFA4J2s%3D&reserved=0>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7Cakirkpat%40adobe.com%7Ce1e8643fbc1641ad2a4808d55db0ae4b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517935779603396&sdata=uCF%2Ffs6hM7pWOgDWLEBch7yRTWcnxJ4cqNwbTjBLldE%3D&reserved=0>

On Wed, Jan 17, 2018 at 8:35 AM, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
Looking good, the ‘true’ aspect doesn’t seem very WCAG though?

The purpose of common interface components can be programmatically determined when:
​- ​ The content is implemented using technologies that support identifying the expected purpose for interface components, and
​- ​ The Interface component has a purpose that maps to the list of ​[internal link] ​ common interface components

…

-Alastair


From: David MacDonald <david@can-adapt.com<mailto:david@can-adapt.com>>
Date: Wednesday, 17 January 2018 at 13:31
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>, WCAG Editors <team-wcag-editors@w3.org<mailto:team-wcag-editors@w3.org>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, "Abma, J.D. (Jake)" <Jake.Abma@ing.nl<mailto:Jake.Abma@ing.nl>>, Detlev Fischer <detlev.fischer@testkreis.de<mailto:detlev.fischer@testkreis.de>>, Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
Subject: Created branch with proposed wording for 1.3.4

The purpose of common interface components can be programmatically determined if the following are true:
​- ​
 The content is implemented using technologies that support identifying the expected purpose for interface components
​- ​
 The Interface component has a purpose that maps to the list of
​[internal link] ​
 common interface components