Staging Review finding: Summary box for direct deposit information may not be appropriate

shiragoodman commented 2 weeks ago

Need help? Please review how to read a Staging Review ticket. Tag @platform-governance-team-members on Slack if you need further assistance.

Product Information

Team: Modernized Check-in Product: eCheck-in Feature: Mileage-only Travel Claim Submissions for VA Facilities that use Oracle Health EHR Software

Findings details

VA.gov Experience Standard - issue: User encounters design components or patterns that are inconsistent or confusing. VA.gov Experience Standard - category: Consistency Launch-blocking: No Design System review: No Collab Cycle Reviewer: @briandeconinck (Accessibility)

Description

On appointment-travel-claim/travel-pay, the "Set up direct deposit" section is in the va-summary-box component. The summary box is intended to highlight whatever is most important on the page, and as such is coded as a role="region", with the heading assigned as its aria-label:

<div class="usa-summary-box" role="region" aria-label="Set up direct deposit">

The region role makes this content extra discoverable for screen reader users --- which makes sense when it's the main point of the page, but is a little less useful when it's secondary content.

I think I would say the direct deposit information counts as secondary content here. It's important, since you definitely want to get your money! But it's not the reason people come to this page and it doesn't really need that special boost for screen reader users.

Having this be in a region doesn't really hurt anything, but it's a little strange to have this section get extra prominence relative to the rest of the page.

Link, screenshot or steps to recreate

!["Set up direct deposit" section, presented in a light blue summary box.](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/Brian-75013-2.png?raw=true)

Recommended action

Review the guidance in VADS for the summary box and decide if this is an appropriate usage.

References

Accessibility Defect Severity: 4: Low. Consider fixing or exploring in 2-4 sprints post-launch.
WCAG Success Criteria: N/A
Modality: Screen reader
Design System Component: N/A
Design System Pattern or Template: N/A
Design System Foundation: N/A
Content Style Guide: N/A
Context: N/A

Next Steps for the VFS Team

[ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members with any questions or to get help validating the issue.
[ ] Ticket ownership: If you believe that this issue is out of scope, not your team's responsibility, or a Design System issue, comment and tag @platform-governance-team-members on your team channel in Slack to provide an explanation and who you believe is responsible. The Governance team will follow up.
[ ] Close this ticket when the issue has been resolved or validated by your Product Owner.