W3C home > Mailing lists > Public > public-personalization-tf@w3.org > June 2019

Re: Missing auto-complete values

From: Steve Lee <stevelee@w3.org>
Date: Tue, 4 Jun 2019 08:11:30 +0100
To: public-personalization-tf@w3.org
Message-ID: <70d8934a-cb88-bef9-4701-0f95b8438e3e@w3.org>

On 03/06/2019 18:46, Charles LaPierre wrote:
 > For completeness we should include impp but do you all think it's a 
good idea?  I myself would vote not to include it but will go with the 
majority on this one.

It seems to me rather limited in scope given the wide range of social 
networks in use these days. Almost an anachronism. But I guess if we 
feel a strong need to be in sync with the HTML 5.2 spec we should 
include it.

So I'm 0-

Steve

> Hello everyone,
> I was tasked today to go through all the HTML5 auto-complete values 
> <https://www.w3.org/TR/WCAG21/#input-purposes> and make sure we weren’t 
> missing any from our specification.
> Here are the ones which I found were missing:
> 
>   * *organization-title* - Job title (e.g., "Software Engineer", "Senior
>     Vice President", "Deputy Managing Director”)
>   * *username* - A username
>   * *new-password* - A new password (e.g., when creating an account or
>     changing a password)
>   * *current-password* - The current password for the account identified
>     by the *username* field (e.g., when logging in)
>   * We currently have “org” should be renamed as *organization* -
>     Company name corresponding to the person, address, or contact
>     information in the other fields associated with this field
>   * We currently have “city” should be replaced by the following:
>       o *address-level4* - The most fine-grained administrative level,
>         in addresses with four administrative levels
>       o *address-level3* - The third administrative level, in addresses
>         with three or more administrative levels
>       o *address-level2* - The second administrative level, in addresses
>         with two or more administrative levels; in the countries with
>         two administrative levels, this would typically be the city,
>         town, village, or other locality within which the relevant
>         street address is found
>       o *address-level1* - The broadest administrative level in the
>         address, i.e., the province within which the locality is found;
>         for example, in the US, this would be the state; in Switzerland
>         it would be the canton; in the UK, the post town
>   * We currently have “country” we should change the definition and add
>     the following:
>       o *country* - Country code
>       o *country-name* - Country name
>   * We currently have “postalcode” we should update the value and
>     definition as:
>       o *postal-code* - Postal code, post code, ZIP code, CEDEX code (if
>         CEDEX, append "CEDEX", and the /dissement/, if relevant, to the
>         *address-level2* field)
>   * *cc-given-name* - Given name as given on the payment instrument (in
>     some Western cultures, also known as the /first name/)
>   * *cc-additional-name* - Additional names given on the payment
>     instrument (in some Western cultures, also known as /middle names/,
>     forenames other than the first name)
>   * *cc-family-name* - Family name given on the payment instrument (in
>     some Western cultures, also known as the /last name/ or /surname/
>   * *tel-local-prefix* - First part of the component of the telephone
>     number that follows the area code, when that component is split into
>     two components
>   * *tel-local-suffix* - Second part of the component of the telephone
>     number that follows the area code, when that component is split into
>     two components
>   * *impp* - URL representing an instant messaging protocol endpoint
>     (for example, "*aim:goim?screenname=example*" or
>     "*xmpp:fred@example.net*”) 
> 
> For completeness we should include impp but do you all think it's a good 
> idea?  I myself would vote not to include it but will go with the 
> majority on this one.
> 
> 
> 
> Thanks
> EOM
> Charles LaPierre
> Technical Lead, DIAGRAM and Born Accessible
> Twitter: @CLaPierreA11Y
> Skype: charles_lapierre
> 
> 
Received on Tuesday, 4 June 2019 07:11:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:59 UTC