Skip to content

[Due for payment 2026-04-14] [$1000] [A11y] Screen Reader: Workspace Category: The accordion button is announced without a state #76929

Closed

Description

@nbhardwaj-del

Action Performed:

Prerequisite:

  • User is logged in
  1. Using Chrome+JAWS, open the URL: https://new.expensify.com/
  2. Tab to focus on the required workspace and press Enter to activate it
  3. Once the Workspace menu is displayed, tab to focus on the "Categories" menu item and press Enter to activate it
  4. Tab to focus the More button and observe the screen reader announcement.

Expected Result:

The accordion button should communicate its expanded or collapsed state to assistive technologies. When expanded, the button should indicate “expanded”, and when collapsed, it should indicate “collapsed”.

Actual Result:

The expanded collapsed state of the accordion button "more" is not announced by the screen reader upon activation. When focused the screen reader only announces the role and label of the control without indicating whether it is expanded or collapsed. As a result, users relying on assistive technologies cannot determine the current state of the accordion content.

HTML:

More
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" viewBox="0 0 20 20" width="16" height="16" hovered="false" pressed="false" fill="#A2A9A3">

Area issue was found in:

Workspace Category

Failed WCAG checkpoints

WCAG 4.1.2 Name, Role, Value
https://www.w3.org/WAI/WCAG22/Understanding/name-role-value

User impact:

Providing role, state, and value information on all user interface components enables compatibility with assistive technology, such as screen readers, screen magnifiers, and speech recognition software, used by people with disabilities.

Suggested resolution:

Add the "aria-expanded" attribute to the accordion button to indicate its current state.

Refer:
https://www.w3.org/WAI/ARIA/apg/patterns/accordion/

Environment(s)

Windows Windows 11 - Chrome

Screenshots/Videos

Bug6996806_1762786478474.Screen_Reader-_Workspace_Category-The_accordion_button_is_announced_without_a_state.mp4
Image

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022013102921460848748
  • Upwork Job ID: 2013102921460848748
  • Last Price Increase: 2026-04-14
Issue OwnerCurrent Issue Owner: @mallenexpensify

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
    c2e9e3a
  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jan 19, 2026
  4. changed the title [-]Screen Reader: Workspace Category: The accordion button is announced without a state[/-] [+][$250] Screen Reader: Workspace Category: The accordion button is announced without a state[/+] on Jan 19, 2026
  5. melvin-bot commented on Jan 19, 2026

    @melvin-bot
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 19, 2026
  7. melvin-bot commented on Jan 19, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 (External)

  8. 95 remaining items

  9. mallenexpensify commented on Apr 13, 2026

    @mallenexpensify
    Contributor

    @QichenZhu @dangrous can either of you plz confirm @daledah 's comment above so I can pay 'em?

    assigned to this issue, and Melvin’s PR also used the solution we had previously discussed.

    If so, it looks like it'd be 100%, correct?

  10. QichenZhu commented on Apr 13, 2026

    @QichenZhu
    Contributor

    @QichenZhu @dangrous can either of you plz confirm @daledah 's comment above so I can pay 'em?

    @mallenexpensify I can confirm @daledah opened a PR and requested review, and Melvin's solution built on @daledah's proposal.

  11. QichenZhu commented on Apr 14, 2026

    @QichenZhu
    Contributor

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

      Link to the comment on the PR: N/A.
      Link to the comment on the Issue: N/A.

      Reported an issue and opened a PR upstream.

    • [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: 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.

    • [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/625160

    Regression Test Proposal

    Precondition:

    • Enable the screen reader

    Test:

    1. Navigate to a workspace's Categories page
    2. Focus the More button
    3. Verify the screen reader announces the button as collapsed

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-1443-a2fc-3336-b1a59b2da094
  12. QichenZhu commented on Apr 14, 2026

    @QichenZhu
    Contributor

    @mallenexpensify @roryabraham, could you adjust the compensation based on #86499 (comment)?

  13. changed the title [-][Due for payment 2026-04-14] [$250] Screen Reader: Workspace Category: The accordion button is announced without a state[/-] [+][Due for payment 2026-04-14] [$1000] Screen Reader: Workspace Category: The accordion button is announced without a state[/+] on Apr 14, 2026
  14. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Upwork job price has been updated to $1000

  15. melvin-bot commented on Apr 14, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2013102921460848748/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. mallenexpensify commented on Apr 16, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @QichenZhu due $1000 via NewDot
    Contributor+: @daledah due $1000 via NewDot

    ^ Test case created

    Thx

  17. trjExpensify commented on Apr 21, 2026

    @trjExpensify
    Contributor

    approved $1,000 for @QichenZhu

  18. quinthar commented on Apr 28, 2026

    @quinthar
    Contributor

    Approved $1000 for @daledah

  19. changed the title [-][Due for payment 2026-04-14] [$1000] Screen Reader: Workspace Category: The accordion button is announced without a state[/-] [+][Due for payment 2026-04-14] [$1000] [A11y] Screen Reader: Workspace Category: The accordion button is announced without a state[/+] on May 4, 2026
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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded 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