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

PACT Act IA #65776

Closed
16 of 67 tasks
Tracked by #43327
jilladams opened this issue Sep 18, 2023 · 15 comments
Closed
16 of 67 tasks
Tracked by #43327

PACT Act IA #65776

jilladams opened this issue Sep 18, 2023 · 15 comments

Comments

@jilladams
Copy link
Contributor

jilladams commented Sep 18, 2023

About your team

CAIA Support Request

Describe what you need in a few sentences:

PACT Act Wizard needs IA consideration for where in the VA.gov navigation the wizard will live.



Which are you doing?

  • Launching a new page, tool, form, or app
  • Making changes to an existing page, tool, form, or app

Types of Support

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

Content

  • Collaboration on content written by your team’s dedicated content writer
  • Collaboration on content if your team does not have a dedicated content writer

Accessibility

  • Accessibility review of wireframes and/or prototypes
  • Accessibility issue (general request)
  • Accessibility PDF review request
  • Accessibility user research support (submit a separate, additional request)
  • DST component or pattern
  • Something else

IA

  • User Flows
  • Page placement
  • URLs
  • Breadcrumbs and Left Nav placement
  • Redirects

Multilingual content

  • Translating 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.

Prototype research will happen in October, hoping to launch by EOY.

Have you worked with CAIA before?

  • Yes
  • No

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

  • Our next step is Midpoint review
  • Provide date if available: 9/19/23

Timing for your next step:

  • Next week
  • This month
  • Next month
  • This quarter
  • Next quarter
  • 6 months
  • 1 year

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

  • Yes
  • No - related to Congressional mandate, but the wizard does not have a related timing mandate for launch, afaik

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

Provide date if available: xx/xx/xxxx

  • Next week
  • This month
  • Next month
  • This quarter
  • Next quarter
  • 6 months
  • 1 year

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

  • Yes
  • No

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.

  • We expect to launch our product to 100% of users on: xx/xx/xxxx

Collaboration Cycle

Will this work be going through the Collaboration Cycle?

  • Yes
  • No

If no ...

  • Skip to the supporting artifacts section, below.

If yes ...

Please provide the link to your Collaboration Cycle ticket:

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

  • Design Intent
  • Midpoint Review. - scheduled 9/19
  • Staging

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

Design Intent
  • Accessibility
  • Content
  • IA
  • Translation
  • Already completed, no assistance needed
  • Unknown at this time
Midpoint
  • Accessibility
  • Content -- final verifications of the content already provided
  • IA
  • Translation
  • Already completed, no assistance needed
  • Unknown at this time
Staging
  • Accessibility
  • Content -- final verifications of the content already provided
  • IA
  • Translation
  • Already completed, no assistance needed
  • Unknown at this time

Supporting artifacts

Please provide links to supporting artifacts as available.

Additional Support: Collaborative Sessions

Have you already worked with someone from OCTO leadership?

  • Danielle
  • Beth
  • Mikki
  • Martha

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

  • I’ll take this to Beth or Danielle’s office hours.
  • I’d like to schedule time to talk about this.
  • Let’s work async and meet as needed.
  • Schedule a kick-off call with your team and CAIA for your project (Recommended)

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.

@jilladams jilladams added Facilities Sitewide Facilities products (VAMC, Vet Center, etc) sitewide IA sitewide CAIA and removed Facilities Sitewide Facilities products (VAMC, Vet Center, etc) labels Sep 18, 2023
@kristinoletmuskat kristinoletmuskat self-assigned this Sep 18, 2023
@kristinoletmuskat
Copy link
Contributor

