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

[Epic] Identity for Inherited Proofing #38185

Closed nsoutouras closed 8 months ago

nsoutouras commented 2 years ago

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

What do you need help with?

Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.

Supporting Artifacts

Please provide supporting artifacts as available.

PRODUCT OUTLINE: LINK WIREFRAME: LINK RESEARCH PLAN: LINK CONVERSATION GUIDE: LINK

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 #va-sitewide-content-ia Slack channel and tag Stan Gardner.

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

mnorthuis commented 2 years ago

Hi @nsoutouras! I have a few questions/comments for you after reviewing the flows and mock ups.

  1. Specifically when will users who are logging in be intercepted with this modal? Just when prompted from related email communications, or content pages specific to this situation? We cannot intercept users logging in to complete a task that is unrelated to this event. It will be confusing, and would take users out of the flow of finishing critical tasks such as completing an application or updating data.
  2. Because this is something that will likely be triggered through email or online content, and not necessarily something users will navigate to in the experience, you will not need the breadcrumb on the information page. You can remove it for user testing along with the horizontal rule (which we don't have on core content pages). Resources and support articles will have a breadcrumb per the existing site.
  3. The wizard component is being retired due to a number of usability and accessibility issues. It looks like the information you have in the wizard should be presented with straight content since it is not part of a form flow.
  4. What page is the user sent to once they complete the Login.gov or ID.me flow? I see it represented in the flow as having either confirmation or error messaging, but don't see a wireframe for it. It is also likely that they will be logged out of VA.gov during the process, so the page they return to would not be personalized.
  5. If the process fails, do they continue to get a prompt to try it again? Or how/where/when do we direct them to try this process up again?
mnorthuis commented 2 years ago

Thank you for jumping on a call with me this morning @nsoutouras! Here are my notes from our discussion related to Sitewide Content and IA needs and timing for this first round of research and Midpoint review. I will add full meeting notes to my IA issue: https://github.com/department-of-veterans-affairs/va.gov-team/issues/38416.

Timeline and research:

Next steps for Sitewide Content and IA:

SgardnerPMP commented 2 years ago

Possible - content stories include: email correspondence Landing page *R&S articles Danielle is leading, and effort is moderate to considerable. 6 to seven weeks, but customer wants now.

DanielleThierryUSDSVA commented 2 years ago

Hi @nsoutouras. As we've talked about a bit in slack, we need a lot of content work on this effort to align with the VA.gov voice/tone/plain language standards. We also need to address some of the questions and recommendations that @mnorthuis has raised as part of her IA work.

Here's a link to a work-in-progress draft content doc. I believe you all have started usability testing, so I think it would be good for all of us to meet and talk through how to proceed before I continue working through this content. Thanks!

DanielleThierryUSDSVA commented 2 years ago

Hi @shiragoodman. Wanted to make sure you're aware of these IA and content reviews for context of collaboration cycle. Thanks!

DanielleThierryUSDSVA commented 2 years ago

Hi @nsoutouras. @mnorthuis mentioned that you all have another round of research coming up soon. We should connect before then re: content and IA to make sure that what you're testing with folks reflects our conversations and recommendations coming out of those. Thanks.

nsoutouras commented 2 years ago

@DanielleThierryUSDSVA Is it possible to move that content doc into another space? Part of the team is unable to access it.

DanielleThierryUSDSVA commented 2 years ago

Hi @nsoutouras. I'm attaching the latest version of the doc here for reference. But ideally, we'll want to work in a shared doc. Team members should be able to access it as long as they're on the VA network. Do folks not have access to the network?

identity content changes_03.30.22

mnorthuis commented 1 year ago

Per John R - This work will pick back up, Joe Niquette (Identity Core), Elizabeth Koch, and Tyler Gindraux (Login.gov Adoption Team) are contacts as Nick is no longer with Oddball.