Staging Review finding: Heading structure for medical records download accordions

[shiragoodman]

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

This ticket was part of a merged Staging Review with MHV Medical Records Download Records, Flow/Images and Settings

Product Information

Team: vfs-mhv-medical-records
Product: MHV Medical Records
Feature: Phase 1 Radiology Flow/Images, Download Records, and Settings

Findings details

VA.gov Experience Standard - issue: User can't determine next steps in a flow.
VA.gov Experience Standard - category: Findability
Launch-blocking: No
Design System review: No
Collab Cycle Reviewer: @briandeconinck (Accessibility)

Description

On /medical-records/download, the "Other records you can download" heading is an H2, followed by accordions with sections of content for records. Visually and from the content, it's clear that these accordions "belong to" the "Other records" H2, but the accordion toggle elements are themselves also H2s.

Many screen reader users navigate a page by heading, where their screen reader will announce heading text and the heading level. This provides information about the structure of the page and the relationship of different sections of information to each other. When headings have the wrong level, a user may get confused or even disoriented.

Link, screenshot or steps to recreate

Recommended action

The accordions should be H3 headings, hierarchically nested beneath the H2.

References

• Accessibility Defect Severity: 2: High. Should be fixed in 1-2 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.

[lichellebain]

https://jira.devops.va.gov/browse/MHV-65367

[bryan-riley-va]

Closed 2/11/25