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
281 stars 201 forks source link

Content support from MHV Portals/Access team #64878

Closed rbsingleton closed 1 month ago

rbsingleton commented 1 year ago

About your team

CAIA Support Request

Describe what you need in a few sentences:

This team is tasked with communicating to Veterans using My HealtheVet (Liferay/ Legacy) that the My HealtheVet credential will no longer be usable without updated security measures beginning December 4th, and will eventually go away in favor of Login.gov and ID.me credentials. This is a complex shift, aspects of which require alignment between OCC and OCTO stakeholders. We want to ensure that we are communicating this shift in line with what is promoted by Identity teams, and will need to ensure that the Identity/MHV on VA.gov Communications Working Group approves content prior to launch. We would appreciate content support.

Which are you doing?

Types of Support

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

Content

Timeframe

We guide and work alongside teams across nearly every OCTO digital product. We also work with partners across VA to lead content migration and manage all unauthenticated content on VA.gov. And we're always working to expand the VA.gov content style guide and our IA and accessibility documentation. We need to prioritize all intake requests based on our overall workload and VA and OCTO priorities.

Tell us about your product's timeline. And we'll work with you to meet timeline needs as best we can.

We must have updated designs with finalized content launched in October in order to sufficiently warn Veterans of the upcoming credentialing change prior the December 4th, when changes will take place.

Have you worked with CAIA before?

What's your team’s next step and its timing?

Timing for your next step:

Is this timing related to a specific event or Congressionally mandated deadline?

If you're conducting research, when is that starting?

Provide date if available: xx/xx/xxxx

Will you release this new product incrementally (for example, release to 25% of users to start)?

Note: If you checked yes, we’ll reach out to discuss details about the content in the react widget (we use these widgets to display entry points for new products to a certain percentage of users who visit our static pages).

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

Please provide an estimated date so our team can create other relevant tickets.

Collaboration Cycle

Will this work be going through the Collaboration Cycle?

If no ...

If yes ...

Please provide the link to your Collaboration Cycle ticket:

Please check all of the phases in the Collaboration Cycle you have completed:

For planning purposes, please check all of the phases in the Collaboration Cycle you feel you might need CAIA support and guidance:

Design Intent

Supporting artifacts

Please provide links to supporting artifacts as available.

Additional Support: Collaborative Sessions

Have you already worked with someone from OCTO leadership?

How do you plan to work with us on this request?

Accessibility Help in Slack

The #accessibility-help channel in the DSVA Slack, is also available to you as a resource. Everyone is welcome to ask questions or get help from our a11y (accessibility) specialists. Tag @Terry Nichols to get a11y help asap.

Next steps

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

sara-amanda commented 1 year ago

@laurwill @kristinoletmuskat @coforma-terry CAIA Note

laurwill commented 1 year ago

Hi @rbsingleton , just noting that Danielle’s going to reach out about this since it’s more of a comms piece specific to MHV.

rbsingleton commented 1 year ago

Thanks @laurwill!

strelichl commented 1 month ago

Closing this since sign in work is well underway in other tickets