Staging Review finding: Continuity of Care and Self-Entered Health Information download links not keyboard accessible

[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 complete a necessary flow or hits a dead end.
VA.gov Experience Standard - category: Usability
Launch-blocking: Yes
Design System review: No
Collab Cycle Reviewer: @briandeconinck (Accessibility)

Description

On /medical-records/download, the download links for the Continuity of Care file ("Download .xml file") and the self-entered health information file ("Download PDF") do not receive focus when tabbing through interactive elements with your keyboard. There is no way for a keyboard-only user to download these files.

Link, screenshot or steps to recreate

Recommended action

The links don't have an href attribute, which is what signals to browsers that they should be focusable. There must be an href attribute on all links, even a perfunctory # if there's some kind of onClick event.

References

• Accessibility Defect Severity: 1: Critical. Must be fixed before launch.
• WCAG Success Criteria: WCAG 2.1.1 Keyboard - Level A
• Modality: Keyboard
• 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.

[bryan-riley-va]

We have resolved the issue (MHV-65354). This was actually resolved as part of MHV-65229 as well. Screenshots of the validation in Staging are below.

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