Re: Street Addresses

Hi Lionel,

FWIW, as I recall the token values are based initially from the HTML 5
spec:
https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute

Those values are also replicated in WCAG 2.1, Section 7, found here:
https://www.w3.org/TR/WCAG21/#input-purposes

So, when proposing that attribute value in the Module, we simply re-used
the existing values. I agree we should monitor the WHAT WG discussion
closely, as it MAY impact our spec (and potentially WCAG as well).

JF

On Tue, Aug 23, 2022 at 7:40 AM Lionel Wolberger <lionel@userway.org> wrote:

> Hi Adapt TF:
>
> I ran into a very current discussion about addresses and autofill. It
> suggests that our address-level names may not be the most up-to-date best
> practice to support all cultures.
>
> In https://www.w3.org/TR/adapt-content/#description-1 we support four
> administrative levels:
>
>    - - 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.
>    - - 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.
>    - - address-level3: The third administrative level, in addresses with
>    three or more administrative levels.
>    - - address-level4: The most fine-grained administrative level, in
>    addresses with four administrative levels.
>
> A lengthy discussion of the limitations of autocomplete here (
> https://github.com/whatwg/html/issues/4986) led to Dominic Battre
> proposing a  "street-address" that includes new lines, and "address-line1,
> 2, 3" to follow on. His proposal is here,
> https://github.com/battre/autocomplete-attribute-explainer/tree/main
>
> Was this robust discussion taken into account when we settled on "level 1,
> level2" etc.? Shall we open the door to discussion about this while we are
> entering candidate review?
>
> - Lionel
>
> [image: Lionel Wolberger]
> <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>
> Lionel Wolberger
> COO, UserWay Inc.
> [image: UserWay.org]
> <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
> [image: Phone Icon] +1 (415) 800-4557 <+14158004557>
> [image: Envelope Icon]
> lionel@userway.org <lionel@userway.org>
> [image: Schedule with Me]
> <https://userway.org/s/lionel?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
> Important Reads: Accessibility and SEO Impact
> <https://userway.org/blog/the-impact-of-accessibility-on-seo/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>  & Accessibility Tax Credits
> <https://userway.org/blog/everything-you-need-to-know-about-web-accessibility-tax-benefits/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger>
>
>

-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"