[CAIA intake] Content review for Board of Veterans’ Appeals (BVA) hearing

[jilladams]

About your team

• Team name: Sitewide Public Websites
• OCTO-DE product owner: Dave Conlon
• Product manager: @FranECross
• Designer: Jordan Wood
• Accessibility specialist: Laura Flannery
• Content writer: N/A
• Slack channel: https://dsva.slack.com/archives/C01K37HRUAH/p1699038995102449

CAIA Support Request

Describe what you need in a few sentences:

https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/ re: CMS ticket 15864

• This child page: https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/
• Has a parent: https://www.va.gov/decision-reviews/legacy-appeals/
• And used to have a different parent: https://prod.cms.va.gov/disability/file-an-appeal, now archived. (You archived in 2020.)

When the old parent page was archived, and the new parent was published, we put a FE redirect in place. But: the URL for the child page was never updated. In the CMS, this child page still has the archived page as its parent, which generates a broken link from CMS breadcrumbs (because the breadcrumb in this case is generated from the URL alias), and generates noise for the helpdesk.

To fix this, we would like to:

1. Update the child page URL:
   • from https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/
   • to https://www.va.gov/decision-reviews/legacy-appeals/board-of-veterans-appeals/
2. Create a FE redirect from old to new URL.

However: @mnorthuis noted: Updating the URL and the redirect is what should be done. But this page and titling needs a content review before we make that change, because as it is, it is very duplicative to the core BVA page: https://www.va.gov/decision-reviews/board-appeal/veterans-law-judge-hearing/

Examples

• We’re updating a form and want to confirm we’re doing it correctly.
• We’re launching a new online tool to VA.gov and need support with our user flows.
• We need to make sure the content we’re using in our tool is written in plain language and follows the style guide.

Which are you doing?

• [ ] Launching a new page, tool, form, or app
• [x] 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
• [x] 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.

Have you worked with CAIA before?

• [x] Yes
• [ ] No

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

• Our next step is making technical changes to resolve noise in the broken links report
• Provide date if available: no firm target date

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
• [x] No

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
• [x] 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
• [x] No

If no ...

• Skip to the supporting artifacts section, below.

Supporting artifacts

Please provide links to supporting artifacts as available.

• Product outline:
• User flows:
• Prototype or mockups:
• If this is in Sketch, which version or specific page should we focus on?
• Content source of truth:
• Research plan:
• Any epics/issues that may be helpful:
• Link to testing accounts (please do not paste them in this ticket):

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.
• [x] 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.

• 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

  • If you are creating an experimental design, please also contact the DST.

• If you are requesting a11y support for user research, please complete this form, next.

### Content
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/71286

[kristinoletmuskat]

@jilladams hey! just checking whether you need IA to confirm these redirects or anything, or if all you need is these content changes to be able to move forward. If you have what you need from Mikki on the IA side that's cool.

[jilladams]

Thanks Kristin. Our team would really like to move ahead with the redirect fixes, to quiet noise in the broken link report. That would mean:

1. Update the child page URL:
   • from https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/
   • to https://www.va.gov/decision-reviews/legacy-appeals/board-of-veterans-appeals/
2. Create a FE redirect from old to new URL.

However, in the Slack thread, Mikki requested a content review of the legacy VBA page (https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/) first, because she's concerned that it's duplicative of the core BVA page: https://www.va.gov/decision-reviews/board-appeal/veterans-law-judge-hearing/, so the legacy page contents may change / URL may change or get archived, which would affect the redirect.

Since this has taken awhile to get prioritized, I wonder if @mnorthuis would be ok with us doing the main changes now, and updating again after content review as needed? (With a reminder that the intent here is to fix noisy monitoring as soon as we can.)

[mnorthuis]

Yes, go ahead and change the URL and implement the redirect. That will give the content team time to do the review and will eliminate noise for more important issues to be seen.

[jilladams]

Child page URL has been updated as well as a FE redirect: from https://www.va.gov/disability/file-an-appeal/board-of-veterans-appeals/ to https://www.va.gov/decision-reviews/legacy-appeals/board-of-veterans-appeals/

[mnorthuis]

Additional work is needed to move the page in drupal from disability to decision reviews I think...the page has the right breadcrumb and URL, but is showing the disability left nav. A left nav item will also need to be added to decision reviews for this page.

[kristinoletmuskat]

Hey @mnorthuis @jilladams I can look into this additional work next week

[jilladams]

Thank you, and we're happy to help however needed!

[kristinoletmuskat]

Hey ya'll, I can take a look at this this week and get back to you with next steps! Does that make sense @mnorthuis ?

[mnorthuis]

Thanks @kristinoletmuskat!

[kristinoletmuskat]

Added some work/comments in the content ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/71286

Seems like most of the work will be on their end.

[coforma-terry]

Shunting to backlog for now