Determine privacy act modal content

[DanielleThierryUSDSVA]

Issue Description

Determine content requirements for privacy act modal content

• Privacy modal appears to reference "education" specifically across benefit forms. This content needs to be customized for each benefit. How do we ensure we have approved content to use for each benefit?
• Language in Respondent Burden and Privacy Act Notice uses "We" and "The VA" and "VA". Can we get approval to change to "We" throughout per VA.gov style guide?
• Can we get approval to also incorporate plain language tweaks (such as active voice)?

---

Recommendations

Near-term

• [ ] Content and design leads to communicate to product teams the need to review and update their products' content. Each product's content should match the information on the relevant paper form.
• [ ] Each design team to review their products' content and update as needed to match relevant paper form.
• [ ] Add correct privacy/burden reduction content as a launch blocker for platform content reviews
• [ ] Consider adding a note in Storybook component to make sure to use the right form's content for this component: https://design.va.gov/storybook/?path=/docs/components-ombinfo--default

Longer-term

• [ ] Audit this content in existing forms for a plain language review/edit. This will need to go in the sitewide content team's backlog, and is not a high priority given all the other priorities.
• [ ] Incorporate working with privacy officers to edit this content for plain language into the process for new products.

[DanielleThierryUSDSVA]

@sshein I'd love to get your thoughts on how best to communicate the need to check/update content to product teams. Beth and I can communicate to the teams we work with. We can also post something in the design channel. Thoughts on adding a note w/ the component or other ways to communicate?

@peggygannon as we chatted about in slack, since this is legal info, I would recommend making having the correct legal/privacy info a launch blocker in platform reviews. Let me know if you have questions/thoughts on this - thanks! @shiragoodman

[sshein]

I thinking posting to the #design channel is good and then I can make sure my whole team sees it. It is probably a good idea to bring up on the Team of Teams meeting as well so all app teams and their POs/PMs are aware. Does the sitewide content team present at team of teams I kind of forget

[DanielleThierryUSDSVA]

Oh, yeah, ToT is a great idea - thanks, @sshein! @RLHecht presents at ToT for us, yes. Randi, let's connect on communicating this in ToT. Thanks!

[DanielleThierryUSDSVA]

@sshein Quick note that there's a 2nd piece to this that's popping up. The 10-10EZ has different info in staging than in production, and it looks like a burials form has a similar issue. So tracking down what's going on around that and then will move forward with these steps. Thanks!

[sshein]

interesting... thanks for the update