Request for content updates on PACT Act page

[laurwill]

Issue Description

Angie sent a request from the Deputy Chief of Staff to add and update content for survivors on the PACT Act page, including:

• 6 additional Q&A sections
• Updates to DIC content
• Updates to burials content

We'll need to assess the need for these Q&As using available data. Michael confirmed in the email thread that this request was not driven by any specific data about frequency of calls/questions.

https://app.zenhub.com/files/133843125/e70cb09b-6dda-45d8-a989-759025392071/download

Here's the approved approach we sent, with Michael's responses:

PACT content changes — approved approach.docx

---

Tasks

• [x] Assess need for additional Q&As
• [x] Send suggested approach to partners
• [x] Draft content updates in Drupal
• [x] Send to partners for approval (Laura)
• [x] Copyedit (Chelsea or Megan)
• [ ] Send to OPIA for approval (Danielle)
• [ ] Publish (Chelsea or Megan)
• [ ] Flag for Ana and Randi to send to translators once it's published (Chelsea or Megan)

Prepublishing checklist

## For all VA.gov pages (including those in Resources and Support) ### Before you begin - [ ] Confirm that there are no updates in draft by other content authors that aren't ready to be published. Check the revision log and then confirm with the content author who made the previous edits that the page is ready to publish. ### Accessibility standards - [ ] If your link or button will take the user off VA.gov, confirm that the text for the link or button contains a purpose and a target. The user should be able to tell from the link or button text what the call to action is (the purpose) and where they will end up if they click on the link (the target). The following link is an example of this:
[Read more about making links accessible on AccessibilityOz](https://www.accessibilityoz.com/2014/02/links-and-accessibility/)
**Note:** When you direct the user to another VA.gov page, the link only needs to contain text indicating purpose (the call to action). - [ ] Confirm all phone numbers are in aria labels. [Learn how to code numbers with aria labels](https://design.va.gov/content-style-guide/dates-and-numbers#phone-numbers) - [ ] Confirm that the hierarchy of section and subsection titles is correct (H1 to H2 to H3—levels shouldn't be skipped). [Learn more about section titles](https://design.va.gov/content-style-guide/page-titles-and-section-titles) - [ ] Replace any sighted language ("view," "see," "look") with a word that's inclusive of our screen reader users ("check," "go to," "review"). - [ ] Avoid using other ability-focused language. ("hear back from") ### Link standards - [ ] Confirm that links work (aren't broken—no error message) and point to the intended page (you pasted in the correct URL or chose the correct node ID). - [ ] Confirm all link text is 100 characters or less. - [ ] Check that you've selected a node ID for all links pointing to VA.gov (internal) pages. Only paste in a URL if the page you're linking to doesn't live in our CMS (isn't one of our modernized pages). [Learn how to add node IDs in Drupal](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/sitewide-content/how-to-do-different-tasks/linking-with-node-ids.md) - [ ] Check that all anchor/jump links are pointing to a node followed by # and the header identifier (Example: /node/47278/#information-for-survivors). Double check all anchor/jump links post-publish. ### CMS standards - [ ] Make sure all apostrophes and quotation marks are curly not straight. (Once this is automatic in Drupal, we can remove this item.) - [ ] If there are alerts at the top of the Drupal Edit node for broken links, redirected links, or links to unpublished pages, correct the issues. If there's an alert for a broken link but the link is actually working, report the issue to the CMS help desk. [Read more about link alerts in the CMS knowledge base](https://prod.cms.va.gov/help/cms-basics/how-to-fix-broken-links-and-redirects) - [ ] If publishing a brand-new page, confirm the left nav and url are set up correclty. (If the page is a child page, the section needs to be the same as the parent page in order for the left nav to show.) [Learn how to set up a url and left nav in Drupal](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/sitewide-content/how-to-do-different-tasks/adding-left-nav-and-url.md) - [ ] Check if the page has a new or updated alert. If so, publish the alert separately. ### Additional checks for translated articles - [ ] If we don't have updated translated versions, add the alert that links to the corresponding English page and lets users know that the translated pages aren't up to date.

Acceptance Criteria

• [ ] Page is updated with suggested Q&A additions (if needed)

[laurwill]

Sent suggested approach to Michael on Friday July 7 (Danielle copied on thread). Will pick up this work when I'm back on 7.17.

[katherine-fung]

Hi @laurwill,

I reviewed the notes from you and stakeholder for this work.

I have a few questions and notes:

1. For burial benefits, is submitting a new application the best way to re-apply? My draft assumes this is the case. When I searched va.gov, I didn't find any special instructions for re-apply for burial benefits, but I realize there may be something I don't know here.

2. For the new FAQ about examples/scenarios, the stakeholders provided 6 examples that include a hypothetical relationship with the Veteran, i.e. "My spouse served in the Vietnam War and..." and "My child served in Afghanistan and..."

Because the stakeholders want to emphasize that these examples don't cover all the situations in which a survivor might be eligible, I'm wondering if we should leave these relationships out of the examples, and say, "The Veteran served..." I'm happy to put them back though if we feel they make the examples more illustrative.

I drafted copy with the 6 examples that stakeholders provided. A few of the examples feel like they overlap, but without context for why the stakeholders identified these examples, I didn't change any of them.

Here's the draft of 2 FAQs for your review:

PACT Act FAQs.docx

[laurwill]

Thanks @katherine-fung ! I should have noted more clearly that we don't need to include all 6 scenarios the partners provided, especially with the space constraint in the single Q&A section.

And we got confirmation that you should reapply for burial benefits if you were previously denied.

A (who I still cannot tag for some reason) is going to take a first pass at reviewing this and then we'll post back. Thank you!

[aprocik1]

Hi @chelsealevinson and @megzehn! We've completed part of the updates requested in this ticket. And we've received accuracy reviews from relevant SMEs and stakeholders. But before publishing this update, Danielle needs to send it to OPIA for approval.

Can you copyedit this Drupal node by 2:30 pm ET today? That way we can confirm next steps with Danielle at our meeting this afternoon. If that's not doable, we can aim for Wednesday's meeting with Danielle. Thanks!

[RLHecht]

@strelichl can you add a task to this to set up the translation work once these changes are published? We'll need tickets for both Tagalog and Spanish.

[laurwill]

Just noting this was copyedited and Danielle will share with OPIA for approval.

[laurwill]

Hi @DanielleThierryUSDSVA ! Here's that ticket I mentioned in a recent sync — I think the next step was for you to share this updated Q&A on the PACT Act page with OPIA.

• We changed the question about reapplying for DIC to include how to reapply for all 4 relevant types of survivor benefits
• We added specific instructions to select the PACT Act options on the DIC form

Let me know if you need anything else or have any questions about the changes we made here!

[strelichl]

Danielle putting this on her list to follow up, leaving in blocked for now