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

[low] Chrome + Talkback: Focus lands twice on the 'text field'. #8670

Closed
Stutikuls opened this issue Apr 18, 2022 · 1 comment
Closed

[low] Chrome + Talkback: Focus lands twice on the 'text field'. #8670

Stutikuls opened this issue Apr 18, 2022 · 1 comment

Comments

@Stutikuls
Copy link

Stutikuls commented Apr 18, 2022

Action Performed:

  1. Using Chrome + Talkback , open URL staging.new.expensify.com
  2. Navigate to Setting using swipe gesture and press double tap on it.
  3. Navigate to any workspace using swipe gesture and press double tap on it.
  4. Navigate to manage members using swipe gesture and press double tap on it.
  5. Navigate to invite using swipe gesture and press double tap to activate.
  6. Navigate to the text field using swipe gesture.
  7. Observe the issue.

Expected Result:

Focus should lands on the each item once. Focus should land on the 'Text field' once.

Actual Result:

Focus lands on the 'Text field' twice. When focus lands on the text field there is no announcement and on the second swipe it announces "Name edit box"

Other occurrences
Same issue also repro on #8689

Workaround:

Yes

Area issue was found in:

Manage members

Failed WCAG checkpoints

2.4.3

User impact:

Keyboard and screen reader users might be confused having extra focus on single element.

Suggested resolution:

Ensure focus lands on the 'Text field' only once.
Refer to:
https://www.w3.org/WAI/WCAG21/Understanding/focus-order

Platform:

  • Android

Version Number: v1.1.55-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Stuti

8437.-6.-Focus.lands.twice.on.the.text.field.mp4
@melvin-bot
Copy link

melvin-bot bot commented Jul 4, 2022

@Stutikuls, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant