Repository navigation
Description
Action Performed:
Precondition: User is logged in
- Using VoiceOver on iOS or TalkBack on Android, open the app
- Swipe right to focus the Account tab and double-tap to activate it
- Swipe right to focus the Profile button and double-tap to activate it
- Swipe right to focus the Status menu item and double-tap to activate it
- Swipe right to focus the Vacation delegate menu item and double-tap to activate it
- Note if the available list of suggestions is announced
- Swipe right to focus the text field and enter any search query
- After loading is complete, note if the search result suggestions are announced
This is a global issue affecting all screen with text fields and search result suggestions
Examples:
- Search
- Group Chat: Start Chat
- Profile: Country
- Profile: Timezone
- Wallet: Add Bank Account
- Reports
- Create Workspace > Company Cards: Add Card
Expected Result:
When search suggestions appear, both initial suggestions (before typing) and resulting suggestions (after entering a query), screen readers should announce that there are available suggestions. Examples:
"Search suggestions available. 12 results".
This announcement should occur automatically, shortly after the user has finished typing and loading is complete, without requiring the user to explore the screen manually.
Actual Result:
Before typing, the suggestions list is visually shown but not announced.
After entering a search query, new results appear, but screen readers provide no status update or hint that results are available.
Users must discover suggestions manually by swiping, which may give the impression that no results exist.
Area issue was found in:
Profile > Status
Failed WCAG checkpoints
WCAG 4.1.3 Status Messages
https://www.w3.org/WAI/WCAG22/Understanding/status-messages
User impact:
When appropriate roles or properties are assigned to status messages, the new content is spoken by screen readers in such a way as to assist blind and low vision users. Assigning proper roles or properties to status messages provides possible future uses and personalization opportunities, such as the potential to be exploited by assistive technologies created for users with some cognitive disabilities.
Suggested resolution:
Use accessibilityLiveRegion="polite" on Android and AccessibilityInfo.announceForAccessibility on iOS to notify screen readers whenever the suggestions list changes to ensure they announce them, for example:
- 'Search suggestions available. 12 results'
https://appt.org/en/docs/react-native/samples/accessibility-live-region
https://reactnative.dev/docs/accessibility#accessibilityliveregion-android
https://reactnative.dev/docs/accessibilityinfo#announceforaccessibility
Environment(s)
Apple iPhone 14 Pro - iOS 18.7.1, Wi-Fi - Native (No mobile browser)
Samsung Galaxy Note10 Plus - Android 12, H0T Mobile - Native (No mobile browser)
Screenshots/Videos
Bug7006896_1763522947278.Displayed_search_result_suggestions_are_not_announced.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/7006896
Issue reported by: NA
Slack conversation: NA
Issue Owner
Current Issue Owner: @mallenexpensifyUpwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022032270284819723181
- Upwork Job ID: 2032270284819723181
- Last Price Increase: 2026-03-13
- Automatic offers:
- aimane-chnaif | Contributor | 110767844
Activity
melvin-bot commentedon Jan 6, 2026
This issue has not been updated in over 15 days. eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
marufsharifi commentedon Feb 1, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When search suggestions appear (initially or after typing), screen readers do not announce that suggestions are available, so users don’t know the list updated.
What is the root cause of that problem?
Suggestion lists update visually, but there is no live‑region or announcement when the data changes, so screen readers never hear “suggestions available.” This happens in two places:
accessibilityLiveRegionorannounceForAccessibility, so the update is silent.)App/src/components/SelectionList/components/TextInput.tsx
Line 71 in 9618ba6
App/src/components/SelectionList/components/TextInput.tsx
Lines 113 to 146 in 9618ba6
What changes do you think we should make in order to solve the problem?
search.suggestionsAvailable) with count + optional query.AccessibilityInfo.announceForAccessibility<Text>that updates when suggestions changeVideo demo of the fix:
annouces-search-suggestions-and-results.mp4
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None
What alternative solutions did you explore? (Optional)
melvin-bot commentedon Feb 16, 2026
@suneox 12 days overdue now... This issue's end is nigh!
suneox commentedon Feb 16, 2026
This issue still depends on #77572, and we’re still working on that PR.
64 remaining items
melvin-bot commentedon Apr 6, 2026
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
mallenexpensify commentedon Apr 7, 2026
Payment Summary
Contributor: @ShridharGoel due $500 via NewDot
Contributor+: @aimane-chnaif paid $500 via Upwork
@aimane-chnaif plz complete the BZ checklist and tag me in a post once you have. Thx
aimane-chnaif commentedon Apr 7, 2026
Accessibility issue
JmillsExpensify commentedon Apr 8, 2026
$500 approved for @ShridharGoel
marufsharifi commentedon May 11, 2026
@mallenexpensify, I have a question about this issue.
I was initially assigned/hired, had already opened a PR, tested, and requested review of the PR before it was reassigned due to the deadline and estimation concerns here:
https://expensify.slack.com/archives/C01GTK53T8Q/p1772739593580499
pr colosed based on this comment.
Am I still eligible for compensation in this case? This is a similar case to here.
Thanks in advance for your guidance!
mallenexpensify commentedon May 11, 2026
👀 above plz @rushatgabhane
rushatgabhane commentedon May 11, 2026
Similar here, the solution by @ShridharGoel is different from @marufsharifi's PR. It also had anti patterns like platform specific code in files
So I don't think it is eligible for comp 😅