Midpoint Review - Content Feedback - Accredited Representation Management, digital submission designs (Appoint a Representative v2, Find a Representative v3, Representative Status Widget v2)

[KKitagawa-Bosch]

Next Steps for the VFS team

• [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• [ ] Must: replace all straight apostrophes with curly
• [ ] Must: be consistent in hyphenation of "VA-accredited" throughout
• [ ] Must: describe the term "accredited representative" when first used per content style guide
• [x] Consider: in the information for individual accredited representatives, consider saying "download this accredited representative's information" rather than "download the"
• [ ] Consider: when the header says "you don't have an accredited representative" but the user has just requested one, is there some way to make it clear that they don't have one "yet"?

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [x] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone

[oddball-lindsay]

Must: describe the term "accredited representative" when first used per content style guide

Confirmed that content is CAIA approved and we are okay to proceed as-is: https://dsva.slack.com/archives/C05L6HSJLHM/p1729261051422889

[oddball-lindsay]

Must: replace all straight apostrophes with curly

@KKitagawa-Bosch I'm trying to understand the priority of this from a development perspective, as we do have some straight apostrophes in our product work.

Is this required to match content standards, for standards sake? Or are there larger impacts to the UX or Accessibility when straight apostrophes are used?

[KKitagawa-Bosch]

This is the content standard. I've been chatting with some folks lately to determine if there is an accessibility reason to keep or change the standard, but for the time being it's just keeping everything consistent with the content style guide!