Skip to content

[Due for payment 2026-07-29] [$250] [HOLD] Screen Reader: Workspace Expensify Card: Step buttons announced without state information #76904

Closed

Description

@nbhardwaj-del

Action Performed:

Prerequisite:
User has an account and is logged in.

  1. Using Windows Chrome + JAWS, open the page: [https://new.expensify.com/](https://new.expensify.com//)

  2. Tab to focus the Workspaces tab and press enter to activate.

  3. Select any workspace and press enter to activate.

  4. Tab to the 'Expensify Card' button and press enter to activate.

  5. Tab to the 'Issue New Card' button and press enter to activate.

  6. Navigate to the 'Connect Manually' or the 'Log into your bank' button and press enter to activate.

  7. 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.

HTML:
Step 1 -

1

Area issue was found in:

Workspace Expensify Card

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 an appropriate state attribute such as aria-current="step" or similar ARIA markup to identify the active step button for screen readers.

Refer:
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-current

Environment(s)

Windows 10 - Chrome

Bug6995623_1762398176526.button-state-not-announced.mp4

Image

Screenshots/Videos

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/6995623
Issue reported by: NA
Slack conversation: NA

Issue OwnerCurrent Issue Owner: @Krishna2323
Upwork Automation - Do Not Edit

Activity

  1. melvin-bot commented on Jan 1, 2026

    @melvin-bot

    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!

  2. added a commit that references this issue on Jan 8, 2026
    3618fd0
  3. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 23, 2026
  4. 86 remaining items

  5. rushatgabhane commented on Jul 24, 2026

    @rushatgabhane
    Member

    applause verified it as fixed 🎉

    nice work @Krishna2323

  6. melvin-bot commented on Jul 27, 2026

    @melvin-bot

    @Krishna2323 Huh... This is 4 days overdue. Who can take care of this?

  7. mkhutornyi commented on Jul 28, 2026

    @mkhutornyi
    Contributor

    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:

    1. Open Workspace → Expensify Card → Issue new card → Connect manually and land on “Confirm currency and country” (step 1 of 6).
    2. Confirm the step indicator still looks correct (6 steps, step 1 highlighted).
    3. 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).
    4. Mac (VoiceOver) + Tab: Same labels; no regression from before.
    5. Click step circles — expected: nothing happens (display-only wizard).
    6. Advance to step 2 — expected: indicator updates; screen reader announces the new current step.
    7. Regression test: Open a flow with clickable steps (e.g. Missing Personal Details). Completed steps navigate on click; locked steps do not.
    1. 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).

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-0e16-af05-25de-cd8ad350e254
  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 28, 2026
  9. melvin-bot commented on Jul 28, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  10. mallenexpensify commented on Jul 30, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @Krishna2323 due $250 via NewDot
    Contributor+: @mkhutornyi due $250 via NewDot

    ^ Test case created. Thx

  11. trjExpensify commented on Aug 3, 2026

    @trjExpensify
    Contributor

    approved $250 for @mkhutornyi

  12. laurenreidexpensify commented on Aug 26, 2026

    @laurenreidexpensify
    Contributor

    $250 approved for @Krishna2323 New Expensify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

AccessibilityIssues affecting WACG accessibility on any platform.Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions