Closed randimays closed 3 months ago
Mid-sprint update: we have been blocked on using va-icon in content-build since 4/19. DST is still working on a fix; it's not clear whether it will be released before the end of our sprint, but flagging the risk here.
@thejordanwood The slider icon for mobile Resources & Support search does not seem to have an equivalent in USWDS (https://designsystem.digital.gov/components/icon/). Is there an icon there that you think would fit with this interface? Also including the open version of this widget for reference.
We could move to an expand/collapse icon set?
I think we should align with the accordion design and use the subtract and remove icons.
@aklausmeier I want to double check with you on this one since there are a couple of different options we can use, like the expand less/more icons that Randi suggested.
Agree with Jordan, let's use the add and subtract USWDS icons.
Thanks @thejordanwood and @aklausmeier!
Still iterating on design & accessibility feedback for these icons. This will carry over.
@randimays I think this is already in Prod - can that be true? I encountered it when I was doing my a11y audit of Resources & Support
@laflannery The vets-website piece of this is already in prod (that's the mobile expand/collapse behavior). The content-build piece (PR here: https://github.com/department-of-veterans-affairs/content-build/pull/2086) has not made it there yet.
The content-build piece has been validated in production. We cannot verify the browse-by-audience
and media_list_images
changes in production as we do not have production usage of them but we have high confidence in their usage / no regression. Closing!
Description
The Design System team is deprecating Font Awesome and encouraging teams to use
<va-icon>
where possible by the end of May 2024. Slack post here: https://dsva.slack.com/archives/C03R5SBELQM/p1710776364414359We need to convert all usage of
<i>
in this application in vets-website and content-build to<va-icon>
to align with the icons in DST's library here: https://design.va.gov/foundation/icons<va-icon>
guidance in Storybook: https://design.va.gov/storybook/?path=/docs/uswds-va-icon--defaultEngineering notes
Icons to be converted:
User story
AS A PO/PM for products/features/applications managed by the Public Websites team I WANT our features/products/applicates migrated to va-icon where appropriate SO THAT when the migration to va-icon and deprecation of Font Awesome takes place, there won't be degraded Veteran-facing experiences in VA.gov.
Quality / testing notes
Acceptance criteria
<i>
that can be converted to<va-icon>
are converted