You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-04-01] Screen Reader: Many Pages: The user is not informed about displayed time and when it disappears #77259
Using iOS VoiceOver or Android TalkBack, open the Expensify app
Swipe to the 'Phone and email' field
Type the valid email address and double-tap to activate
Note that the time counter appeared on the screen
Note what is announced
Other Occurrences:
Onboarding - Verify your email
On Profile - Verify Email
On Security - Merge Accounts
On Security - Merge Accounts - Enter Code
Expected Result:
The displayed time should be announced once it appears, e.g.:
'Time remaining: 19 seconds'
And immediately announce the final status when the timer ends: 'The time has expired'
Actual Result:
The time display changes visually, but VoiceOver remains silent, leaving the user unaware of how much time has passed or when the time limit has passed.
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 displayed time is announced once it appears, e.g.:
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!
Please re-state the problem that we are trying to solve in this issue.
When a verification countdown appears (e.g., Sign In → magic code), screen readers do not announce that the timer has started or when it expires. Users don’t know how much time is left or when the time limit ends.
What is the root cause of that problem?
The countdown UI updates visually, but no screen‑reader announcement is triggered. The timer is rendered as HTML text only, so VoiceOver/TalkBack never receives a status update.
diff --git a/src/languages/en.ts b/src/languages/en.ts
index e9750ea9ad0..a0f3ad4fce7 100644
--- a/src/languages/en.ts+++ b/src/languages/en.ts
@@
validateCodeForm: {
magicCodeNotReceived: "Didn't receive a magic code?",
enterAuthenticatorCode: 'Please enter your authenticator code',
enterRecoveryCode: 'Please enter your recovery code',
requiredWhen2FAEnabled: 'Required when 2FA is enabled',
requestNewCode: ({timeRemaining}: {timeRemaining: string}) => `Request a new code in <a>${timeRemaining}</a>`,
+ timeRemainingAnnouncement: ({seconds}: {seconds: number}) => `Time remaining: ${seconds} ${seconds === 1 ? 'second' : 'seconds'}`,+ timeExpiredAnnouncement: 'The time has expired',
requestNewCodeAfterErrorOccurred: 'Request a new code',
Video demo of the fix:
time-announces.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)
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.43-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Dec 10, 2025
📣 @elisenwazuoke! 📣
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 9, 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.
When a verification countdown appears (e.g., Sign In → magic code), screen readers do not announce that the timer has started or when it expires. Users don’t know how much time is left or when the time limit ends.
What is the root cause of that problem?
The countdown UI updates visually, but no screen‑reader announcement is triggered. The timer is rendered as HTML text only, so VoiceOver/TalkBack never receives a status update.
App/src/components/ValidateCodeCountdown/index.tsx
Lines 30 to 36 in 6c1a24c
What changes do you think we should make in order to solve the problem?
Trigger SR announcements at two key moments:
Video demo of the fix:
time-announces.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. Walking. Toward. The. Light...
37 remaining items
melvin-bot commentedon Mar 25, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.43-3 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-04-01. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 1, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Apr 2, 2026
Payment Summary
Contributor+: @situchan due $250 via NewDot
laurenreidexpensify commentedon Apr 16, 2026
Payment Approved - $250 in New Expensify @situchan