Design intent Collaboration [VANotify Email Confirmation]

[toddstanich]

Steps to complete Design Intent Collaboration

• [x] Product Manager or Designer: create this issue and fill in feature name in the title and other bolded information appropriately
• [x] Link to this issue once created in #design in Slack; tag @ Crystabel Reiter @ Emily
• [x] Crystabel and Emily to schedule meeting with VSP reviewers and requesting team attendees (as listed below)
• [x] At least 2 days before scheduled meeting, you must provide list of artifacts below
• [x] VSP <> VANotify design intent collaboration meeting completed
• [x] Design experts leave feedback and relevant resources on this ticket
• [x] VFS designer acknowledge receipt of feedback/resources
• [x] VFS designer and all other requesting team attendees complete brief VSP Collaboration Cycle Feedback survey

Artifacts - please provide the following at least 2 days before the scheduled meeting

• Link to product outline (template)
• Sketches
• Lo-fi mockups - See comment below

Meeting attendees from requesting team

• Designer(s) (required): Todd Stanich
• Product Manager (optional): Qaysar Ahmad
• DEPO design lead (required as applicable):

Scheduling

Preferred Time Wednesday 6/17 11:30-12 ET

• Please reference the VSP Collaboration Meetings Calendar (times shown are ET)
• Note an available time slot within a recurring "[CALENDAR BLOCK] Review Group Office Hours" slot that works for your team and is at least 2 business days from now
• Write that preferred time slot here (on this ticket), and VSP will send you a meeting invite
• If no available time slots work for your team, write your availability and requirements here and Crystabel will reach out as needed

Additional Notes

Design experts will provide:

• A list of relevant design components and patterns (with URLs)
• A list of existing applications or pages with similar execution or patterns with URLs in staging

During this collaboration point, you will receive feedback from the following practice areas: design, accessibility

[CrystabelReiter]

Scheduled for Wednesday 6/17 11:30-12 ET

[toddstanich]

Attaching an early comp to aid in the discussion.

[mnorthuis]

Thoughts, comments, questions from IA:

• From email address
  • may be helpful to do some early thinking around whether you want to classify different types of emails with different "from" email addresses (i.e. confirmation@va.gov, benefit-application@va.gov, notification@va.gov, submission-status@va.gov, etc)
  • Agree that allowing users to reply to the email with questions is best, but if that is not possible, ensure there is content that indicates that and a bounce back email if they do try
• Would love to see mobile and plain text versions of the mock to show how content hierarchy lays out
• Ensure that subject line is clear and concise for what it is and provides trust
• Consider what content may need to be added to the confirmation page in regards to "You will receive an email confirmation..."
• Consider adding text to check status CTA that indicates they will need to log in

[1Copenut]

Thoughts from VSP accessibility using the Must, Should, Consider feedback model.

Feedback framework

• ❗️ Must for if the feedback must be applied
• ⚠️ Should if the feedback is best practice
• ✔️ Consider for suggestions/enhancements

Guidance

Must

• Test designs with a variety of thick and thin clients. Outlook, Thunderbird, Mail, Gmail, for example. VSP (Trevor) has used Litmus in the past. Litmus has several pricing models starting at $99 per month and up.
• Include a good alt text description for the VA logo. Some clients will not render images by default.

Should

• Conduct research with assistive technology users. It would be beneficial to have a participant who uses a screen reader and a participant who uses a screen magnifier.
• Reach out to Trevor and schedule a dry run for remote screen reader testing if schedules permit. I have done this with several teams. It's beneficial for moderators and observers who might be asked to troubleshoot technology.

Consider

• Making the inline links blue #004795 color. This is the recommended color in our VA typography guide

Definition of Done

• [ ] Team acknowledges the accessibility feedback in comment or Slack message, letting VSP know which items are being implemented, which are not.
• [ ] Schedule a dry run with Trevor for remote screen reader testing, if desired

[toddstanich]

Thanks @mnorthuis and @1Copenut. We've captured these items and will address them while building out the confirmation email.

[karlbrown-va]

@andreahewitt-odd @emilywaggoner @CrystabelReiter I came across this old issue I think it can be closed can you confirm? Our team is no longer working on VANotify