Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VACMS-17280: benefit hub component upgrade #1955

Merged
merged 7 commits into from
Mar 15, 2024

Conversation

chriskim2311
Copy link
Contributor

@chriskim2311 chriskim2311 commented Mar 12, 2024

Summary

Benefit hub landing template component upgrade v1 to v3

Related issue(s)

department-of-veterans-affairs/va.gov-cms#17280

Testing done

Tested new components locally
/health-care/

Screenshots

VA_Health_Care___Veterans_Affairs

VA_Health_Care___Veterans_Affairs

VA_Health_Care___Veterans_Affairs

VA_Health_Care___Veterans_Affairs

What areas of the site does it impact?

Benefit Hubs

Acceptance criteria

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17280-benefit-hub-component-upgrade March 12, 2024 09:16 Inactive
@chriskim2311
Copy link
Contributor Author

chriskim2311 commented Mar 12, 2024

@laflannery
Working on the telephone component upgrade on benefit hubs. Came across this where we are setting the title and the phone number. We have the same issue as before in the other PR where the component cannot take custom non-digit numbers from the CMS. We can make them va-links, or keep them a tags until DST accounts for custom strings.

@thejordanwood Also this would be the new look since the va-link cannot use the title like we did in the previous implementation. Thoughts on this if its okay to use the va-link?

Old
VA_Health_Care___Veterans_Affairs

New
VA_Health_Care___Veterans_Affairs

@laflannery
Copy link

@chriskim2311 totally my bad for not calling this out because when I did my investigation the first time you brought this up I knew this was used here too - so sorry!

But that being said, the discovery ticket I made to figure this all out will handle this eventually so at least that's covered for future.

For now, I'm not sure <va-link> is going to work because a couple don't seem to have an href that is formatted properly:

  • The TTY number is tel:1+771. Having the + in the middle is going to be not ideal and I'm also questioning the 1, I feel like that might mess it up as well?
  • The VETS number on the Health care page has tel:1-877-222-VETS(8387) the non-digit characters in the number I think are going to mess up using this properly

So with that - because we can't guarantee proper formatting for these numbers here, we may want to keep these as they are?

@chriskim2311
Copy link
Contributor Author

@laflannery Thanks for the quick response! That makes sense to me, I think we should hold off then on changing the telephones until we have a more complete component.

@thejordanwood
Copy link

@chriskim2311 I agree with that approach!

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17280-benefit-hub-component-upgrade March 12, 2024 19:19 Inactive
Chris Kim added 2 commits March 13, 2024 15:25
…ent-build into 17280-benefit-hub-component-upgrade
@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17280-benefit-hub-component-upgrade March 13, 2024 22:30 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17280-benefit-hub-component-upgrade March 14, 2024 16:38 Inactive
@chriskim2311 chriskim2311 marked this pull request as ready for review March 14, 2024 21:09
@chriskim2311 chriskim2311 requested review from a team as code owners March 14, 2024 21:09
Copy link
Collaborator

@va-vfs-bot va-vfs-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Icon found

Icons can be decorative, but sometimes they are used to convey meaning. If there are any semantics associated with an icon, those semantics should also be conveyed to a screen reader.

What you can do

Review the markup and see if the icon provides information that isn't represented textually, or wait for a VSP review.

src/site/layouts/landing_page.drupal.liquid Show resolved Hide resolved
src/site/layouts/landing_page.drupal.liquid Show resolved Hide resolved
src/site/layouts/landing_page.drupal.liquid Show resolved Hide resolved
src/site/layouts/landing_page.drupal.liquid Show resolved Hide resolved
Copy link
Contributor

@eselkin eselkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chriskim2311 chriskim2311 merged commit 24c14f8 into main Mar 15, 2024
25 checks passed
@chriskim2311 chriskim2311 deleted the 17280-benefit-hub-component-upgrade branch March 15, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants