Enable browser autocomplete on user's own address fields

[gcamacho079]

Description

Enable autocomplete for most address fields for user’s own address (not other user addresses), the exception being selectize fields. (@brandonkelly would this be a good opportunity to un-selectize locale/address fields entirely, or save that for a later release?)

This PR — specifically the getInputPurpose method — will also help achieve WCAG 2.1 AA compliance in Console, as we can use it to set input purposes on the billing address fields.

Related issues

Resolves ACC-42

[linear]

CLD-121 Payment method address fields don't use appropriate autocomplete values

Page Area:

Billing - payment method modal

Issue Description:

Address inputs use user information, but don't use autocomplete values that would assist in user input. This includes:

• Full name
• Country
• Address Line 1
• Address Line 2
• Postal Code
• Province
• City
• And other regional address fields

Action:

Use autocomplete values specified in Input Purposes for User Interface Components

Screenshot/Code Snippet:

N/A

craftnet/controllers/console/AddressesController.php

[linear]

ACC-42 city

[brandonkelly]

This PR — specifically the getInputPurpose method — will also help achieve WCAG 2.1 AA compliance in Console, as we can use it to set input purposes on the billing address fields.

Feels a little sketchy to be relying on that method on front ends. Couldn’t the Console UI be setting its own autocomplete values?

[gcamacho079]

Feels a little sketchy to be relying on that method on front ends. Couldn’t the Console UI be setting its own autocomplete values?

I’ll need to refresh myself on why I went this route and see if that alternative makes more sense. Will get back to you on this shortly!

[gcamacho079]

@brandonkelly moved that method to Cp and made the other methods private and static. What are your thoughts about un-selectizing the other fields (country, state, etc.) in the address forms?

[brandonkelly]

I think we should keep Selectize there until we have a better alternative (like the disclosure menu with a search input + inline list, like we talked about). Until then, it does make working with very large selects a lot more manageable.

[gcamacho079]

I think we should keep Selectize there until we have a better alternative (like the disclosure menu with a search input + inline list, like we talked about). Until then, it does make working with very large selects a lot more manageable.

Ok! I’ve been working on a mockup/wireframe for this in Figma, trying to think through the a11y UX; I’ll aim to have something concrete by Monday.

[linear]

CLD-121 Payment method address fields don't use appropriate autocomplete values