IN PROGRESS - Accessibility Feedback — Design Intent Collaboration — AuthXp [Logged-in Homepage]

[jenstrickland]

Feedback framework

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

Description

This ticket contains the accessibility feedback/guidance for the Authenticated Experience [Logged-in Homepage] Design Intent Collaboration.

Must

• For icons that provide context, screen reader only text must be provided, so people who are unable to see the icons have that detail to support understanding.

Consider

• The same comments from the project kickoff are repeated here, consider how progressive enhancement and progressive web app methods may be useful in achieving user goals in inclusive ways.

• As the AuthXp usually does, consider continuing to arrange ad hoc conversations to collaborate with the VSA accessibility specialist. This may also happen asynchronously through Slack messages or tickets.

• Consider a mobile-first design approach to clarify hierarchy.

• Consider evaluating decisions on mobile devices regularly. For example, the subtext on the tab/cards, while the text may be 16px, it can be very small and hard to read on mobile devices in challenging lighting although it meets contrast requirements. It may be hard for low-vision users to read the copy, particularly since VA.gov on mobile doesn't support a user increasing font size in settings. The enclosed screenshots look different on a computer than they do on a phone, of course.

Point of Contact

VFS Point of Contact: Jennifer

Definition of done

1. Review and acknowledge feedback.
2. Fix and/or document decisions made.
3. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.

[jenstrickland]

cc @1Copenut for VSP review

[1Copenut]

@tressaellen & @jenstrickland I only have a few items to add, and they're all considers, with one question for my own understanding:

Question:

• The first view for Charles Darcy will replace the logged out, default VA.gov homepage when users log in, correct?

Consider:

• I lean toward the left navigation instead of tabs for managing views. The tabs command more vertical real estate at mobile size, and my hunch is there's a slightly larger cognitive load for parsing more than 3-4 horizontal tabs than a vertical list of links.
• I ❤️ the discussion point of having calls to action for new benefits or things veterans might not have previously signed up for. This is an excellent way to handle the first-run experience and as new services or benefits get brought into the fold.

[jenstrickland]

@1Copenut

Regarding the tab navigation, my take on the comps is that the tab navigation is presented as the stacked mini-cards. The left navigation would collapse into a hidden menu, which we already have a stack of pancakes of collapsed items.

[tressaellen]

Thank you for reviewing this! @1Copenut - to answer your question, yes the first view for Charles Darcy will replace the logged out, default VA.gov homepage when users log in.