BUG - sev-3 - All - Claims file upload: error request screen reader callout for missing file/photo is inconsistent/less helpful

[TKDickson]

What happened?

During claims file request upload, if a veteran adds a photo (or a file), and then removes it and attempts to submit, we throw an error that lets them know that a file/photo is required.

However, the screen reader treatment of that error is inconsistent with, and less helpful than, the other error messages on the page. Video example.

The two missing elements are:

• Announcing the word "error" as part of the error message
• That the error message + element you'd need to interact with to correct the error message should be a single swipe target (not two swipes, like they are currently)

Specs:

• Device:
• OS:
• User Account: +12345 (login.gov)
• Accessibility State: screen reader on

Steps to Reproduce

Turn on screen reader for your device.
As Arfan (+12345 in login.gov), go to a claim with an open file request (Claims > [specific claim] > review file requests > [specific file request]).
Pick 'select a file', then upload a file, then delete the file, then attempt to submit the file upload. Swipe through the error messages for each field, and notice the problems with the file upload button's error message.
Back out of this workflow, then repeat the above step with the photo upload ("select a picture") workflow. Same problem.

Desired behavior

Should be a single swipe target, that announces something like "Error: file is required. Select a file, button, double-tap to activate" (for the file workflow, and similarly worded for photo workflow)

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

• Impact: Low
• Frequency: Low

• 3 - Low

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• Steps to reproduce are defined
• Desired behavior is added
• Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
• Estimate of 1 added (for front-end tickets)
• Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

[jennb33]

12/19/2024 - Possible new issue for MFS?