Skip to content

[Due for payment 2026-05-22] [$250][Accessibility][Tracking] Hide from Assistive Tech / Remove Interactive Role #79243

Closed

Description

@rushatgabhane

Overview

This issue tracks elements that should be hidden from assistive technology or have incorrect interactive roles removed.

Context

Part of the accessibility improvement effort tracked in https://github.com/Expensify/Expensify/issues/575078

Issues to Fix

Instructions

Suggested Fix: Hide redundant elements or remove incorrect roles

Note: Discuss on Slack if you are unsure whether a sub-issue should be fixed or if you are unsure about the right fix / expected result. Ideally, create a single PR that will fix all the issues listed to minimize review time (more PRs only if necessary).

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022009703243399104750
  • Upwork Job ID: 2009703243399104750
  • Last Price Increase: 2026-01-09
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jan 9, 2026
  2. changed the title [-][Accessibility] Hide from Assistive Tech / Remove Interactive Role[/-] [+][$250] [Accessibility] Hide from Assistive Tech / Remove Interactive Role[/+] on Jan 9, 2026
  3. melvin-bot commented on Jan 9, 2026

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

    @melvin-bot

    Current assignee @mallenexpensify is eligible for the Bug assigner, not assigning anyone new.

  6. melvin-bot commented on Jan 9, 2026

    @melvin-bot

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

  7. changed the title [-][$250] [Accessibility] Hide from Assistive Tech / Remove Interactive Role[/-] [+][Accessibility][Tracking] Hide from Assistive Tech / Remove Interactive Role[/+] on Jan 9, 2026
  8. changed the title [-][Accessibility][Tracking] Hide from Assistive Tech / Remove Interactive Role[/-] [+][$250][Accessibility][Tracking] Hide from Assistive Tech / Remove Interactive Role[/+] on Jan 9, 2026
  9. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    ⚠️ This issue has had its price increased by 4x or more. Please review the issue and ensure the price is correct.

  10. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    Upwork job price has been updated to $250

  11. yatin-italy commented on Jan 9, 2026

    @yatin-italy

    Thanks a lot! I’m happy to take on these issues. 😊

  12. 134 remaining items

  13. Uzaifm127 commented on May 22, 2026

    @Uzaifm127
    Contributor

    @mallenexpensify Let me try to clarify the full journey of this issue because there were multiple PRs and regressions involved:

    In the first PR, I worked on it and @dominictb reviewed it. That PR solved one of the two issues mentioned by the OP. It also fixed a regression that had been introduced by another PR (not by our PR). We also covered the second issue in that PR but we left the Android mweb case and then another PR already fixed that before ours get merged.

    Then for the second issue, I was working but I had to OOO so @truph01 took over.

    Then they raised a PR with Melvin and it merged then it got reverted here based on the reasoning they provided here.

    After the revert, @truph01 raised an another final PR which then solved the Android mweb issue we left.

    Note: The first PR by @truph01 (before regression) was reviewed by @dominictb and second PR by @truph01 (after regression) was reviewed by @mkhutornyi


    I hope I explained well.

  14. melvin-bot commented on May 22, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @mkhutornyi owed $250 via NewDot
    • ROLE: @Uzaifm127 paid $(AMOUNT) via Upwork (LINK)
    • Contributor: @dominictb does not require payment (Contractor)
    • Reviewer: @truph01 owed $250 via NewDot

    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/2009703243399104750/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
  15. Uzaifm127 commented on May 23, 2026

    @Uzaifm127
    Contributor

    ROLE: @Uzaifm127 paid $(AMOUNT) via Upwork (LINK)

    @mallenexpensify Melvin is saying paid but I'm also due payment here.

  16. melvin-bot commented on May 25, 2026

    @melvin-bot

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  17. mallenexpensify commented on May 25, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @Uzaifm127 paid $250 via Upwork
    Contributor+: @truph01 due $125 via NewDot
    Contributor+: @mkhutornyi due $250 via NewDot
    Contributor+: @dominictb due $250 via NewDot

    @Uzaifm127 can you please accept the job below? Please reply here and tag me once you have.
    If you're not sent an offer in Upwork when you're assigned to an issue, and an Upwork job exists, please submit a proposal.
    https://www.upwork.com/jobs/~022059029571903417582

    I hope I explained well.

    @Uzaifm127, yes, the breakdown was very helpful (even if I might not have gotten the first attempt at the payment summary correct)

    All, comment if anything isn't correct. Provide reasoning and links, when needed and tag me too, thx

  18. Uzaifm127 commented on May 26, 2026

    @Uzaifm127
    Contributor

    @mallenexpensify Accepted the offer, requested the payment. Thanks.

    please submit a proposal

    Also, luckily I applied on the job and submitted the proposal when I got the offer.

  19. dominictb commented on May 26, 2026

    @dominictb
    Contributor

    @mallenexpensify Hi this is my C+ work and outside of backend hourly work so I'm also due payment here.

  20. Uzaifm127 commented on May 26, 2026

    @Uzaifm127
    Contributor

    Yes, @dominictb is correct. They started with this issue before they were the backend contributor and then in between they became the backend contributor but still they continued to review the PR.

  21. mallenexpensify commented on May 26, 2026

    @mallenexpensify
    Contributor

    @Uzaifm127 paid, summary updated above. Thx.
    Added @dominictb too for the review of the first PR, think/hope we're good to close

  22. trjExpensify commented on May 27, 2026

    @trjExpensify
    Contributor

    approved $250 for @dominictb

  23. trjExpensify commented on Jun 2, 2026

    @trjExpensify
    Contributor

    approved $250 for @mkhutornyi

  24. garrettmknight commented on Jul 10, 2026

    @garrettmknight
    Contributor

    $125 approved for @truph01

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

Metadata

Metadata

Labels

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