Repalce custom access/verification alerts with new DS ones

[sterkenburgsara]

[BLOCKED as of 8/28, DS components are in Figma but not implemented]

Description

The account access and verification alerts content has been updated again, and should be updated to reflect the most accurate version.

User story

As a Cartography team member, I want to update our alerts to the most recent version so that we are communicating the current state to Veterans in the clearest and most accurate language possible.

Notes

• Source of truth for content is here
• Design system has added the finalized content into componentized alerts that (in theory) we should be able to grab! That file is here
  • Note: as of 8/28 these were not available in code (only in Figma). We plan to keep this ticket backlogged until they are available for use in the actual code. Sara sent a note to Design System Team (DST) to ask about planned timeline for implementation on 8/28/24. Will update ticket when we get a response.

Possible tasks:

• [ ] Remove custom alerts we created previously & leverage the new versions added to the VA Design System (VADS) for the same thing.

Acceptance criteria

• Alerts have been updated
• QA review
• A11y review

[wesrowe]

@sterkenburgsara, please help me understand the importance of this change – is the change significant?

[sterkenburgsara]

@wesrowe change is not wildly significant - biggest difference is some of these alerts will now be globally managed and available in components within the Design System (we don't have to manage custom versions of all alerts). We should retire our custom versions & leverage the VADS versions of the alerts that we can, and only manage custom alerts that are specific to My HealtheVet (not meaningful to all of VA.gov) on our own.

However, as of 8/28 we are realizing that VADS has them available via Figma, but they aren't available in code. We want to keep this backlogged until they are grabbable for devs.

[sterkenburgsara]

Update: @laurwill worked with Identity and figured out that there are specific URLs/buttons that allow a user to automatically go down the path of ID-verification, which will simplify several access alerts if we can get changes made. She is working with VADS to update the MHV "register with My HealtheVet" alert, which is the most straightforward one to update. Slack thread here.

Updating the other 2 alerts depends on feasibility of building a revised version of the sign-in modal (similar to what VAHB uses) that forces ID-verified authentication for any of the 4 options that a user might select when they choose to sign-in.

@laurwill is it okay to wait until VADS makes the update? Or should we first make these changes to our current custom alerts in My HealtheVet?