Alert Sign-in - Development

[babsdenney]

Description

Build a web component of Alert - sign-in. Be sure to add analytics if necessary, see guidance.

Details

• Design documents: Alert - sign-in examples
• documentation: https://design.va.gov/components/alert/alert-sign-in/
• Alert Sign in Flow
• Documentation branch
• Related Ticket

  • 3239

  • 2556

  • 3133

• Review accessibility considerations added to component design ticket - https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/3385
• Review Design System Engineering Best Practices document

Tasks

• [ ] Review DST backlog for outstanding issues with this component, if necessary
• [ ] Create web component and add to Storybook
• [ ] Write any necessary tests
• [ ] Add Chromatic link to #[add accessibility ticket number] and request review from an accessibility specialist
• [ ] Contact designer for design review
• [ ] Display the appropriate maturity scale option in Storybook (once this feature is available)
  • If this is a new component that has not gone through Staging Review, it should be labeled "Use with Caution: Candidate"
• [ ] Merge component
• [ ] Create a new release of component-library
• [ ] Update component-library dependency in vets-design-system-documentation to get the updated component-docs.json
• [ ] Add analytics set-up to vets-website repository. See guidance here.

Acceptance Criteria

• [ ] Component is written and added to Storybook
• [ ] Component has had accessibility and design reviews
• [ ] Design.va.gov has the latest version of component-library
• [ ] Analytics has been configured for the component in the vets-website repo

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @Andrew565 @ataker @harshil1793 @it-harrison @jamigibbs @micahchiang @powellkerry @rsmithadhoc

[jamigibbs]

Should these button variations be created first before we can build this component?

[micahchiang]

• Is the value for ENTER TIME LIMIT based on the respondent burden listed on a given form, or the session timer for when a user is logged in?
• Start your form without signing in will need to be a dynamic link since this currently drops a user into a form specific workflow based on form URL.

[micahchiang]

To @jamigibbs's point regarding buttons. Are there use cases where these buttons exist outside of the sign in alert? We may want to consider creating those first and house that work in a separate ticket.

[caw310]

https://developers.id.me/brand-assets https://developers.login.gov/user-experience/sign-in-sign-out/

[caw310]

From Slack thread: Enter time limit is respondent burden = estimated total time it will take to fill out the form

[jamigibbs]

Is the value for ENTER TIME LIMIT based on the respondent burden listed on a given form, or the session timer for when a user is logged in?

Per Sara Sterkenburg: The respondent burden. It's the amount of time that a specific form will "save" the in progress data.

Start your form without signing in will it need to be a dynamic link since this currently drops a user into a form specific workflow based on form URL?

Per Sara Sterkenburg: Yes, definitely. That does need to be a conditional URL destination.