Link - Action Web Component - Development

[caw310]

Description

Build a web component of Link- Action. Be sure to add analytics if necessary, see guidance.

If this is a pattern or component that is already in existence, check the Design System Team backlog for outstanding issues. If you find any, link to them in a comment on this ticket. If possible, address any outstanding issues with this new version and link to this issue from the original issue. If not, indicate that in the original issue.

Details

• Design documents: [Figma]
• Review accessibility considerations added to component design ticket (if any)
• 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 @nickjg231 @powellkerry @rmessina1010 @rsmithadhoc

[jilladams]

@caw310 Question for you: our team has a ticket we're holding on until this one is completed ([V1 & 3 Components] Implement available components for Income Limits #17276). Looks like this ticket had been planned, but is now back in considering prioritization -- do you have a sense of when this may be possible to get prioritized? (cc @randimays @davidconlon @FranECross )

[caw310]

@jilladams this is scheduled to be worked on in mid-April. We moved it out a few sprints as we have other higher priority work.

[randimays]

Adding here that we will need to add a white action link version for dark backgrounds, please! Screenshot from the homepage hero banner.

[caw310]

We are swapping this ticket and moving it to the next sprint to work on 2676

[humancompanion-usds]

Just a head's up that the a11y CoP and I are designing, and plan to test, a revision to the primary Link - Action that will solve for making the primary link stand out in a sea of text. That experimental issue is here. I mention it just so you can look at it before coding so that we leave room for what the eventual implementation could be. In other words, we'll likely want to create a va-link-action rather than extending va-link as the design may potentially become slightly more complicated. But that experimental issue should not hold up the creation of the new web-component.