RLHecht
commented
3 months ago @moviedosoco You'll need to assess if the changes should be sent out to State or if they are minimal enough for you to translate. Thanks!
Open strelichl opened 3 months ago
RLHecht
commented
3 months ago @moviedosoco You'll need to assess if the changes should be sent out to State or if they are minimal enough for you to translate. Thanks!
moviedosoco
commented
3 months ago Hi, @RLHecht I compared the English against the Spanish page and did the necessary proofreading. There are several changes to be made, but they aren't complicated in translation. Some of the terms are already on other pages. Please take a look at the translation and proofread I made in the Google doc below. Thank you!
moviedosoco
commented
2 months ago @RLHecht @saratorres2 Changes were updated and saved in Drupal to match the English version. This is ready to review and publish. http://preview-prod.vfs.va.gov/preview?nodeId=62084
moviedosoco
commented
1 month ago @RLHecht and @saratorres2 The first sentence on the intro was updated to match the change made on the English page. The page is ready to publish with this change. https://preview-prod.vfs.va.gov/preview?nodeId=62084
EN- If you have new and relevant evidence to submit or want to request a review of your claim based on a change in law, a Supplemental Claim may be an option for you.
SPA- Si tiene pruebas nuevas y pertinentes para presentar o quiere solicitar una revisión de su reclamación basada en un cambio en la ley, una reclamación complementaria podría ser una opción para usted.
saratorres2
commented
1 week ago @moviedosoco I copy edited this page and published updates.
Issue Description
Changes were made to the English language version of the Supplemental Claims page, so we need to make those updates on the Spanish page now.
Reclamaciones complementarias
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