search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

[CAIA intake] 10-10CG Facility page #55327

Open hdjustice opened 1 year ago

hdjustice commented 1 year ago

What does your team need support for? Check all that apply.

Will this new product be released incrementally (for instance 25% of users initially)?

Note: If you checked yes, we'll reach out to discuss details about the content in the react widget.

When do you expect to launch your product to 100% of users?

Supporting artifacts

Please provide supporting artifacts as available.

Will this work be going through the Collaboration Cycle?

When does this work need to be done?

Do you plan to bring this to an upcoming content office hours session?

Note: If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet.

About your team

Next steps

Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag Randi Hecht.

If you also need engineering support from the Public Websites team, fill out their intake request form.

If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a Redirect, URL change, or vanity URL request

### Content tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/55614
kristinoletmuskat commented 1 year ago

Confirmed that we don't need a separate IA ticket for this. The only thing that stuck out to me might be out of scope: The stepper shows that we're on step 1 of the process, but there are several sub-steps within step 1 (veteran name, then location, then this facilities selector). As someone walking through the flow for the first time, I was confused and thought maybe the stepper wasn't working, and then once I saw each step had several pages, I wasn't sure how many steps the 5 step process really was!

And one other thought: I think the confirmation screens are really helpful. But I'm unsure what the impact will be on the user if the facility with the caregiver support coordinator is diff from the one my Veteran usually goes to. Will I have to drive there? Or is that just where the coordinator works? Will I have to change my Veteran's facility to be this other one?

hdjustice commented 1 year ago

Thank you for this feedback! We are reviewing and making updates on the Design Intent feedback, so we will put this in there as well. The stepper has always been an issue for us (we feel the same!), and we have that on our list to address as a whole, which may impact our other application (10-10EZ) and potentially other forms online. cc @jessicastump @davidakennedy

jessicastump commented 1 year ago

Design intent feedback has been incorporated into the following Sketch links: Confirmation screen updates: removed alert, changed link styling for finding a new facility and worked with content on updates

Accessibility feedback: Removed pagination and added link to follow Navigate a long list pattern, team decided to not show closed facilities so a disabled radio tile state is not needed, added annotations for focus order

Content feedback: Updates to confirmation screen language above

RLHecht commented 1 year ago

@jessicastump We still have a ticket open for our team to give content support. Just confirming that we should still be working on this. Should I reopen this ticket? FYSA @aliyahblackmore

jessicastump commented 1 year ago

@RLHecht - As part of the Design Intent phase, we incorporated content feedback received by going to office hours and workshopping only the confirmation page with @DanielleThierryUSDSVA. This will still need content support to get through midpoint/staging phases on time, correct @hdjustice? Or would a final content review now be appropriate?

hdjustice commented 1 year ago

We opened this ticket as part of the Collab cycle process. Perhaps I may have been confused by the comment above from @kristinoletmuskat

Confirmed that we don't need a separate IA ticket for this.

Whichever way is best to track this work is fine, I just didn't want an open ticket that wasn't needed.

RLHecht commented 1 year ago

Hi @hdjustice I'll reopen this ticket since @aliyahblackmore will post final content and any questions for your team in here.

hdjustice commented 1 year ago

Sounds great to me, thank you @RLHecht and @aliyahblackmore!

aliyahblackmore commented 1 year ago

Hi @jessicastump - I'd like to move to this work now that the we've wrapped up most of the 1010EZ household work.

I know that we'd chatted about prioritizing the other field label ask from Katelyn (feedback provided on June 29) and then moving to this.

I'll be able to turn to this when I'm back in office, in early August.

aliyahblackmore commented 1 year ago

Hi @jessicastump - I've taken a look at the screens linked above and the initiative brief and have two questions:

  1. Can you confirm what screen comes before the facility selection screens?
  2. Will the search for facilities input include the type-ahead function? Link to this component in the design system

Thanks so much!

jessicastump commented 1 year ago

Hi @aliyahblackmore

  1. Here is a link to the Mural user flow doc - before the facility selection screens are the two pages around Veteran information. The facility page is the last page in this section before moving on to the primary caregiver section
  2. I think it would but I would need to check with engineering first - I will circle back on this one early next week.
aliyahblackmore commented 1 year ago

Thanks @jessicastump !

A few additional questions:

jessicastump commented 1 year ago
aliyahblackmore commented 1 year ago

Thanks @jessicastump !

I'm back with a follow up question about how the facilities will show in the search (considering the fact that there are still some unknowns around the API!):

  1. As you mentioned, I took a look at the insurance section in the 1010 EZ and it seems like there's a slightly different use case there - someone can either use the drop down or they can use the facility locator link. And it seems like if they use the facility locator link, they'd need to come back to the form and then find the selection based on what showed on the facility locator. So they'd select the state and facility name from the drop down, based on what showed on the facility locator. Is that thinking right?
  2. If the facility search shows all locations, it sounds like you all want the facility locator link be another way that someone can search and then select in the application screen based on what showed in the facility locator? If so, I'd suggest showing the facility link before the results. I can provide content suggestions for this.
  3. If the facility search won't show all locations at this time and the facility locator link is there for someone to search for additional options ("Don't see your facility listed in search?"), how does that map back to the application? From my understanding of the flow, I have a concern about the user experience in this instance since the results for the facility locator (name of facility, state, zip code, etc.) aren't a direct or exact map to the field input options on CG search (city, state, or postal code). Are you all expecting that the user would go through the searches that populated already and match the information to what showed in the facility search (I.e. looking for a name or searching for a name, zip code, etc.) or search again and only enter the state, zip, code or city information that showed in the facility locator search?

Because there are still some unknowns about the API, after getting some more clarity about the above, I'd likely suggest content for two different use cases/scenarios and we can plan to chat more in our meeting on Friday about the flow if someone isn't finding their facility in the application and goes out to the external link!

jessicastump commented 1 year ago

Let's talk through this on Friday or happy to meet before too! And maybe this will help.

  1. The EZ facility search page is odd and is intended to be updated next and the use cases between the forms are very different.
  2. The goal is to have a zip/city/state input search for locations and not really have to rely on the map at all. With this discussion, I am wondering if the link should remain on there at all.
  3. The hope here is the new api has all locations and has them mapped in a way that works for the Caregiver program. There are basically caregiver point facilities that some smaller facilities map up to, "parent" facilities. There are two different flows, only difference is the confirm facility page for those smaller "child" locations and that is just to provide awareness of the caregiver coordinator location.
aliyahblackmore commented 1 year ago

Thanks for providing this info @jessicastump - chatting further tomorrow would be great to confirm I'm aligned with content needs given the API conversation.

I will plan to walk through some preliminary suggestions tomorrow and looking forward to continued conversation!

aliyahblackmore commented 1 year ago

As the Jessica, DK, and Hieu mentioned last week, just tracking here that this work is on pause as we pivot to and prioritize the 1010EZR work!

strelichl commented 2 weeks ago

This work might be done, Heather will check with the team