Repository navigation
Description
Action Performed:
Prerequisites:
- the user is not signed in
- Open the Expensify app
- Start the onboarding flow
- Note how the status of the progress bar is displayed.
Expected Result:
The progress bar should not rely only on the use of color, e.g.:
- by using a text 'step 3 of 5'.
Actual Result:
When the progress bar changes status, the only indication is a color change (e.g., from grey to green). Users with color vision deficiencies cannot perceive the status update, making the information unreliable.
Area issue was found in:
Onboarding
Failed WCAG checkpoints
WCAG 1.4.1 Use of Color
https://www.w3.org/WAI/WCAG22/Understanding/use-of-color
User impact:
Users with partial sight often experience limited color vision. Some older users may not be able to see color well. Users who have color-blindness benefit when information conveyed by color is available in other visual ways. People using limited color monochrome displays may be unable to access color-dependent information. Users who have problems distinguishing between colors can look or listen for text cues.
Suggested resolution:
Provide a non-color visual indicator and programmatic status text to ensure the information is accessible to all users, e.g.:
- by using a text 'step 3 of 5'
https://www.w3.org/TR/WCAG22/#use-of-color
Environment(s)
Samsung Galaxy S24 Ultra - Android 14, Partner - Native (No mobile browser)
Apple iPhone 11 - iOS 17.5.1, H0T Mobile - Native (No mobile browser)
Screenshots/Videos
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/7005654
Issue reported by: NA
Slack conversation: NA
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022009685364726607157
- Upwork Job ID: 2009685364726607157
- Last Price Increase: 2026-01-09

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!
[-]Color: Onboarding: The status of the progress bar relies only on the use of color[/-][+][$250] Color: Onboarding: The status of the progress bar relies only on the use of color[/+]melvin-bot commentedon Jan 9, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022009685364726607157
melvin-bot commentedon Jan 9, 2026
Current assignee @mallenexpensify is eligible for the Bug assigner, not assigning anyone new.
108 remaining items
[-][$250] [A11y] Color: Onboarding: The status of the progress bar relies only on the use of color[/-][+][Due for payment 2026-08-25] [$250] [A11y] Color: Onboarding: The status of the progress bar relies only on the use of color[/+]melvin-bot commentedon Aug 18, 2026
@suneox
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.54-4 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-08-25. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
suneox commentedon Aug 18, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
N/A: accessibility enhancement, no offending PR exists. The bar was color-only since its introduction; nothing regressed.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
N/A: It isn't an impactful bug
melvin-bot commentedon Aug 21, 2026
@suneox Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Aug 24, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Aug 26, 2026
Payment Summary
Contributor+: @suneox due $250 via NewDot
garrettmknight commentedon Aug 27, 2026
$250 approved for @suneox