Repository navigation
Description
Action Performed:
Prerequisites:
- the user is not signed in
- Using Android TalkBack or iOS VoiceOver, open the Expensify app
- Swipe to the 'Continue' button and double-tap to activate without entering the phone or email
- Note if the displayed error message is announced.
Other Occurrences:
- On Sign In - Enter Code
- Onboarding: all fields in the flow
- On Inbox: the field 'Enter your boss's email'
- On Profile - Display Name
- On Profile - Date of Birth
- On Profile - Address
- On Profile - Legal Name
- On Profile - Verify Email
- On Security - Merge Accounts
- On Security - Merge Accounts - Enter Code
- On Security - Close Account
- On Wallet - Add Bank Account
- On Create Expense - Confirm Details
- On Save the World - I know a teacher
- On Create Workspace
Expected Result:
The displayed error message should be announced once it appears.
Actual Result:
When a user triggers an error, the error message appears visually, but is not announced.
Area issue was found in:
Sign in
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:
Ensure the error message is being announced once it appears.
https://appt.org/en/docs/react-native/samples/accessibility-live-region
Environment:
Samsung Galaxy S24 Ultra - Android 14, Partner - Native (No mobile browser)
Screenshots/Videos
Bug7004827_1763200408008.The_displayed_error_message_is_not_announced.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/7004827
Issue reported by: NA
Slack conversation: NA

Activity
melvin-bot commentedon Dec 12, 2025
📣 @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 📖
melvin-bot commentedon Jan 10, 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 validation errors appear (e.g., Sign In → Continue with empty input), the error text is visible but not announced by screen readers, so users miss critical feedback.
What is the root cause of that problem?
The shared error renderers output error text as plain
<Text>without any live‑region/alert semantics, so when the error appears dynamically, screen readers treat it as a silent visual update.DotIndicatorMessage(dot‑style errors):App/src/components/DotIndicatorMessage.tsx
Lines 109 to 115 in 9618ba6
FormHelpMessage(most inline form errors)App/src/components/FormHelpMessage.tsx
Lines 75 to 77 in 9618ba6
Why this caused the issue: the error text is displayed visually, but no
accessibilityRole="alert"or live‑region is set, so VoiceOver/TalkBack does not announce it.What changes do you think we should make in order to solve the problem?
Add
accessibilityRole="alert"andaccessibilityLiveRegion="assertive"to shared error text output so screen readers announce newly displayed errors across the app.App/src/components/DotIndicatorMessage.tsx
Lines 109 to 115 in 9618ba6
App/src/components/FormHelpMessage.tsx
Lines 75 to 77 in 9618ba6
Video demo of the fix:
announces-errors.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)
12 remaining items
MelvinBot commentedon Feb 19, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When a user triggers a validation error on any form in the app (Sign In, Onboarding, Profile fields, Wallet, etc.), the error message appears visually (red text with dot indicator) but is not announced by screen readers (Android TalkBack, iOS VoiceOver). This violates WCAG 4.1.3 (Status Messages) because users relying on assistive technology have no way to know an error occurred without manually navigating to find it.
What is the root cause of that problem?
The shared error rendering component
FormHelpMessage(src/components/FormHelpMessage.tsx:59-79) renders error text in a plain<View>with<Text>that has no accessibility role or live-region semantics:There is no
role="alert", noaccessibilityRole, and noaccessibilityLiveRegionon any element. The error distinction is purely visual (red color + dot icon viaisErrorprop). Screen readers have no semantic signal that important, time-sensitive information has appeared.This single component is imported by 53+ files across the codebase, including
TextInput(field-level errors),FormAlertWrapper/FormAlertWithSubmitButton(form-level server errors),CheckboxWithLabel,RadioButtons,MagicCodeInput,MenuItem, and many page-level components. This means every form error across all 15+ pages listed in the issue flows through this one component.Additionally, the codebase has zero usage of
accessibilityLiveRegion,aria-live, orAccessibilityInfo.announceForAccessibilityanywhere insrc/, making this a systemic accessibility gap.What changes do you think we should make in order to solve the problem?
Update
FormHelpMessageto addrole="alert"(viaCONST.ROLE.ALERT) to the outer<View>whenisErroris true. Per the discussion between the contributor (@marufsharifi) and C+ reviewer (@suneox), userole="alert"on web with a platform-specific native fallback usingaccessibilityRole="alert"+accessibilityLiveRegion="assertive"for reliable TalkBack announcement on Android, sincerole="alert"alone was not consistently announced on some Android devices.The change is limited to
FormHelpMessageonly --DotIndicatorMessagechanges are not required per the C+ reviewer, as the primary error paths across the 15+ affected pages flow throughFormHelpMessage.CONST.ROLE.ALERTalready exists atsrc/CONST/index.ts:5661and is described as "Use for elements with important, time-sensitive information."What alternative solutions did you explore? (Optional)
accessibilityLiveRegion="assertive"alone: Works on Android TalkBack but is redundant withrole="alert"on web (which implicitly carriesaria-live="assertive"semantics), risking duplicate announcements in some screen readers (NVDA, JAWS).AccessibilityInfo.announceForAccessibility(): Programmatic approach, but requires imperative calls from every error site rather than a single declarative fix at the component level.<Text>nodes: Would cause multiple alerts if there are multiple error messages. Placing the role on the container<View>is the correct approach.Note: This analysis confirms the proposal by @marufsharifi (reviewed and approved by C+ @suneox). The contributor indicated a PR is in progress.
Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.[-]Screen Reader: Many Pages: The displayed error message is not announced[/-][+][Due for payment 2026-03-04] Screen Reader: Many Pages: The displayed error message is not announced[/+]melvin-bot commentedon Feb 25, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 25, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.25-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-04. 🎊
For reference, here are some details about the assignees on this issue:
rushatgabhane commentedon Feb 26, 2026
fixed