outerpress
commented
2 months ago @laurwill here's the ticket we talked about in the SME sync today. Design file is linked in the ticket, as are the collab cycle tickets that this came out of.
For next steps, I'm thinking we need you to create the resources page, and make any content adjustments there. After that this one should be pretty much ready to go.
Let me know if you want a separate CAIA ticket for this one. Thanks!
Task Description
This moves the instructions to prepare for a video visit to a new resources page, and updates the content in those instructions. This follows a similar pattern to what we used for medication review.
Notes and References
A/C below comes out of these collab cycle tickets:
Acceptance Criteria
[ ] Must: Look at your additional info components and the amount of content in them. Review the guidance on how much content should be in additional info components. Specifically the "How to set up your device" additional info.
[ ] Must: In the "video appointment" section, the content currently says "we'll add the link the join", but does not specify where the link will appear. Some additional content is needed so users know where to look for that link in the future.
[ ] Must: In the "video appointment" section, the guidance tells users to "click the join session button". We should avoid the word "click" as not all users will actually be clicking on buttons depending on what device they use. (https://design.va.gov/content-style-guide/neutral-and-inclusive-language#language-that-doesnt-assume-an-ability-or-device)
[ ] Must: several locations in the content use straight apostrophes ('). Design system guidance asks that we always use curly apostrophes (’). I noticed this specifically in the "travel reimbursement", "video appointment", and "phone appointment" sections, but comb through to make sure there aren't other instances!
[ ] Should: In the "video appointment" section, users are told to be in a "well-lighted" room. While this is technically correct, it is a more formal/less common phrasing, and should be replaced with "well-lit" to better meet plain language standards.
[ ] Instead of using 1 additional info component, link to another page, consider an Accordion, or shorten the content. Collaborate with a member of CAIA to edit content and explore alternatives. You could also break this into 2 additional info components.
[ ] Design spec is complete
[ ] Dev tickets have been created
Deliverables