Experimental Design - Address Validation Pattern Request

[carly-yamrus]

What

We wish to create or add updates to the current address validation pattern using VETS360 to validate inputted user addresses and check against USPS address data. The address validation pattern will determine if the address entered is correct or offer an alternative address that is a better match. The purpose is to collect accurate data, helping Veteran’s and their family to access their benefits quickly and easily.

Purpose

The client states NCSO agents receive inaccurate address data and responses from applicants without correct address validation implemented. Incorrect data must be manually edited, which is time consuming, causing delays for Veterans and their families waiting for a determination of eligibility from the VA.

Usage

Many VA.gov forms require users to input mailing address information for themselves, or on behalf of someone else. An example where this new feature would be used, is if the user is entering their own personal address under the applicant information section.

Behavior

The user inputs the desired address and clicks continue. New functionality would require users to check the inputted address and decide which one they would like to use – the address that was entered, or a suggested address. If the inputted address is not a match to the U.S. Postal Service data, a warning appears that states “We can’t confirm the address you entered with the U.S. Postal Service. Check the address before continuing.” The user is able to go back and re-enter their information, or they can continue using the address that was entered, regardless of if it was validated or not. The functionality is similar if entered in the review section of the form. Users can edit their address, which takes them back into the form flow to check the address and validate it against U.S. Postal Service data. There aren’t any key considerations for mobile.

Examples

Figma Prototype: https://www.figma.com/proto/6ZBtsZJt7Llx1jA5rR8T83/Pre-Need---Address-Validation-Prototype?page-id=94%3A75077&node-id=785-139239&viewport=1594%2C2689%2C0.16&t=0rVsFSYs56EsUa4Z-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=785%3A139239

Accessibility

Necessary information for the user is moved inside the legend of the field set, accounting for screen readers.

Guidance

The pattern is carefully crafted, user friendly, and provides ease or use. When a user can’t confirm their address, the process includes ‘Check the address you entered’ warning alert with text describing how we can’t confirm the address. The user checks the address they entered with an address block, then we provide more context on why we couldn’t confirm the address.

Collaboration Cycle Ticket

Provide a link to your collaboration cycle ticket. https://github.com/department-of-veterans-affairs/va.gov-team/issues/70628

Your team

Memorials Self-Service

Research (optional)

Code (optional)

Next steps

We are requesting an asynchronous approval.

Submit requests to join an upcoming Design System Council meeting in #platform-design-system.

During the meeting, the Design System Council Working Group will evaluate the request and make a decision.

If your request is approved, you can add your component or pattern to the system. If you have any questions on how to add your component or pattern to the system, please reach out to the Design System Team at #platform-design-system.

[caw310]

@CareyCaldwell are you available Sept 5 at 11am ET to attend the DSC meeting?

[CareyCaldwell]

Hi Carol,

Was this meant for me?

I am available at that time - can you give me some information about what a DSC meeting is?

Carey 'Nick' Caldwell, (Contractor - BAM IV&V Services) Test Automation Engineer Sierra7, Inc. @.**@.>

From: Carol Wong @.> Sent: Wednesday, August 28, 2024 1:42 PM To: department-of-veterans-affairs/vets-design-system-documentation @.> Cc: Caldwell, Carey N., (Sierra7) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/vets-design-system-documentation] Experimental Design - Address Validation Pattern Request (Issue #3235)

@CareyCaldwellhttps://github.com/CareyCaldwell are you available Sept 5 at 11am ET to attend the DSC meeting?

- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/3235#issuecomment-2315925558, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUJ3MNMLLQSKNIKRZOXI7MTZTYDXZAVCNFSM6AAAAABNIN3EISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVHEZDKNJVHA. You are receiving this because you were mentioned.Message ID: @.***>

[caw310]

oops sorry, was meant for @carly-yamrus

[carly-yamrus]

Yes!

[humancompanion-usds]

Carol was on leave this week so just brief notes from me:

• We agreed that we want to bring this into the Design System once it is tested with users and we have their feedback.
• There are some issue to resolve around messaging when we cannot validate an address and the team will work with CAIA on that. It should be flagged for CAIA that there are similar message in VA.gov Profile and we should be consistent (which could mean updating messaging there).
• The team does plan to test with users in this form and the medallion burials form so more feedback and potentially iteration is forthcoming.
• The Design System team has an action item to consider allowing for HTML markup in the Radio Button - Tile variation to accommodate proper address formatting. This would mean allowing for a slot to be passed to the component.