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-17436: Update links for manage your health care section #2174

Merged
merged 6 commits into from
Jul 12, 2024

Conversation

chriskim2311
Copy link
Contributor

Summary

For this PR we are adding 2 new links under the Manage your health care section.

Download VA Health Chat and Connect to VA Care.

Also we changed the header as well to an h2 to fix an a11y defect.

Related issue(s)

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

Testing done

Tested locally at /greater-los-angeles-health-care/

Verified links are working and redirecting to correct address.

Screenshots

VA_Greater_Los_Angeles_Health_Care___Veterans_Affairs

What areas of the site does it impact?

VA Health Care system pages

Acceptance criteria

Add VA Health Chat

  • add 'chat' USWDS v3 icon
  • include aria-hidden="true" on icon
  • add link text "Download VA Health Chat" with a link [https://mobile.va.gov/app/va-health-chat]

Add VA Health connect

Additional Acceptance Criteria

  • all existing links remain
  • new links should appear below existing links
  • Change header to h2 (currently h3)

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17436-va-health-links July 11, 2024 22:15 Inactive
@chriskim2311 chriskim2311 marked this pull request as ready for review July 11, 2024 22:28
@chriskim2311 chriskim2311 requested a review from a team as a code owner July 11, 2024 22:28
@chriskim2311 chriskim2311 requested a review from laflannery July 11, 2024 22:28
@va-vfs-bot va-vfs-bot requested a review from a team July 11, 2024 22:28
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.

Note:

Font Awesome is deprecated. Please use va-icon instead. For more information, visit the migration documentation: Migrate from font awesome to va-icon

@chriskim2311 chriskim2311 requested a review from a team July 11, 2024 22:28
@laflannery
Copy link

@chriskim2311 aria-hidden was added on the va-link which is not correct this is for the icon only and in fact is already being done automatically because we are using va-icon. Can you remove this from the links?

Copy link
Contributor

@randimays randimays left a comment

Choose a reason for hiding this comment

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

There's an additional AC in the ticket about keeping these links "below existing links" but on mobile they are nested within the other links per the structure:

Screenshot 2024-07-12 at 9 24 03 AM Screenshot 2024-07-12 at 9 22 51 AM

Could we confirm with Michelle & design what the behavior should be on mobile? (If we need to reorder things, we can use flex / order to achieve this simply, I think).

@laflannery
Copy link

@randimays Nice catch! Unfortunately though I believe flex order is the property that makes the tab order and the visual order off and confusing (If I'm thinking of the right thing?) However I had a different question for Design I pinged Amanda on in Slack and I will add this to that thread

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17436-va-health-links July 12, 2024 16:37 Inactive
@chriskim2311 chriskim2311 requested a review from a team as a code owner July 12, 2024 17:05
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.

Note:

Font Awesome is deprecated. Please use va-icon instead. For more information, visit the migration documentation: Migrate from font awesome to va-icon

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17436-va-health-links July 12, 2024 17:44 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/main/17436-va-health-links July 12, 2024 18:00 Inactive
Copy link

@laflannery laflannery left a comment

Choose a reason for hiding this comment

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

Looks good!

@chriskim2311
Copy link
Contributor Author

@randimays Can you review this PR thanks!

Copy link

@IGallupSoCo IGallupSoCo 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 1e1d357 into main Jul 12, 2024
24 checks passed
@chriskim2311 chriskim2311 deleted the 17436-va-health-links branch July 12, 2024 21:35
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.

5 participants