Open RLHecht opened 1 year ago
@ABeltran77 The word doc above has all 3 Pension pages we sent out to the translation team so you just need to scroll to the how to apply one. For the eligibility page that's missing the H1 and the intro text could you translate those and we'll have State QA when we send them the live link. Thank you!
@RLHecht Got it, thanks! The H1 and the intro text has been translated on the Eligibility For Veteran's Pension page.
@RLHecht @strelichl I built the How to Apply for a VA pension as a Veteran page (Cómo tramitar un a pensión de VA para veteranos) but need some corrections.
@megzehn I was able to get the widget up but and information alert (I think) pops up on the page. I tried removing it but no luck. Can we screen share to review? A couple notes:
On the English Drupal page there is a pink Alert regarding the coronavirus pandemic. That was not on the translated docs received back from State.
I added (por sus siglas en inglés) after PMC.
@RLHecht - Megan and I met to problem solve the error message that appears on the Spanish page. She suggested bringing this up to you as it is not translated into Spanish. Let's connect when you have a chance to discuss.
Thanks, Ana. I think for now we should hold off on moving these Pension pages forward until the work is completed on the English pages with the online form. Once the alert language is finalized we could send it out for translation and update the Spanish pages. Can we move this to blocked?
@strelichl Katherine let me know that the 527 form should be back to 100% next week. Once that's the case we should be able to pull this back in. @ABeltran77 you'll have to check if any of the content on the English page has changed from what we initially sent out to be translated and if we will need to send out any additional content before we can move forward with the page. Thanks!
@RLHecht I picked up this work where it was left off. By comparing the English page with the Spanish translation that was received in 2023, we need to send out the updated content for translation. I will prepare the Word document with the updates to send to State. Once we receive it back, we can resume building the Spanish page in Drupal, review it, and publish it.
@RLHecht The Word document was created and uploaded into the Translation Tracker, and emailed to State on 9/19/24.
@moviedosoco here's the translation back from State:
SPA-FINAL_How to apply for a VA pension as a Veteran_UPDATED CHANGES_for translation_09192024.docx
@RLHecht This page is built and updated in Drupal.
@saratorres2 The page Cómo tramitar una pensión de VA como veterano is ready to be reviewed and published. https://preview-prod.vfs.va.gov/preview?nodeId=62476
Thank you!
Issue Description
As part of our ongoing effort to have more multilingual content on our site, we need to publish the core Pension pages in Spanish. This includes How to apply for a VA pension as a Veteran.
We need to build the page in Drupal, review, and publish.
Content from translation team: LS-2022-0118394-G-SPA-FINAL_Pension content for Spanish translation Batch 1 (1).docx
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