Cleanup in modules to match updated auto-complete harmonization

Question

Cleanup in modules to match updated auto-complete harmonization

clapierre opened this issue 5 years ago · 4 comments

we changed from camelCase to hyphens and harmonized with HTML auto-complete values.
We need to make sure all our examples throughout the 3 modules and explainer all match:

Eg: In Module 1 we have:

The purpose values that would typically be on form controls should provide context for the user. For example tel would relate to the user's telephone number. Note that there is no default value and there can be more than one value for a field, such as data-purpose="country postcode" which includes both the country and postal code.

This should be
such as data-purpose="country-name postal-code" which includes both the country and postal code.

Answer 1 · 2019-06-18T13:17:23.000Z

List of possible Values are also incorrect as they do not match the new hyphenated names
3.1.3, 3.2.4, and 3.3.4
IE:
We are also missing the new auto-complete values
ie
address-level1, 2, 3, 4 etc.

Answer 2 · 2019-06-19T09:04:16.000Z

Hi Charles, I did those things in the autocomplete branch, do you need me to pull request for this branch now or after we go through all of values?

Answer 3 · 2019-06-19T14:14:24.000Z

Hi All, Can we add the following to a meeting agenda to discuss? Charles wrote: *The purpose values that would typically be on form controls should provide context for the user. For example tel would relate to the user's telephone number. Note that there is no default value and there can be more than one value for a field, such as data-purpose="country postcode" which includes both the country and postal code.* *This should besuch as data-purpose="country-name postal-code" which includes both the country and postal code.* This is new for me - "overloading" the attribute, or letting the attribute take more than one value. I'm not 100% sure this is a wise choice, as it is rare to find an input that wants multiple pieces of information like this in the wild, especially the types of personal information that the current values represent (your address, your email, your telephone). TOPIC: Should those attributes that take a fixed taxonomy term also allow for space separated (or comma separated) values for that attribute? Thanks. JF

…

On Tue, Jun 18, 2019 at 8:08 AM Charles LaPierre ***@***.***> wrote: In our new updated sortable table <https://raw.githack.com/w3c/personalization-semantics/rewrite-prototype/content/index.html#values> we changed from camelCase to hyphens and harmonized with HTML auto-complete values. We need to make sure all our examples throughout the 3 modules and explainer all match: Eg: In Module 1 we have: The purpose values that would typically be on form controls should provide context for the user. For example tel would relate to the user's telephone number. Note that there is no default value and there can be more than one value for a field, such as data-purpose="*country postcode*" which includes both the country and postal code. This should be such as data-purpose="*country-name postal-code*" which includes both the country and postal code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#125>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJL443SAW6Y2MCV2VXPW3TP3DM5JANCNFSM4HY74ATA> .

-- *John Foliot* | Principal Accessibility Strategist | W3C AC Representative Deque Systems - Accessibility for Good deque.com

Answer 4 · 2019-06-19T14:31:40.000Z

Good point John, I was just matching our current values to the examples but it does tease out that our examples did have multiple terms. I am sure there are better examples where two values may make sense but do we want to go there or not is the question. I will be on PTO for the next 3 Mondays so looking forward to reading the minutes to see what you all decide. Thanks EOM Charles LaPierre Technical Lead, DIAGRAM and Born Accessible Twitter: @CLaPierreA11Y Skype: charles_lapierre On Jun 19, 2019, at 7:14 AM, John Foliot <notifications@github.com<mailto:notifications@github.com>> wrote: Hi All, Can we add the following to a meeting agenda to discuss? Charles wrote: *The purpose values that would typically be on form controls should provide context for the user. For example tel would relate to the user's telephone number. Note that there is no default value and there can be more than one value for a field, such as data-purpose="country postcode" which includes both the country and postal code.* *This should besuch as data-purpose="country-name postal-code" which includes both the country and postal code.* This is new for me - "overloading" the attribute, or letting the attribute take more than one value. I'm not 100% sure this is a wise choice, as it is rare to find an input that wants multiple pieces of information like this in the wild, especially the types of personal information that the current values represent (your address, your email, your telephone). TOPIC: Should those attributes that take a fixed taxonomy term also allow for space separated (or comma separated) values for that attribute? Thanks. JF

…

On Tue, Jun 18, 2019 at 8:08 AM Charles LaPierre ***@***.******@***.***>> wrote: In our new updated sortable table <https://raw.githack.com/w3c/personalization-semantics/rewrite-prototype/content/index.html#values> we changed from camelCase to hyphens and harmonized with HTML auto-complete values. We need to make sure all our examples throughout the 3 modules and explainer all match: Eg: In Module 1 we have: The purpose values that would typically be on form controls should provide context for the user. For example tel would relate to the user's telephone number. Note that there is no default value and there can be more than one value for a field, such as data-purpose="*country postcode*" which includes both the country and postal code. This should be such as data-purpose="*country-name postal-code*" which includes both the country and postal code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#125>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJL443SAW6Y2MCV2VXPW3TP3DM5JANCNFSM4HY74ATA> .

-- *John Foliot* | Principal Accessibility Strategist | W3C AC Representative Deque Systems - Accessibility for Good deque.com<http://deque.com> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#125>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AB3A3LMP3TKDXBZNBKOYP7DP3I5MFANCNFSM4HY74ATA>.