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] Claim status tool updates from Benefits Mgmt Tools #61696

Closed skylerschain closed 6 months ago

skylerschain commented 1 year ago

About your team

CAIA Support Request

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

Give a brief description of what your team needs support with:

We are working on new designs for the Claim Status Tool home page. We are looking for a content review on a first draft prototype to see if there are any content tweaks we should make to align with VA.gov standards.

Timeframe

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?

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

When does this work need to be completed?

Collaboration Cycle

Will this work be going through the Collaboration Cycle?

If no ...

If yes ...

Please provide the link to your Collaboration Cycle ticket:

https://github.com/department-of-veterans-affairs/va.gov-team/issues/58828

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 supporting artifacts as available.

Additional Support

Collaborative Sessions

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

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.

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/62735
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/68345
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/68344
coforma-terry commented 1 year ago

Tagging @megzehn for this one as it's content focused :)

skylerschain commented 1 year ago

Just an update here. We are working on some design iterations based on the feedback from the Design Intent review. Would love for some content eyes on this – but keep in mind we will have a newer version of the design probably in a week or so. Latest versions can be found here.

laurwill commented 1 year ago

Hi @skylerschain , thanks for the update! Your original target date for CAIA work was July 20, but we want to avoid double work if you're making updates based on design intent. Would it make sense to pause this until next week and provide our suggestions based on the updated designs?

skylerschain commented 1 year ago

Yes I think that makes sense! I will circle back to this next week with an updated set of designs.

On Tue, Jul 18, 2023 at 9:29 AM laurwill @.***> wrote:

Hi @skylerschain https://github.com/skylerschain , thanks for the update! Your original target date for CAIA work was July 20, but we want to avoid double work if you're making updates based on design intent. Would it make sense to pause this until next week and provide our suggestions based on the updated designs?

— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/61696#issuecomment-1640554125, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWVSI2VBNTVXIEJEIAAN3XDXQ22WVANCNFSM6AAAAAA2E5RYHI . You are receiving this because you were mentioned.Message ID: @.*** .com>

laurwill commented 1 year ago

Hi @skylerschain — documenting some notes from our meeting last week, and also pulling in @kristinoletmuskat to note IA / OOUX considerations.

This work is moving towards an async midpoint (not yet scheduled). We'll provide content support in stages. The first piece to focus on in our current sprint is the new cards in these 2 Sketch screens. Veterans usually have 2 to 10 of these cards:

As part of this ongoing content work, we'll need to resolve these inconsistent word clusters flagged in design intent feedback: Image

@skylerschain could you also provide the list of "Recent activity" steps that we'll need descriptions for in that screen? I think you mentioned it would be a long list, so we'll want to make a plan for those.

skylerschain commented 1 year ago

Yes, thank you @laurwill!

As a source of truth, let's use this link: https://www.sketch.com/s/98e35645-34eb-40cf-80c1-6c4952943584/v/4LPabm/p/B9C46ABC-36AD-4CA8-9896-55762FC6912E/canvas?posX=-718.5416497737808&posY=-3212.7872891352317&zoom=0.36041006445884705

This has a few minor tweaks from the last one we looked at, but this is the Final Spec I'll be passing off to developers and I'll maintain this with our latest language changes.

As for the "Recent activity" list, those are tracking updates coming from VBMS. The current version of this appears as "updates" in the CST claim status page (see below). I'm not sure where that full list of strings lives, if anywhere, but I'll check with my engineering team.

Screenshot 2023-08-02 at 9 17 55 AM
skylerschain commented 1 year ago

Ok, here is the full list of strings for the "Updates" / "Recent activity" section.

We added a notice for: {linkTofile} You or someone else submitted {event.displayName}. We have reviewed your submitted evidence for {event.displayName}. We will notify you if we need additional information. We closed the notice for {event.displayName} You or someone else submitted {file ? "${file}" : 'a file'}. Your claim moved to {getUserPhaseDescription(phase)} Thank you. VA received your claim

joshkimux commented 1 year ago

@laurwill adding another small request here! We're looking for some guidance on how to write out our page titles. I've included context to this in this ticket here.

We need help determining:

I'm happy to meet about this if it's easier than working async!

mistymg commented 1 year ago

@skylerschain I may give some content feedback in partnership with Laura from a mobile app standpoint, since these changes will affect us as well. Could you give me access to comment in the Sketch files? Thanks!

skylerschain commented 1 year ago

Done :)

uxgary commented 1 year ago

Hello @kristinoletmuskat

We have a separate ticket that is dependent on the work here. Per the ticket, we need to update the browser tab titles. As we know it, the browser tab title will be a combination of the breadcrumb, H1, and H2. I'm looking for some help, if you could please provide answers to these questions:

kristinoletmuskat commented 1 year ago

Hey @uxgary -- I was reading through the ticket you connected and looking through Josh Kim's suggestions. It looks like ya'll might have made some decisions based on his feedback? Or have you solidified your H1s with content @laurwill?

Here's some info for your questions, but first we gotta confirm what you've selected for the H1

  1. The breadcrumb should ideally match the H1.
  2. General guidance for title tags:
    • the title tag does have to include | Veterans Affairs. It's ok if it gets cut off in the browser tab, it will still show up in search engine results.
    • The title tag doesn't have to be <52 characters, just note that's where it will get cut off.
    • The current official pattern is H1 | Veterans Affairs...however, we are starting to do things differently for auth pages. Based on what we are doing for health, the pattern we are using is specific --> general: [H1] - [tool/product name] | Veterans Affairs. Ex: Blood Pressure History - Medical Records | Veterans Affairs

@skylerschain can you remind me why we can't put the claimed conditions in the H1s? Ex: 'Claim for Headaches, PTSD, left foot condition'

skylerschain commented 1 year ago

@kristinoletmuskat Is the H1 you're referring to the "Your compensation claim" title?

I think putting the claim conditions in the H1 could be tough, because we don't control how many of those there are, and often there are quite a few. So it could lead to really long H1s in a high portion of claims.

MacBook Air 13 Copy 51
uxgary commented 1 year ago

Thank you for your feedback @kristinoletmuskat the information you've provided is great. One last thing, we wanted to have browser tab unique in the event that a veteran (incl. ones using assistive tech) has two or more claims tab open they can differentiate.

I wanted to share some ideas that came to mind (based on the H2s), I wanted to know what you think or if you could modify these in the way you think is most appropriate.

Generic title for the entire page:

Tab specific (the page title would update when the user clicks on a tab)

kristinoletmuskat commented 1 year ago

Chatted with Skylar and we're going to touch base on a call tomorrow.

But I also wanted to mention this! Our title tags are all initial caps which is different from H1s - so the title tag would be "Status Of June 15, 2023 Compensation Claim | Veterans Affairs"

skylerschain commented 1 year ago

Outcomes from the meeting Aug 31, 2023

  1. We will go with Gary's second option for browser tab titles. The only note is to remove "your" to keep it more concise.

  2. To make the breadcrumbs more unique for the different parts of the detail page we will update them to:

    • Status of claim
    • Files for claim
    • Overview of claim

  3. Skyler to create mocks reflecting these decisions and will post a link here ASAP for the team's review.

skylerschain commented 1 year ago

Update: After discussion with engineering, it's not feasible to have the breadcrumbs say "Status of claim," "Files for claim," etc. because we won't know if it's a claim vs. a decision review type the way that this code is currently written.

As a result we are going with the following for breadcrumbs to keep it claim type-agnostic.

The latest mocks reflect these changes.

kristinoletmuskat commented 6 months ago

Hey @skylerschain do we still need this ticket open?

skylerschain commented 6 months ago

Nope!