Staging Review: (DS) Converted File Input Component

[caw310]

Design System Staging Review

Converted USWDS v3 File Input 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: https://design.va.gov/components/form/file-input
• [ ] Storybook link: https://design.va.gov/storybook/?path=/story/uswds-va-file-input--default and https://design.va.gov/storybook/?path=/docs/uswds-va-file-input-multiple--docs
• [ ] Figma link: https://www.figma.com/file/JDFpGLIojfuQwANXScQjqe/VADS-Component-Examples?type=design&node-id=1360-85508&mode=design&t=i1Eao9Pxo60e5DFK-0
• [ ] 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: old Request thread Request thread
• [x] Meeting date/time: Canceled: Thursday, March 14, 2024 at 1:30PM ET Thursday, July 25 at 3:30pm ET

After meeting

Platform actions

• [x] Update this ticket with the Zoom recording
  • Recording of Staging Review meeting
  • Passcode: kwU0wWW%

Design System actions

• [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns
• [ ] Let Governance know when any High Priority findings have been incorporated
• [ ] 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

[caw310]

@shiragoodman @briandeconinck , I forgot that we have to make a change to File Input to accommodate removing a file. I will need to reschedule this for probably late March or early April. Sorry for the mix up.

[briandeconinck]

Hey @caw310! No worries! I'll go ahead and cancel the meeting for now

[shiragoodman]

hey @caw310 - are you planning on picking this back up soon? Please let us know.

[caw310]

@shiragoodman development on multiple file input is still in progress. Once that is done we have tickets to do an accessibility review and to update documentation. Once those are done I will resubmit this request.