- From: John Foliot <john.foliot@deque.com>
- Date: Fri, 12 Jan 2018 13:48:29 -0600
- To: James Nurthen <james.nurthen@oracle.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAKdCpxx5NunofRbY3oZj2Rw1Wzs5L0GUG-duJUC0UQLSbPaXaA@mail.gmail.com>
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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=zi_5QrA22csOImNNtL-_epqCl6yXNBLbnWBScjx_kG0&s=iulQV0_cQlIpMuyroT4Gy6P2fa--dCLF_astSzaanSc&e=> 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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=zi_5QrA22csOImNNtL-_epqCl6yXNBLbnWBScjx_kG0&s=iulQV0_cQlIpMuyroT4Gy6P2fa--dCLF_astSzaanSc&e=> 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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=ads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8&e=>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://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: 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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=ads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8&e=>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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=ads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8&e=>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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=ads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8&e=>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://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_awkawk&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=Qxho3T9BBrygeOOOCWGrt9L-je6YH_QAZGyWO2mqHWQ&s=OTHqZ8LWhSDOeIPMqCIDopKXBOGqKkCLK_-17tZ2Hmw&e=> > > > > *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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=ads5VC-C6Mfo8VQtlNIpurA-6cFvMk_w7Wi_opByeK8&e=>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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=J1p9aWiRzMnym7LcLkG_mij1WI7NLFKMIeUmfSHN0ag&e=>, > icons, and *regions* > <https://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=H3KufAkbM17cTqG2LWv-mPE52LpLK3XiZCSy1ijXIc8&e=>can > be programmatically determined. > > ( > *http://rawgit.com/w3c/wcag21/master/guidelines/index.html#identify-purpose* > <https://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=bom6ubPNq9uT0F6lnajB04YauyIQ6-0iip3V9s2RqN0&e=> > ) > > > > 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* <akirkpat@adobe.com> > > *http://twitter.com/awkawk* > <https://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=iTQ4dPkVbrNtmKyIDL_nEMJYTUyxZ1VMTYKpE73JneU&e=> > > > > *From: *Alastair Campbell <*acampbell@nomensa.com* <acampbell@nomensa.com> > > > * Date: *Friday, January 12, 2018 at 13:16 > * To: *Andrew Kirkpatrick <*akirkpat@adobe.com* <akirkpat@adobe.com>> > * Cc: *WCAG <*w3c-wai-gl@w3.org* <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://urldefense.proofpoint.com/v2/url?u=https-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&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=-tGRnd0O2NeyJOdIqJyQWFXmkvidfIdbh1qC5CLQd4w&s=NBGAZu9rUhiMjxWAT9TcJorMhpD_2B66bg6sxoll_I4&e=> > > > > -Alastair > > > -- > Regards, James > > <http://www.oracle.com> 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 > Oracle Corporate Architecture > 500 Oracle Parkway | Redwood City, CA 94065 > <https://maps.google.com/?q=500+Oracle+Parkway+%7C+Redwood+City,+CA+94065&entry=gmail&source=g> > <http://www.oracle.com/commitment> 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
Received on Friday, 12 January 2018 19:48:56 UTC