Skip to content

Web-Accessibility- RHP doesn't resize whith screen reader keyboard navigation #106861

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.39-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #106120
Email or phone of affected tester (no customers): gd868gd+34n@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Desktop / Windows 11
App Component: Other

Action Performed:

  1. Open the Expensify Web App and log in
  2. Enable "resizableRHP" beta override
  3. Go to any chat and click on its header to open the Details
  4. Enable the Screen reader
  5. Press Tab until you reach the left edge of the RHP
  6. Press the left arrow three times

Expected Result:

The RHP should resize by 8 pixels.

Actual Result:

Nothing happens.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7313016_1794559680290.Expensify_PR106120_Keyboard_Resize_Web.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7313016

Issue OwnerCurrent Issue Owner: @Krishna2323

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 13, 2026
  2. melvin-bot commented on Nov 13, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #106120

  3. applause-bot commented on Nov 13, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/8816ec5cb2e2fe72ec6140369e3477c4249044817b77e27c4f8c28a103a98524

  4. melvin-bot commented on Nov 13, 2026

    @melvin-bot

    @lakchote @Krishna2323 you have been assigned to this deploy blocker because you reviewed the offending PR: #106120

  5. melvin-bot commented on Nov 13, 2026

    @melvin-bot

    @war-in you have been assigned to this deploy blocker because you authored the offending PR: #106120

  6. melvin-bot commented on Nov 13, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  7. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  8. MelvinBot commented on Nov 13, 2026

    @MelvinBot
    Contributor

    🤖 Web test steps verification results: ⚠️ partial

    The web session reported signed in, but displayed a blank page; no resizing or screen-reader reproduction was established. Keep DeployBlockerCash: the responsible implementation is identified, but the failure mechanism remains unconfirmed.

    Blank web app despite authenticated session state

    Step Status
    1. Open web app and log inSession state reported authenticated and onboarding complete, but the app rendered blank.
    Blank web app despite authenticated session state
    ✅
    2. Enable resizableRHP beta overrideBlocked by the blank app; no accessible controls were available.
    ❌
    3. Open a chat’s DetailsBlocked: no chat header was accessible.
    ❌
    4. Enable a screen readerReal Windows/Chrome screen-reader testing was unavailable in the Linux headless browser.
    ❌
    5. Tab to the RHP’s left resize edgeNot tested; actual separator focus could not be established.
    ❌
    6. Press Left three times and verify resizingNo runtime width measurements were obtained.

    Investigation: Keyboard support and ARIA for the resize handle introduced this behavior and was deployed before the reported staging build. It is the primary candidate—not a confirmed root cause.

    The resize handler requires keyboard events reaching the focused separator. The key interpreter rejects modified arrows. Three unmodified Left presses should widen the panel by 24px total, unless clamped at maximum width.

    An earlier accessibility-tree defect was already addressed: the merged dialog structure encloses both the panel and resize handle. That earlier defect should not be cited as the shipped cause.

    Next action: QA should identify the screen reader/version and interaction mode, start below maximum width, confirm actual separator focus, and compare reader-off/on behavior while checking whether ArrowLeft reaches the handler and aria-valuenow changes. This distinguishes intercepted arrows, focus divergence, and width clamping.

    Deploy recommendation: Retain the blocker pending that retest. Reverting the candidate PR removes keyboard resizing rather than restoring previously working behavior; a revert is not yet demonstrated to resolve this report.
    ❌

    view run · no recording available

  9. 3 remaining items

  10. JS00001 commented on Nov 13, 2026

    @JS00001
    Contributor

    Lets not block on this

  11. cocvn157 commented on Nov 14, 2026

    @cocvn157
  12. war-in commented on Nov 17, 2026

    @war-in
    Contributor

    @jponikarchuk looks like you're using some screen keyboard to navigate the layout. I tried to reproduce it with the regular keyboard on mac and it worked just fine. Please let me know if this is some custom app, or maybe screen reader opens the keyboard when turned on on windows? I'm afraid I can't reproduce this :/
    @Krishna2323 do you have any idea what could have caused this?

  13. jponikarchuk commented on Nov 18, 2026

    @jponikarchuk

    @war-in I used the built-in screen keyboard that I enabled in the Windows Accessibility settings separately from the Screen Reader. I used it to display my keyboard actions.
    The Screen Reader is also the built-in one.
    The issue is also reproducible on Windows Chrome with the physical laptop keyboard.

    Expensify_7313016_Repro.mp4
  14. war-in commented on Nov 18, 2026

    @war-in
    Contributor

    The issue is also reproducible on Windows Chrome with the physical laptop keyboard.

    @jponikarchuk is it also reproducible when the screen reader is off? Did this happen to you in other places that can be resized (table columns with the resizableTableColumns beta on)?

  15. jponikarchuk commented on Nov 18, 2026

    @jponikarchuk

    @war-in The issue is reproducible with the resizable columns when the Screen Reader is on, and not reproducible when it’s off (in both columns and RHP).

    Sreen_Reader_Columns.mp4
  16. expensify-chore-bot commented on Nov 19, 2026

    @expensify-chore-bot

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

  17. jakubkalinski0 commented on Nov 20, 2026

    @jakubkalinski0
    Member

    Hi everyone, I'm Jakub from SWM and I'll be looking after this issue next week while @war-in is OOO

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringOverdue

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions