Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG - Sev-3 - iOS - VoiceOver not announcing role of component #10185

Closed
5 tasks
rbontrager opened this issue Nov 14, 2024 · 6 comments
Closed
5 tasks

BUG - Sev-3 - iOS - VoiceOver not announcing role of component #10185

rbontrager opened this issue Nov 14, 2024 · 6 comments
Assignees
Labels
accessibility Accessibility awareness or needs for the ticket bug Used to identify a bug ticket that will be worked through the bug process global Issues for the global team sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this

Comments

@rbontrager
Copy link
Contributor

What happened?

Found while verifying another ticket. VoiceOver is not announcing the role of the component for iOS. So for example Android says "Active 1 of 2. Tab. Review your..." while iOS says "Active 1 of 2. Review your...".

Specs:

  • Device:
  • OS:
  • User Account:
  • Accessibility State:

Steps to Reproduce

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

  • Impact: High Low
  • Frequency: High Low
  • 3 - Low
  • 2 - High
  • 1 - Critical

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)
@rbontrager rbontrager added accessibility Accessibility awareness or needs for the ticket bug Used to identify a bug ticket that will be worked through the bug process global Issues for the global team QA Tickets require QA work / review sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this labels Nov 14, 2024
@ajsarkar28 ajsarkar28 added What's New and removed QA Tickets require QA work / review What's New labels Nov 25, 2024
@jennb33
Copy link

jennb33 commented Dec 11, 2024

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
Copy link

jennb33 commented Jan 2, 2025

1/2/2025 - @oddballdave is running this down. Currently there is no way to silo directly to iPhone to register for debugging and testing, and the seats that we have are taken. This budget is managed by a different department in VA and we won't know if there will be more seats in the new budget year (July 2025?)
This could be an issue in the code or in ReactNative. More to come.

@jennb33
Copy link

jennb33 commented Jan 6, 2025

1/6/2025 - @oddballdave is making changes and progress on this, but it may require a fix to the DS Library, which will determine if the work completes in Sprint 8.

@jennb33
Copy link

jennb33 commented Jan 7, 2025

1/7/2025 - per @oddballdave this will be a Design System Library fix - it has to be released to the app stores, then will the fix can be done.

@jennb33
Copy link

jennb33 commented Jan 8, 2025

1/8/2025 - move to Sprint 9 since this is dependent on the DS Library update.

@oddballdave
Copy link
Contributor

This issue has been moved to va-mobile-library#619.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Accessibility awareness or needs for the ticket bug Used to identify a bug ticket that will be worked through the bug process global Issues for the global team sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this
Projects
None yet
Development

No branches or pull requests

5 participants