RE: Possible wording for 1.3.4?

+1

From: Michael Gower [mailto:michael.gower@ca.ibm.com]
Sent: Friday, January 12, 2018 2:27 PM
To: Andrew Kirkpatrick <akirkpat@adobe.com>
Cc: Alastair Campbell <acampbell@nomensa.com>; Alex Li (CELA) <alli@microsoft.com>; WCAG <w3c-wai-gl@w3.org>
Subject: Re: Possible wording for 1.3.4?

The last version of that is the best of the three, I think. I can live with that. However, I still prefer Jason's that does not tie everyone to the 5.2 meanings. Here they are back to back:

  *   In content implemented using technologies with support for identifying the expected meaning for form input data, for each input field that has a purpose that maps to any of the HTML 5.2 Autofill field names<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DXRbdqxqP8ZK6sblYsmHoYOwbcLFZuiEs6zZ07udO-252Br4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=VD5IBmmCl7jtuz6pbJhwgBfNLynR4BCYr3g%2BetMsFUA%3D&reserved=0>the meaning of the input field can be programmatically determined.

  *   For content implemented using technologies that support specifying the purpose of specific types of form input fields, the purpose of each such field of a supported type can be programmatically determined.


Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
To:        "Alex Li (CELA)" <alli@microsoft.com<mailto:alli@microsoft.com>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc:        WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Date:        2018-01-12 11:13 AM
Subject:        Re: Possible wording for 1.3.4?
________________________________


I like that version Alex. A few tweaks in line with John’s:



In content implemented using technologies with support for autofilling form inputs and an equivalent input field as any of the HTML 5.2 Autofill field names<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DXRbdqxqP8ZK6sblYsmHoYOwbcLFZuiEs6zZ07udO-252Br4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=VD5IBmmCl7jtuz6pbJhwgBfNLynR4BCYr3g%2BetMsFUA%3D&reserved=0>is used, the meaning of the equivalent input fields can be programmatically determined.



Changed:

In content implemented using technologies with support for autofilling form inputs, for each input field that has a purpose that maps to any of the HTML 5.2 Autofill field names<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DXRbdqxqP8ZK6sblYsmHoYOwbcLFZuiEs6zZ07udO-252Br4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=VD5IBmmCl7jtuz6pbJhwgBfNLynR4BCYr3g%2BetMsFUA%3D&reserved=0>the meaning of the input field can be programmatically determined.



Or, to step away from “autofill” a bit:

In content implemented using technologies with support for identifying the expected meaning for form input data, for each input field that has a purpose that maps to any of the HTML 5.2 Autofill field names<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DXRbdqxqP8ZK6sblYsmHoYOwbcLFZuiEs6zZ07udO-252Br4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=VD5IBmmCl7jtuz6pbJhwgBfNLynR4BCYr3g%2BetMsFUA%3D&reserved=0>the meaning of the input field can be programmatically determined.







Thanks,

AWK



Andrew Kirkpatrick

Group Product Manager, Accessibility

Adobe



akirkpat@adobe.com<mailto:akirkpat@adobe.com>

http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=1tgOzYY95abml%2B6QV3LYwZ9JUEYuyE44jDsL8uWLfWk%3D&reserved=0>



From: Alex Li <alli@microsoft.com<mailto:alli@microsoft.com>>
Date: Friday, January 12, 2018 at 13:54
To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: RE: Possible wording for 1.3.4?



How about something like this?



In content implemented using technologies with support for autofilling form inputs and an equivalent input field as any of the HTML 5.2 Autofill field names<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DXRbdqxqP8ZK6sblYsmHoYOwbcLFZuiEs6zZ07udO-252Br4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=VD5IBmmCl7jtuz6pbJhwgBfNLynR4BCYr3g%2BetMsFUA%3D&reserved=0>is used, the meaning of the equivalent input fields can be programmatically determined.



From:Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Friday, January 12, 2018 10:26 AM
To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: Possible wording for 1.3.4?



If a company creates a tool that allows people to create web content they may be able to conform when the software is tested but that is a different date then for the person who builds content with it.



The suggestions are very much like 1.3.5:

In content implemented using markup languages, the purpose of User Interface Components<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fmaster-252Fguidelines-252Findex.html-2523dfn-2Duser-2Dinterface-2Dcomponents-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DaShpbJxNlVln6eAEUJg6nk8lPkPB-252BjdXstjbGKIILp4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3DJ1p9aWiRzMnym7LcLkG_mij1WI7NLFKMIeUmfSHN0ag%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=icC8yv8kqHJvQt4AMFxdFDZDobHOUgz71cBf%2FkQVegE%3D&reserved=0>, icons, and regions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fmaster-252Fguidelines-252Findex.html-2523dfn-2Dregions-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3Dk1pms5bzqxOapQWfkpzlGPeYKyudC-252BaHJjvKCQaBxRI-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3DH3KufAkbM17cTqG2LWv-mPE52LpLK3XiZCSy1ijXIc8%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=Kos4d0bjvtFIybKUtY8%2Fshd4oVxxL2DIcNKuUUqH0PI%3D&reserved=0>can be programmatically determined.

(http://rawgit.com/w3c/wcag21/master/guidelines/index.html#identify-purpose<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fmaster-252Fguidelines-252Findex.html-2523identify-2Dpurpose-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3Dm3MxLxENUGRWUi7Zr-252Fvv2uJp9Lqg4Wk8gDkTvNR7T-252Bs-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3Dbom6ubPNq9uT0F6lnajB04YauyIQ6-0iip3V9s2RqN0%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=Ibe%2FArd%2FNXsOgf11GnUD79dGE1R06Ufs1gfb5wc2d80%3D&reserved=0>)



in 1.3.4 we have tried to define a smaller, more testable set.



Thanks,

AWK



Andrew Kirkpatrick

Group Product Manager, Accessibility

Adobe



akirkpat@adobe.com<mailto:akirkpat@adobe.com>

http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257Cca969dfd8a4a4e21f6e408d559ede8cc-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513800714094670-26sdata-3DsYITmzrmcIzPXaBCJCP-252BsEUsnKXwY86bLKc48kfaISA-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3DiTQ4dPkVbrNtmKyIDL_nEMJYTUyxZ1VMTYKpE73JneU%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=%2BwUJJj2J5QAtaNm0qP7lhslVNjd0qYKsW4aFIFkhzh4%3D&reserved=0>



From: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Date: Friday, January 12, 2018 at 13:16
To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
Cc: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: Possible wording for 1.3.4?



AWK:

> If I use HTML in a “living standard” way today and include all of the appropriate meanings/purposes that are defined, but then HTML adds meanings, how will I be able to handle my conformance? I haven’t changed the site, but the list changes. We can’t leave that open-ended.



As per Michael’s email on the other thread: Conformance is at a particular date, so it’s the standard at the time.



This was one of the reasons that the W3C has tried to ‘version’ HTML though, so your conformance could also reference a specific version, e.g:

https://www.w3.org/TR/html52/sec-forms.html#autofill-field<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FTR-252Fhtml52-252Fsec-2Dforms.html-2523autofill-2Dfield-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C1a91d1adbbec4a5f136108d559e88c25-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636513777735429494-26sdata-3DKaptVuMMuXLmJ4IPdDuZTIRdkM9A6P0PPEjys0vUmiA-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w%26s%3DNBGAZu9rUhiMjxWAT9TcJorMhpD_2B66bg6sxoll_I4%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C89aa504088c24a3cd64908d559f2b64b%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513821330858393&sdata=hJi1fRwFP53tG8rK3a9KXTG2ISfb9LasOK0qstNAiQk%3D&reserved=0>



-Alastair


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________