You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On February 16, all design system web components will default to their v3 variant. v3 will be opt-out only. Current PW product status regarding web components:
Some products use some v3 web components
Some products don't use web components but can/should
Some products use web components, but they are not v3
To align with brand standards and maximize compliance with accessibility requirements, we need to update as many of our products as possible to use v3 web components. It is anticipated that this ticket will include a review of both vets-website and content-build code.
This ticket is intended for discovery only as design/functionality may change for new web components and we want to ensure thorough testing and design approval.
User story
Describe the audience/user, enhancement or fix, and value / outcome desired.
Based on 1 example of each content type that has a veteran-facing page, used the handy dandy plugin Laura shared here, and noted the components I saw in use.
This isn't comprehensive, as some markup may not appear if content isn't populated fully in Drupal, etc. But a starting point.
Description
On February 16, all design system web components will default to their v3 variant. v3 will be opt-out only. Current PW product status regarding web components:
To align with brand standards and maximize compliance with accessibility requirements, we need to update as many of our products as possible to use v3 web components. It is anticipated that this ticket will include a review of both
vets-website
andcontent-build
code.Slack thread for v3 update announcement: https://dsva.slack.com/archives/C03R5SBELQM/p1705503589174489
List of PW products: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/public-websites
This ticket is intended for discovery only as design/functionality may change for new web components and we want to ensure thorough testing and design approval.
User story
AS A
I WANT
SO THAT
Acceptance criteria
The text was updated successfully, but these errors were encountered: