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

Update Other nearby locations directions link with sr-only solution #14309

Closed
5 tasks done
laflannery opened this issue Jul 10, 2023 · 8 comments
Closed
5 tasks done

Update Other nearby locations directions link with sr-only solution #14309

laflannery opened this issue Jul 10, 2023 · 8 comments
Assignees
Labels
accessibility Issues related to accessibility Facilities Facilities products (VAMC, Vet Center, etc) Good first task Misc label to track specific ad hoc topics sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team

Comments

@laflannery
Copy link
Contributor

laflannery commented Jul 10, 2023

Description

This is related to #13837 and #12085

The Directions links should include text for screen readers to specifically indicate which location the link is providing directions for. Screen reader users may navigate pages by only focusable items, which means they only hear "link Directions (Google Maps)" without the surrounding context.

Ideally all the directions links through the site should be implemented in the same way, so that this is consistent and users can expect the same experience whenever they encounter a directions link.

  • Visually the link text should be "Get directions on Google Maps" as this is more clear and also consistent with what is being used in the Facility Locator.
  • It would then include screen reader only text class="sr-only" that would include the title of the specific location that would make these unique links.
    This would include the directions link for locations under "Other nearby locations" also.

Steps to Recreate

  1. Go to a VAMC Locations page, or Vet Center Locations page
  2. Scroll down to the Other nearby locations section
  3. Notice that the directions links for these locations do not follow the pattern indicated in the description.

Acceptance Criteria

  • The directions links should be programmatically unique and provide information as to the location the directions pertain using the sr-only pattern
  • All links should open in a new tab with target="_blank"
  • All directions links should also have noreferrer attribute
  • All directions links visually say "Get Directions on Google Maps"
  • Accessibility review

Possible Fixes (optional)

Add screen reader only text:
<a href="#">Get directions on Google Maps <span class="sr-only">to Erie Health Care Medical Center</span></a>

This is already done on the Facility Locator search results Directions links for reference and in the 2 tickets mention in the Description

WCAG or Vendor Guidance (optional)

Screenshots

image

image

@laflannery laflannery added Needs refining Issue status VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team accessibility Issues related to accessibility VA.gov frontend CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) labels Jul 10, 2023
@mmiddaugh
Copy link
Contributor

May make sense to do at the same time as "Other nearby VA locations" list on VAMC page #13896

@laflannery laflannery added the Still Applicable Issue has been reviewed and determined to be still valid label Jul 19, 2023
@jilladams jilladams added the Good first task Misc label to track specific ad hoc topics label Aug 2, 2023
@Dottisea Dottisea removed the Needs refining Issue status label Aug 3, 2023
@xiongjaneg xiongjaneg added the UX label Aug 21, 2023
@laflannery laflannery removed the Still Applicable Issue has been reviewed and determined to be still valid label Sep 5, 2023
@davidmpickett davidmpickett removed the UX label Sep 21, 2023
@eselkin
Copy link
Contributor

eselkin commented Oct 10, 2023

This is still open because the builds keep failing on required steps (e.g. it'll build on dev and prod but not staging and have to be rebuilt, or it'll run tests then one test will timeout waiting for a runner and then need to be restarted and then a subsequent test will do the same). So many hours of instability.

EDIT: Finally enough re-running of tests passed. Merged.

@jilladams
Copy link
Contributor

Verified the sr-only appears correctly,

screenshots: ![Screenshot 2023-10-11 at 4 28 34 PM](https://github.com/department-of-veterans-affairs/va.gov-cms/assets/85581471/55d0a533-9293-4900-acdd-8da6957686f2)

Screenshot 2023-10-11 at 4 38 31 PM

One missing piece: Not all directions links include noreferrer. I'm pretty sure the spirit of the AC is for Google links on Locations page to be treated the same, so I do think we should clean this up if that's easy to do, before call it done here. Notes:

https://www.va.gov/north-florida-health-care/locations/
Main: 🔴 does not
Health clinic: 🔴 does not
Other nearby: 🟢 does

https://www.va.gov/ocala-vet-center/locations/
Main: 🔴 does not
Satellite: 🔴 does not
Other nearby: 🟢 does

@eselkin
Copy link
Contributor

eselkin commented Oct 12, 2023

They are separate areas managed by other components. Only the ones in other nearby were supposed to be updated here. I can modify the ticket if needed to list all areas, but those aren't the only google driving directions either, I think.

@jilladams
Copy link
Contributor

@laflannery can confirm -- I'm ok breaking the missing noreferrers into a separate ticket since they're separate components if we need to.

@laflannery
Copy link
Contributor Author

laflannery commented Oct 12, 2023

@jilladams You are correct that this ticket was supposed to get everything all nicely cleaned up and it has from a strictly accessibility standpoint. However noreferrers is another request for external links that was added with the updated external links guidance - it is not an accessibility request but rather just a general thing Platform would like external links to have now. This guidance didn't happened until after the previous tickets (#13837 & #12085) were completed which is why those are now behind.

That being said - I think it's your call whether we:

  1. Expand the scope of this ticket to go backwards and add the noreferrer to those previous directions links or
  2. Make a new backlog ticket to add noreferrer to the previous directions links

@jilladams
Copy link
Contributor

Ok. That in mind, closing this ticket as complete in prod for Other nearby locations, and have created #15670 as a blanket ticket to mop up whatever has been left behind in our products / Google links.

@eselkin
Copy link
Contributor

eselkin commented Oct 12, 2023

Putting a note here and there where to find the main facility listing & satellite listings google directions links (they are in content-build in src/site/includes/directions-google-maps.liquid not in vets-website like these were).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility Facilities Facilities products (VAMC, Vet Center, etc) Good first task Misc label to track specific ad hoc topics sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

7 participants