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 - All - Voiceover for the pagination button is saying <previous/next> page - link - <previous/next> page instead of just <previous/next> page - link #9636

Closed
5 tasks
rbontrager opened this issue Sep 20, 2024 · 3 comments
Assignees
Labels
bug Used to identify a bug ticket that will be worked through the bug process Closed - Deployed/Fixed front-end Ticket requires front-end work global Issues for the global team mobile-feature-support QA Tickets require QA work / review sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this
Milestone

Comments

@rbontrager
Copy link
Contributor

rbontrager commented Sep 20, 2024

What happened?

Voiceover for pagination buttons is saying <previous/next> page - link - <previous/next> page instead of just <previous/next> page - link

Specs:

  • Device: any
  • OS: any
  • User Account:
  • Accessibility State: Voiceover/talkback on

Steps to Reproduce

  • log into an account with pagination occurring on one of the features
  • navigate to feature with pagination navigation using talkback/voiceover
  • observe the screenreader announcement of the navigation buttons (arrows)

Desired behavior

voice over should read the pagination arrows as <previous/next> page - link

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)
@rbontrager rbontrager added 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 Sep 20, 2024
@TKDickson TKDickson added the front-end Ticket requires front-end work label Oct 24, 2024
@TKDickson TKDickson assigned TKDickson and dumathane and unassigned TKDickson Nov 22, 2024
@rbontrager rbontrager self-assigned this Nov 26, 2024
@DJUltraTom
Copy link
Contributor

updated ticket description, repro steps, "what should happen" and severity sections

@DJUltraTom DJUltraTom self-assigned this Nov 29, 2024
@DJUltraTom
Copy link
Contributor

Using an on demand builds on both android and iOS I verified the pagination buttons no longer announce twice.
QA approves this build.

@DJUltraTom
Copy link
Contributor

verified this was in the RC build, closing

@kellylein kellylein added this to the v2.43.0 milestone Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to identify a bug ticket that will be worked through the bug process Closed - Deployed/Fixed front-end Ticket requires front-end work global Issues for the global team mobile-feature-support QA Tickets require QA work / review 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

6 participants