Repository navigation
Description
Action Performed:
- Using JAWS + Chrome, open the page https://new.expensify.com/
- Navigate using TAB to the phone or email input field.
- Trigger an error message, then press Tab/Shift+Tab key to focus the field with an error.
- Note how the field is announced.
Other Occurrences:
- On Settings - Save the world - I know a teacher
- On Settings - Save the world - Intro your school principal
- On Settings - Security - Close account
- On Settings - Security - Two-factor authentication (step 2 of 2)
- On Settings - Profile - Display name
- On Settings - Profile - DOB
- On Settings - Profile - Phone number
- On Settings - Profile - Legal name
- On Settings - Profile - Address
- On Workspaces - Duplicate Workspaces
- On Workspaces - Overview - Workspace Name
- On Workspace - Categories - Add Category
- On Workspace - Expensify Card - Bank info
- On Workspace - Create Workspace - Confirm Workspace
- On Create Report - Add payment card
Expected Result:
The error message should be associated with the form control, so that it is announced upon focusing the control.
Actual Result:
The error message is not associated with the form control and is not announced upon focusing the control.
HTML:
Area issue was found in:
Landing Page
Failed WCAG checkpoints
WCAG 1.3.1 Info and Relationships
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
User impact:
Users with different disabilities employ assistive technology to adapt content according to their specific needs. For example, users who are blind (using a screen reader) benefit when information conveyed through color is also available in text (including text alternatives for images that use color to convey information), and users who are deaf-blind and use braille (text) refreshable displays may be unable to access color-dependent information.
Suggested resolution:
Use the aria-describedby to associate the error message with the form control.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-describedby
Environment(s)
Windows Windows 10 - Chrome
Screenshots/Videos
Bug6997302_1762539559698.Error_message_not_announced.mp4
Version Number: NA
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/36605/community-issues/6997302
Issue reported by: NA
Slack conversation: NA
Activity
melvin-bot commentedon Jan 1, 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 a form field has a validation error (e.g., Sign In email/phone), the error text is visible but not associated with the input on web, so JAWS doesn’t announce the error when the user focuses the field.
What is the root cause of that problem?
The error text is rendered in
FormHelpMessagewithout a stable DOM id, and the input does not setaria-describedby(oraria-errormessage) to point to that error element. As a result, the screen reader has nothing to announce when the input receives focus.App/src/components/TextInput/BaseTextInput/implementation/index.tsx
Lines 395 to 452 in 9618ba6
App/src/components/TextInput/BaseTextInput/implementation/index.tsx
Lines 395 to 452 in 9618ba6
App/src/components/FormHelpMessage.tsx
Lines 75 to 77 in 9618ba6
What changes do you think we should make in order to solve the problem?
Add a stable ID for the error message and connect it to the input using
aria-describedby/aria-errormessageon web. Also setaria-invalidwhen an error exists so SRs announce the field is invalid.App/src/components/FormHelpMessage.tsx
Lines 75 to 77 in 9618ba6
type FormHelpMessageProps = { isError: boolean; message: string | null; + messageID?: string; }; -<View style={[styles.flexRow, styles.mt1]}> - <View style={styles.flex1}> +<View style={[styles.flexRow, styles.mt1]}> + <View style={styles.flex1} nativeID={messageID}> <Text style={[isError ? styles.formError : styles.formHelp, styles.mb0]}> {message} </Text> </View> </View>App/src/components/TextInput/BaseTextInput/implementation/index.tsx
Lines 395 to 452 in 9618ba6
App/src/components/TextInput/BaseTextInput/implementation/index.tsx
Lines 395 to 452 in 9618ba6
Video demo of the fix:
login-input-error-announcment.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.
27 remaining items
mallenexpensify commentedon Mar 24, 2026
Payment Summary
Contributor: @marufsharifi paid $250 via Upwork
Contributor+: @suneox due $250 via NewDot
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022036242381341911516
If there's anything lingering on this issue, ie. the need for a followup PR, please comment.
suneox commentedon Mar 24, 2026
@rushatgabhane Do you agree that we should handle the payment for this issue separately, as it uses a different solution as this confirmation?
melvin-bot commentedon Mar 27, 2026
@yuwenmemon, @suneox, @mallenexpensify, @marufsharifi Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Mar 27, 2026
@yuwenmemon, @suneox, @mallenexpensify, @marufsharifi Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Mar 31, 2026
@yuwenmemon, @suneox, @mallenexpensify, @marufsharifi Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Mar 31, 2026
@yuwenmemon, @suneox, @mallenexpensify, @marufsharifi Still overdue 6 days?! Let's take care of this!
mallenexpensify commentedon Apr 2, 2026
@marufsharifi paid, summary updated above. Thx.
@rushatgabhane 👀 plz, I'm unsure what's best.
rushatgabhane commentedon Apr 2, 2026
Yes I think that is fair 👍
#76939 (comment)
rushatgabhane commentedon Apr 2, 2026
closing since we already paid
trjExpensify commentedon Apr 10, 2026
approved $250 for @suneox