Started thinking on this, work is documented here (https://docs.google.com/document/d/1IvhC-mUObiH35p8UkkthxFNAoaHhW8poZiGue2M1pZc/edit#heading=h.cj7t67f7zwn0). Meeting with Danielle on 9/22 to finalize.

@kristinoletmuskat
Copy link
Contributor

Hi @jilladams , I wanted to share the current IA thinking on the wizard in this Mural.

Would ya'll be able to leave comments with questions in there, and we can try to address async? Since there are so many crosslinking entrypoints for the PACT Act content, I thought a visual would be more helpful.

@jilladams
Copy link
Contributor Author

All makes sense to me! @wesrowe @randimays @thejordanwood : IA updates from CAIA here.
Proposed path = va.gov/pact-act-eligibility
Mural includes more IA thinking about entry points, for reference, as well as disclaimers that we may need to update path in future if PACT extends to cover more toxic exposure benefits.

Please add notes in Mural as necessary, and comment here to let Kristin know you did, just in case.

@kristinoletmuskat if team has no feedback, are there additional steps needed to finalize?

@kristinoletmuskat
Copy link
Contributor

@jilladams I'll just want to confirm who is going to do the work on the entry points that are in the benefit hubs and navs, whether us or content. And then the final step will be once the tool is live, to let us know so we can update the Best Bets for the tool url so that it pops up in search results.

Here is the finalized markdown file as well: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/information-architecture/ia-design-docs/PACT-Act-wizard.md

@wesrowe
Copy link
Contributor

wesrowe commented Oct 10, 2023

looks good to me @jilladams

@randimays
Copy link
Contributor

Looks good to me too @jilladams

@kristinoletmuskat
Copy link
Contributor

@DanielleThierryUSDSVA just confirming whether you team will be doing the work on the remaining entry points, and whether you have enough info in the mural.

@kristinoletmuskat
Copy link
Contributor

@jilladams I think we can move forward with this IA plan, with the content team owning the entry point work as they usually do! But @DanielleThierryUSDSVA just lmk if you need any more collab on the entry points from us.

@jilladams
Copy link
Contributor Author

Perfect, thanks!

@jilladams
Copy link
Contributor Author

@kristinoletmuskat @DanielleThierryUSDSVA Coming back to this: PACT Act next steps are final content signoff from Stakeholders, Security review, and then launch. Is there any additional thing we need to do here for CAIA's sake to manage the entry point work? I've not been through that process, so not sure if this ticket is closeable and we should be cutting a new one, or if that work will happen here?

@kristinoletmuskat
Copy link
Contributor

kristinoletmuskat commented Jan 26, 2024

Hey @jilladams we actually just created a process for the entry points this past week. Will there be a staged rollout for this tool, or is it going live to 100% of users at once?

@strelichl and @megzehn it sounds like we're getting ready to launch this new PACT ACT wizard, so I think we should initiate our new entry point process! Here is the IA spec doc with the link to the entry points: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/information-architecture/ia-design-docs/PACT-Act-wizard.md

Note that all of the entry points will link to the PACT Act R+S page, which will in turn link to the wizard. So no direct links to the wizard without the contextual info in the R+S page. lmk if you want to sync on any of this!

@jilladams
Copy link
Contributor Author

No staged rollout, will go to 100% of users at once, as far as I'm aware. For @strelichl & @megzehn 's sake, just re-stating: we're blocked on launch date currently by final stakeholder sign off and getting CC Security Review completed, so timing isn't final yet, just getting close! (cc @DanielleThierryUSDSVA @FranECross )

@FranECross
Copy link
Contributor

@kristinoletmuskat @DanielleThierryUSDSVA We're coming up on being able to release PACT Act in the near future (awaiting final content and ensuring all launch activities/tasks are completed), and I wanted to check on the entry point again to see how/if we need to coordinate this. Thanks in advance! cc @jilladams @mmiddaugh @randimays

@kristinoletmuskat
Copy link
Contributor

Hey @FranECross -- if we're still planning for the main entry point to be on the R+S page, the content team will need to add that entry point after the tool is published! I'm not sure who will be doing that -- do we need to spin up a ticket for content, or will you be handling that @DanielleThierryUSDSVA ?

@DanielleThierryUSDSVA
Copy link
Contributor

Thanks, all! I can handle...might as well see this one through to the end ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment