Update address for VBA insurance center on HLR and Supp Claims pages

strelichl commented 1 year ago

Issue Description

VBA’s Insurance Service now uses centralized mail and would like to update the address section on the Higher-Level Review page.

Since there are additional draft changes in this page, we'll need to revert to the published version, fix the address, publish, revert to the draft with in-process changes, remake the address change and leave it in draft.
But one of the draft changes included a different accuracy correction on the pension addresses. We should implement those changes now, following this model:

This new insurance address will also need to go on the Supplemental Claims page.

In the Insurance section under “Find addresses for other benefit types”, update the statement “Please refer to your decision for instructions on how to submit the form” to reflect the following address:

Department of Veterans Affairs Attention: Insurance Center PO BOX 5209 Janesville, WI 53547

For follow up questions that require subject matter expertise, we can reach out to POC from Insurance Service, Melinda Alexander.

Tasks

[x] LW: Assess request
[x] AP: Draft Higher-Level Reviews page
[x] KF: Share Higher-Level Reviews preview with stakeholders for approval
[x] AP: Draft Higher-Level Reviews and Supplemental Claims pages with stakeholder feedback
[x] CL: Copy edit and publish both pages
[x] AP: Revert both pages
[x] AP: Save drafts of both pages with address updates
[ ] LS: Check if any additional pages need this address change and open tickets, as needed

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

[ ] Update is live on the site

laurwill commented 1 year ago

@aprocik1 @strelichl I've updated top of this ticket to reflect more specific next steps — let me know if you have questions!

aprocik1 commented 1 year ago

@katherine-fung: I've incorporated the following changes on the Higher-Level Reviews page:

Updated to "disability compensation" for clarity and consistency
Updated to "life insurance" for clarity and consistency
Added life insurance address
Added pension address
Replaced collapsible accordion with "all other benefit types" bullet point

Drupal preview

After stakeholder approval, I'll make identical updates to the Supplemental Claims page. Thanks for sharing these!

katherine-fung commented 1 year ago

Thanks @aprocik1! I scheduled an email to the stakeholders Monday morning.

aprocik1 commented 1 year ago

@chelsealevinson: The Higher-Level Reviews and Supplement Claims pages are ready for your review. The only changes on these pages are within the "file by mail" sections - we've updated addresses and changed formatting. After you've published, please tag me in a comment on this ticket. I'll revert edits and save updated draft pages in Drupal. Thanks!

chelsealevinson commented 1 year ago

Confirming that I copy edited + published these pages. Thanks again for your help, @aprocik1 these are ready to be reverted!

aprocik1 commented 1 year ago

@strelichl, I've moved this ticket to validate for your final steps. Thanks!

department-of-veterans-affairs / va.gov-team