DST Staging Review: Annotate accessibility information in screenshots.

[shiragoodman]

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

Design System Staging Information

Component: Help users to... Know when their information is prefilled
Staging Review ticket: AEDP, Design Patterns, Help users to... Know when their information is prefilled

Findings details

VA.gov Experience Standard - issue: User doesn't have enough information to complete a task.
VA.gov Experience Standard - category: Comprehension
This is an issue with the: guidance
High-priority: No
Collab Cycle Reviewer: @briandeconinck (Accessibility)

Description

VFS teams sometimes struggle with creating an accessible page structure. Including some of that information, even incidentally in the screenshot annotations, would be beneficial.

Recommended action

In particular, I'd love to see heading levels annotated, eg. under the Prefill check page, the heading levels for Mailing address (h3) and Current mailing address (h4, styled as h3).

References

• Accessibility Defect Severity: 4: Low. Consider fixing or exploring in 2-4 sprints post-launch.
• WCAG Success Criteria: N/A
• Modality: 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 DST

• Close the ticket when the issue has been resolved or validated by your Product Owner
• If your team has additional questions or needs Governance help validating the issue, please comment on the ticket
• If this ticket has a high-priority label, please address as soon as possible so VFS teams are not impacted
• If this ticket has a consider label, please consider for future implementation

[msbtterswrth]

@kristen101606 could you update the annotated screenshots to include this please?