Skip to content

[$250] Screen Reader: Many Pages: Elements are focused in a confusing order #77499

Description

@elisenwazuoke

Action Performed:

Precondition: User is logged in

  1. Using VoiceOver on iOS, open the app
  2. Swipe right to focus any chat and double-tap to activate it
  3. Swipe right to and note the focus order of the message input field and the Send button

Other Occurrences:

  1. New Chat
  2. Group Chat

Expected Result:

Focus should move logically through interactive elements, following the visual and functional order:
The text input field should receive focus before the Send button.

Screen reader users should encounter elements in the same order as sighted users.

Actual Result:

The Send button receives focus before the message input field.

Screen reader users may be confused, as activating the Send button before typing is meaningless.

Area issue was found in:

Chat

Failed WCAG checkpoints

WCAG 2.4.3 Focus Order
https://www.w3.org/WAI/WCAG22/Understanding/focus-order

User impact:

People with mobility impairments who must rely on keyboard access for operating a page benefit from a logical, usable focus order. People with vision impairments or disabilities that make reading difficult can become disoriented when tabbing takes focus someplace unexpected or when they cannot easily find the content surrounding an interactive element. Only a small portion of the page may be visible to an individual using a screen magnifier at a high level of magnification. Such a user may interpret a field in the wrong context if the focus order is not logical.

Suggested resolution:

Adjust the focus order so that the text input field is focused first, followed by the Send button.
https://appt.org/en/docs/react-native/samples/accessibility-order

Environment(s)

Apple iPhone 14 Pro - iOS 18.7.1, Wi-Fi - Native (No mobile browser)

Screenshots/Videos

Bug7009129_1763635139804.Send_button_incorrectly_receives_focus_before_the_text_field.mp4

Version Number: Production
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): NA
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA
Notes/Photos/Videos: Any additional supporting documentation Yes
Expensify/Expensify Issue URL: https://platform.applause.com/company/12102/products/36628/community-issues/7009129
Issue reported by: NA
Slack conversation: NA

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022009685288839664335
  • Upwork Job ID: 2009685288839664335
  • Last Price Increase: 2026-02-06
Issue OwnerCurrent Issue Owner: @TaduJR

Metadata

Metadata

Labels

AccessibilityIssues affecting WACG accessibility on any platform.BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions