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 Status Emoji button and double-tap to activate it
- Swipe right to focus the emoji category emojis and double-tap to activate it
- Note the behavior after selecting any emoji category and the announcement
This issue reproduces in all screens with the emoji option
Examples:
- New chat
- Group chat
Expected Result:
When a user selects an emoji category button (e.g., "Frequently used", "Smileys", "Animals"), the screen reader focus should move to the corresponding category heading at the top of the emoji list and announce it.
This announces that the view has updated and helps the user understand that the emoji list has changed.
Expected screen reader announcement:
"Smiley, heading"
"Animals, heading"
Actual Result:
Android (TalkBack): No feedback; the user receives no indication that the category changed.
iOS (VoiceOver): Re-announces only the button label (e.g., "emoji Picker.headers.frequently used, button"), giving no indication that the content changed or that a new category is active.
Focus does not move to the category heading or emoji grid.
Area issue was found in:
Profile > Status
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:
After selecting a category, programmatically set focus to the category heading and ensure it is announced, using AccessibilityInfo API.
https://appt.org/en/docs/react-native/samples/accessibility-focus
https://reactnative.dev/docs/accessibilityinfo
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
Bug7008046_1763623857687.No_announcement_or_focus_change_after_selecting_an_emoji_category.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/7008046
Issue reported by: NA
Slack conversation: NA
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 2, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The emoji category shortcuts don’t provide enough screen reader feedback. Two gaps:
What is the root cause of that problem?
Category shortcuts only scroll the list, and the headers are not focusable or targeted by SR focus. So the screen reader stays on the shortcut button and never lands on (or announces) the list header.
App/src/components/EmojiPicker/EmojiPickerMenu/index.native.tsx
Lines 71 to 77 in 8372553
App/src/components/EmojiPicker/EmojiPickerMenu/index.native.tsx
Lines 93 to 99 in 8372553
What changes do you think we should make in order to solve the problem?
We fix two behaviors:
We track the selected category index and expose it to the shortcut buttons so SR announces “selected”.
We make headers focusable and programmatically move SR focus after scroll finishes, with retries for far jumps.
Video demo of the fix:
emoji-category-announces-and-focus-changes-to-header.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.
42 remaining items
rushatgabhane commentedon Apr 1, 2026
The guideline is that if we used your proposal, you're due partial payment (if I'm not wrong)
@truph01 did we use @marufsharifi's proposal to fix the issue
melvin-bot commentedon Apr 6, 2026
@truph01 Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Apr 8, 2026
@truph01 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
mallenexpensify commentedon Apr 10, 2026
@truph01 👀 above plz
melvin-bot commentedon Apr 10, 2026
@truph01 Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
marufsharifi commentedon Apr 11, 2026
@mallenexpensify, could you please review this issue from the start?
I assigned and hired for it, opened the PR, and requested a review before it was reassigned. With that in mind, would I still only be eligible for payment if they used the proposal approach?
Thank you for your time and consideration.
mallenexpensify commentedon Apr 13, 2026
@truph01 👀 above to see if you Maruf might be due payment. Thx
truph01 commentedon Apr 13, 2026
Here’s a clear summary of what happened in this issue:
@rushatgabhane initially assigned the issue to @marufsharifi (see: comment).
Since they were assigned, @marufsharifi began working on it and opened a PR.
Later, @rushatgabhane reassigned the issue to me and closed the existing PR based on this Slack thread:
https://expensify.slack.com/archives/C01GTK53T8Q/p1772739593580499
After that, I asked Melvin to implement this issue independently, without relying on the previous PR from @marufsharifi.
Conclusion
Given that @marufsharifi had already started work and submitted a PR before the reassignment, they were involved in partial implementation. Based on the context and the Slack confirmation, they should receive partial payment for their contribution.
cc @rushatgabhane @mallenexpensify
mallenexpensify commentedon Apr 13, 2026
Thanks @truph01 I agree with you. Updated the payment summary above
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022043794311713278483
marufsharifi commentedon Apr 14, 2026
@mallenexpensify, I've accepted the offer. thanks.
mallenexpensify commentedon Apr 14, 2026
@marufsharifi paid, summary updated above. Thx.
garrettmknight commentedon May 10, 2026
$250 approved for @truph01