Design System Staging review: Minimal Footer

[caw310]

Design System Staging Review

Design System Staging review: Minimal Footer web component

Before meeting

Design System actions

• Navigate to reference link: Design System Staging Review Guidance
• [ ] Schedule your Staging Review when ready:
  • Open the Calendly staging review calendar
  • Select a date and time and click “Confirm”
  • Add your name and email
  • Click "Add Guests" and enter the Design System meeting attendees email addresses
    • Invite all relevant Design System team members
  • Click "Schedule Event"
• [ ] Notify the Collaboration Cycle team of this event by using the /Collab Cycle Staging Review "slash-command" in your team channel. Provide information as prompted by the Slack workflow.
• [ ] If this product contains any experimental design, add the experimental-design label and schedule a meeting with DSC to present the research findings.
• [ ] Link all artifacts ONLY in the Staging Review artifacts section below at least four days before the scheduled Staging Review. Do NOT add artifacts to Comments section

Staging Review artifacts

• [ ] Design system link:
• [ ] Storybook link: https://design.va.gov/storybook/?path=/docs/components-va-minimal-footer--default
• [ ] Sketch link: https://www.sketch.com/s/f5f91c9c-f5c5-41f6-8e7e-6cfe003299fa
• [ ] Other links
• [ ] QA E2E tests (provide a link to the product’s code)
• [ ] Completed accessibility testing artifact. For details, see Prepare for an accessibility staging review.

Platform actions

• [x] Staging review Slack thread with VFS team: Slack thread
• [x] Meeting date/time: Thursday, December 14, 2023 at 3:30PM ET

After meeting

Platform actions

• [ ] Update this ticket with the Zoom recording
  • Recording URL: https://oddball-io.zoom.us/rec/share/qHuZOJa3ZqliAJSvrcgBBxnrwPDDpSmW_T9siIjAkN2BKsA-GSK0WyRt_I03TPro.hiRJJtteeOtISFZJ
  • Password: VWa4&%LJ

Design System actions

• [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns
• [ ] Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket.
• [ ] Close ticket

[pjhill]

All, For the QA review of this component, the BLUF is that the minimal footer component looks good to me!

How I evaluated --

• Looked over the unit test and e2e test spec
• Ran yarn test and saw that it passed
• Served up the example index.html in web-components with the the component added
• Ran axe browser plugin against my index.html example page
• Looked over the component in Storybook including the accessibility tab with 0 violations

I noticed that there's no page for the minimal-footer component on design.va.gov, but there is a link to a page that gives a 403.

[allison0034]

No real feedback, I would love to see "when to consdier something else" added to the guidance. I have a fear a lot of teams will abuse this.