Skip to content

Screen Reader: Profile Subsections: No feedback announced after requesting a new OTP code #77573

Closed

Description

@olenamihno

Action Performed:

Precondition: User is logged in

  1. Using VoiceOver on iOS or TalkBack on Android, open the app
  2. Swipe right to focus the Account tab and double-tap to activate it
  3. Swipe right to focus the Profile button and double-tap to activate it
  4. Swipe right to focus the Contact methods menu item and double-tap to activate it
  5. Swipe right to focus an email address that requires verification and double-tap to activate it
  6. Swipe right to focus the "Didn't receive a code?" button and double-tap to activate it
  7. Note if the new OTP code request is announced

Expected Result:

After requesting a new OTP code screen readers should announce a confirmation message, e.g., "A new code has been sent to your email".

Users should know that the action succeeded and can proceed to enter the new OTP.

Actual Result:

No feedback is announced after requesting a new OTP code.

Users relying on screen readers cannot confirm that the code was sent.

Area issue was found in:

Profile

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 on Android / AccessibilityInfo.announceForAccessibility on iOS to ensure screen reader users receive feedback announcement after requesting a new OTP code, e.g., "A new code has been sent to your email".
https://appt.org/en/docs/react-native/samples/accessibility-live-region
https://reactnative.dev/docs/accessibilityinfo#announceforaccessibility

Environment:

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

Image
Bug7008105_1763623726778.No_feedback_announced_after_requesting_a_new_OTP_code.mp4

Version Number: Production
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): No
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/7008105
Issue reported by: NA
Slack conversation: NA

Activity

  1. melvin-bot commented on Dec 12, 2025

    @melvin-bot

    📣 @olenamihno! 📣
    Please report bugs or suggest features in the #expensify-open-source Slack channel, don't directly open issues in this repo!
    Instructions here to join the channel 📖

  2. melvin-bot commented on Jan 10, 2026

    @melvin-bot

    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!

  3. self-assigned this
    on Feb 23, 2026
  4. rushatgabhane commented on Feb 24, 2026

    @rushatgabhane
    Member

    fixed by #79248

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

Metadata

Metadata

Assignees

Labels

AccessibilityIssues affecting WACG accessibility on any platform.MonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions