Re: Possible wording for 1.3.4?

Hi Josh,

This does not address the concern brought forward by James. Imagine if you
will an online HR document that collects names and addresses: we don't want
each"line" of name and address auto-populated with the same data; the form
is actually looking for multiple names (and in some instances those names
would not likely include the actual name of the end-user data-entry clerk),
so tying these back to the individual affected user is critical. That said,
happy for further wordsmithing towards brevity and clarity.

JF

On Fri, Jan 12, 2018 at 2:29 PM, Joshue O Connor - InterAccess <
josh@interaccess.ie> wrote:

> I also like Jasons/Mike Gs wording, but I'm not really a fan of the
> 'corresponding to the user' bit and think that should go into the
> Understanding documentation:
>
> "    For content implemented using technologies that support specifying
> the purpose of form input fields, the purpose of each such supported field
> can be programmatically determined."
>
> reads clearer to me, thoughts?
>
> Thanks
>
> Josh
>
>
>
>
>
>
>    - For content implemented using technologies that support specifying
>    the purpose of specific types ofform input fields, the purpose of each such
>     *supported *field corresponding to the user can be programmatically
>    determined.
>
>
>
> White, Jason J wrote:
>
> The second version below is indeed better than the first.
>
>
>
> *From:* Michael Gower [mailto:michael.gower@ca.ibm.com
> <michael.gower@ca.ibm.com>]
> *Sent:* Friday, January 12, 2018 3:01 PM
> *To:* John Foliot <john.foliot@deque.com> <john.foliot@deque.com>
> *Cc:* James Nurthen <james.nurthen@oracle.com> <james.nurthen@oracle.com>;
> WCAG <w3c-wai-gl@w3.org> <w3c-wai-gl@w3.org>
> *Subject:* Re: Possible wording for 1.3.4?
>
>
>
> Yep, oversight. Here is Jason's version with a similar phrase put in.
>
>    - 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 *corresponding to the user* can be
>    programmatically determined.
>
>
> I was also wondering if we can tweak this to make it a tad less wordy...
>
>    - For content implemented using technologies that support specifying
>    the purpose of specific types ofform input fields, the purpose of each such
>     *supported *field corresponding to the user can be programmatically
>    determined.
>
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        John Foliot <john.foliot@deque.com>
> To:        James Nurthen <james.nurthen@oracle.com>
> Cc:        WCAG <w3c-wai-gl@w3.org>
> Date:        2018-01-12 11:49 AM
> Subject:        Re: Possible wording for 1.3.4?
> ------------------------------
>
>
>
>
> Good catch James - not forgotten, but things are moving quickly here
> <smile>.  How about:
>
> 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%3DDwMFaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3Dzi_5QrA22csOImNNtL-_epqCl6yXNBLbnWBScjx_kG0%26s%3DiulQV0_cQlIpMuyroT4Gy6P2fa--dCLF_astSzaanSc%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=mbMarDCnu%2BuBs1VTw%2F3z7XvtS%2BfRkVtdBs%2F%2FwuVKUPw%3D&reserved=0> directly
> related to the user, the meaning of the input field can be
> programmatically determined.
>
> ​(or, and I am not a huge fan of this one, but can live with it...):
>
> 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%3DDwMFaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3Dzi_5QrA22csOImNNtL-_epqCl6yXNBLbnWBScjx_kG0%26s%3DiulQV0_cQlIpMuyroT4Gy6P2fa--dCLF_astSzaanSc%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=mbMarDCnu%2BuBs1VTw%2F3z7XvtS%2BfRkVtdBs%2F%2FwuVKUPw%3D&reserved=0>
>  directly related to the user,  the meaning of the input field can be
> programmatically determined.
>
> ​JF​
> ​
>
> On Fri, Jan 12, 2018 at 1:40 PM, James Nurthen <james.nurthen@oracle.com>
> wrote:
> Both of these below have lost the fact that this only pertains to
> information about the user. If I am forced to use the autocomplete
> attribute on fields about employees (for example) in an HR application -
> that will make the usability of that application far worse as the browser
> will keep on prompting me for autocomplete suggestions for data pertaining
> to someone else.
>
> On 1/12/2018 11:27 AM, Michael Gower wrote:
> 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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=uWeYmd%2BA%2BaY6B9QRfx0PkqWsGlhp6OQOLLANzmJFuuc%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
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__maps.google.com_-3Fq-3D1803-2BDouglas-2BStreet-2C-2BVictoria-2C-2BBC-2B-25C2-25A0V8T-2B5C3-26entry-3Dgmail-26source-3Dg%26d%3DDwMFaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D0LCxYH9fWb6MqIIHnTJcRVHBCWvmywGyJfNj4cLg-7w%26s%3DoSHGvjmGprvprW3Ne4HZH1Ti0_lId8OFKC0sKQjt5hY%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=djgonc%2BKTewBdZWJ4pjnGmvVHHgPvupfzqnvR20YxS0%3D&reserved=0>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 <%28250%29%20220-1146>* cel: (250) 661-0098
> <%28250%29%20661-0098>*  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com> <akirkpat@adobe.com>
> To:        "Alex Li (CELA)" <alli@microsoft.com> <alli@microsoft.com>,
> Alastair Campbell <acampbell@nomensa.com> <acampbell@nomensa.com>
> Cc:        WCAG <w3c-wai-gl@w3.org> <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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=uWeYmd%2BA%2BaY6B9QRfx0PkqWsGlhp6OQOLLANzmJFuuc%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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=uWeYmd%2BA%2BaY6B9QRfx0PkqWsGlhp6OQOLLANzmJFuuc%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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=uWeYmd%2BA%2BaY6B9QRfx0PkqWsGlhp6OQOLLANzmJFuuc%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
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__twitter.com_awkawk%26d%3DDwMGaQ%26c%3DRoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE%26r%3DCIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I%26m%3DQxho3T9BBrygeOOOCWGrt9L-je6YH_QAZGyWO2mqHWQ%26s%3DOTHqZ8LWhSDOeIPMqCIDopKXBOGqKkCLK_-17tZ2Hmw%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=PMsr157nEEeDRxpyj7639eTu1b6Q7Upjo2i3Pe%2FoeD4%3D&reserved=0>
>
>
>
> *From: *Alex Li <alli@microsoft.com> <alli@microsoft.com>
> * Date: *Friday, January 12, 2018 at 13:54
> * To: *Andrew Kirkpatrick <akirkpat@adobe.com> <akirkpat@adobe.com>,
> Alastair Campbell <acampbell@nomensa.com> <acampbell@nomensa.com>
> * Cc: *WCAG <w3c-wai-gl@w3.org> <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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=uWeYmd%2BA%2BaY6B9QRfx0PkqWsGlhp6OQOLLANzmJFuuc%3D&reserved=0>is
> used, the meaning of the equivalent input fields can be programmatically
> determined.
>
>
>
> *From:*Andrew Kirkpatrick [mailto:akirkpat@adobe.com <akirkpat@adobe.com>]
>
> * Sent:* Friday, January 12, 2018 10:26 AM
> * To:* Alastair Campbell <acampbell@nomensa.com> <acampbell@nomensa.com>
> * Cc:* WCAG <w3c-wai-gl@w3.org> <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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=JmsWAOv6MF4Fduekx4RryO5sxinADanTiq0Vipuoxqw%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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=wdprhfNR3NKaa7xRIRNFK5b0lppfdAhcqT5pqwi4akk%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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=SVRbbvGUMGg4TaoyDcli8o2ZmtgqaEvYyIrLYxg6ra8%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
>
> 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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=9BGRxbC6cn4nJT2g2cg5qdHKjljC7GUlTJNT8vH863E%3D&reserved=0>
>
>
>
> *From: *Alastair Campbell <acampbell@nomensa.com>
> * Date: *Friday, January 12, 2018 at 13:16
> * To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> * Cc: *WCAG <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%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=HWL4IbPbiTeInxloYDb%2FTSutUo6XAPwhd7f2Hwe6BeQ%3D&reserved=0>
>
>
>
> -Alastair
>
>
>
>
> --
> Regards, James
> James Nurthen | Accessibility Architect
> Phone: +1 650 506 6781 <+1%20650%20506%206781>| Mobile: +1 415 987 1918
> <+1%20415%20987%201918>| Video: james.nurthen@oracle.com
> OracleCorporate Architecture
> 500 Oracle Parkway | Redwood City, CA 94065
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__maps.google.com_-3Fq-3D500-2BOracle-2BParkway-2B-257C-2BRedwood-2BCity-2C-2BCA-2B94065-26entry-3Dgmail-26source-3Dg%26d%3DDwMFaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3D0LCxYH9fWb6MqIIHnTJcRVHBCWvmywGyJfNj4cLg-7w%26s%3DxoyPW5D_15xGuzCO977l3in4z0KI1V7a12G6nRA-xQM%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C13adef66cf1947b0cfd808d559f74c34%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636513841023545042&sdata=ReVPzCCafxMfPozYNAxfcXLuDzgyjFCDAik9K1HE8A8%3D&reserved=0>
> Oracle is committed to developing practices and products that help protect
> the environment
>
>
>
> --
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> john.foliot@deque.com
>
> Advancing the mission of digital accessibility and inclusion
>
>
> ------------------------------
>
> 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.
> ------------------------------
>
>
> --
> Joshue O Connor
> Director | InterAccess.ie
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion