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 of form 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
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 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​
 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 namesthe 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
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Andrew Kirkpatrick <akirkpat@adobe.com>
To:        "Alex Li (CELA)" <alli@microsoft.com>, Alastair Campbell 
<acampbell@nomensa.com>
Cc:        WCAG <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 namesis 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 namesthe 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 namesthe 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

 
From: Alex Li <alli@microsoft.com>
Date: Friday, January 12, 2018 at 13:54
To: Andrew Kirkpatrick <akirkpat@adobe.com>, Alastair Campbell 
<acampbell@nomensa.com>
Cc: WCAG <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 namesis 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>
Cc: WCAG <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, icons, and regionscan be programmatically 
determined.
(
http://rawgit.com/w3c/wcag21/master/guidelines/index.html#identify-purpose

)
 
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

 
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

 
-Alastair


-- 
Regards, James 
James Nurthen | Accessibility Architect
Phone: +1 650 506 6781 | Mobile: +1 415 987 1918 | Video: 
james.nurthen@oracle.com 
Oracle Corporate Architecture
500 Oracle Parkway | Redwood City, CA 94065 
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