BUG - Sev 3 - Android (maybe all) - "claims history" text not wrapping, infringing on "VA" header space

[DJUltraTom]

What happened?

on android with text enlarged if you navigate to claims history you can see the "claims history" getting all up in th eVA headers personal space, creating a sort of tension between the two elements that if occurring in a physical manifestation might result in a shoving match or an exchange of heated words... in this case that tension is transmitted to the viewer in the form of "cluttery and claustrophobic vibes"

Specs:

• Device: pixel 4A
• OS: 14
• User Account: any one with claims history
• Accessibility State: n/a

Steps to Reproduce

• on a device with large "wonky" text settings log in using an account with claims history,
• navigate to the claims history page
• observe the header

Desired behavior

the app should present a clean and uncluttered appearance

Acceptance Criteria

tbd

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/11/2024 - @kellylein @timwright12 @oddballpete @Eallan919 @ATeal @TKDickson The MFS team will be taking this ticket into Sprint 7, (12/14/2024-12/27/2024)

[jennb33]

12/16/2024 - Per @ATeal work is in progress

[jennb33]

12/18/2024 - @ATeal has the code, and is reviewing.

[jennb33]

12/19/2024 - Don't think we have to do much for a11y at the moment, this is to be finalized by @ATeal as he is reviewing the ticket. He can push out the non-accessibility version on 12/20/2024, if necessary.