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

Rework Higher-Level Reviews static page to match VA.gov style #48533

Open RLHecht opened 2 years ago

RLHecht commented 2 years ago

Issue Description

We are reworking the decision reviews section to make sure the static pages match the voice and style of VA.gov. These pages were originally put on the site without much collaboration from the Sitewide Content and IA team. We need to make sure it meets our plain language standards and follows the same patterns as our other benefit detail pages.

This ticket is for the Higher-Level Reviews page.

Tasks

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

katherine-fung commented 1 year ago

I started work on this.

Preview: http://preview-prod.vfs.va.gov/preview?nodeId=3003

katherine-fung commented 1 year ago

Hi @laurwill,

This page is ready for your review: http://preview-prod.vfs.va.gov/preview?nodeId=3003

I made re-organized some of the information, and made other changes throughout the page to align it with the style of the Supplemental Claims page.

laurwill commented 1 year ago

Thanks @katherine-fung !

I'm actually going to pull in @aprocik1 to review this page — A, this is the second of 3 decision reviews pages we're updating to follow a new style/approach. I think a good first step would be to go into the Drupal revision history for the Supplemental Claims page and compare the previously published version to Katherine's recent updates, or do a quick sync together so you have context for these changes.

Then after you've reviewed, you and I can talk through any questions you have or edits you suggest. Let me know if you have questions about this as you get started!

aprocik1 commented 1 year ago

@katherine-fung and @laurwill: I updated the Higher-Level Reviews page to match the style of the Supplement Claims page. Here's the preview. Any and all feedback welcome.

Note: The preview contains unpublished edits from Danielle and Katherine. Before sharing the preview with partners, Laura will connect with Danielle to ensure we can move forward with her edits. Thanks!

aprocik1 commented 8 months ago

I moved this ticket to blocked because we're waiting on Danielle's approval to publish her draft edits or share them with stakeholders. Here's the Slack thread for reference: https://dsva.slack.com/archives/C03MP8MEPCN/p1695840530748999

aprocik1 commented 7 months ago

Update: Danielle made another round of health care related updates to this page. She reverted to the version of this page before the updates on this ticket were made. After this page is published with Danielle's edits, we should revert it to Chelsea's draft on 1/17/2024 at 2:55 pm ET. Then we should reincorporate Danielle's edits and get stakeholder approval.

This ticket is still blocked, because the page hasn't been published with Danielle's edits.

aprocik1 commented 2 months ago

Update: This ticket is no longer blocked. The HLR page has been published with Danielle's edits. There aren't any remaining draft edits in Drupal. I'm moving this ticket to in progress.

@katherine-fung and I met today to re-start this work. She's going to draft an updated HLR page that matches content patterns on the Board Appeals and Supplement Claims pages. I started this work in October 2023 in this SharePoint document.

katherine-fung commented 2 months ago

Hi @aprocik1,

Here's the preview of the HLR static page for your review: http://preview-prod.vfs.va.gov/preview?nodeId=3003

Thanks!

aprocik1 commented 2 months ago

Thanks @katherine-fung! I made some body copy edits and added a "related links" section to match the SC and BA pages. I'll share this with Beth today and we'll determine our next steps.

aprocik1 commented 2 months ago

Update: @bethpotts is going review this page. Here's the Drupal preview: http://preview-prod.vfs.va.gov/preview?nodeId=3003