[HOLD] Screen Reader: Workspace Expensify Card: Step buttons announced without state information

[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

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 Owner

Current Issue Owner: @rushatgabhane

[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!