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-07-29] [$250] [HOLD] Screen Reader: Workspace Expensify Card: Step buttons announced without state information #76904
Prerequisite:
User has an account and is logged in.
Using Windows Chrome + JAWS, open the page: [https://new.expensify.com/](https://new.expensify.com//)
Tab to focus the Workspaces tab and press enter to activate.
Select any workspace and press enter to activate.
Tab to the 'Expensify Card' button and press enter to activate.
Tab to the 'Issue New Card' button and press enter to activate.
Navigate to the 'Connect Manually' or the 'Log into your bank' button and press enter to activate.
Tab to the numerical step buttons and note what is announced.
Expected Result:
The current step should be programmatically identifiable so assistive technology users can understand their position in the sequence.
Actual Result:
All step buttons are announced identically, such as “1,” “2,” “3,” etc. The active step (visually shown with a green outline) is not programmatically marked as selected or current. Users of assistive technologies cannot tell which step they are on.
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 an appropriate state attribute such as aria-current="step" or similar ARIA markup to identify the active step button for screen readers.
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!
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: accessibility issue
[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.
Link to discussion:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Open Workspace → Expensify Card → Issue new card → Connect manually and land on “Confirm currency and country” (step 1 of 6).
Confirm the step indicator still looks correct (6 steps, step 1 highlighted).
Windows (JAWS) + Tab: Step 1 announces Step 1 of 6, Confirm currency and country, current step; steps 2–6 announce Step X of 6 only (not 1/2/3, not colon, not press enter).
Mac (VoiceOver) + Tab: Same labels; no regression from before.
Advance to step 2 — expected: indicator updates; screen reader announces the new current step.
Regression test: Open a flow with clickable steps (e.g. Missing Personal Details). Completed steps navigate on click; locked steps do not.
iOS/Android (native): Open the same bank account wizard flow — expected: step indicator looks and behaves the same as before (no visual or interaction regressions).
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!
Fix Expensify#76904: Add step number and aria-current to step buttons
86 remaining items
rushatgabhane commentedon Jul 24, 2026
applause verified it as fixed 🎉
nice work @Krishna2323
melvin-bot commentedon Jul 27, 2026
@Krishna2323 Huh... This is 4 days overdue. Who can take care of this?
mkhutornyi commentedon Jul 28, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: accessibility issue
[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.
Link to discussion:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/666551
Regression Test Proposal
Test:
Step 1 of 6, Confirm currency and country, current step; steps 2–6 announceStep X of 6only (not1/2/3, notcolon, notpress enter).Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-0e16-af05-25de-cd8ad350e254melvin-bot commentedon Jul 28, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Jul 30, 2026
Payment Summary
Contributor: @Krishna2323 due $250 via NewDot
Contributor+: @mkhutornyi due $250 via NewDot
^ Test case created. Thx
trjExpensify commentedon Aug 3, 2026
approved $250 for @mkhutornyi
laurenreidexpensify commentedon Aug 26, 2026
$250 approved for @Krishna2323 New Expensify