# Jitsi chat and poll controls do not respond to the keyboard

> First distinguish an unreachable message action from an input that ignores Escape, arrow keys or Backspace. October 2026 reports describe both problems in the web client, and the reviewed source retains the reported code paths. No released correction was established in this review. Record the exact client and a harmless reproduction; changing server ports will not make a missing keyboard control appear. [S1][S2][S3]

Source: https://jitsi.help/troubleshooting/jitsi-chat-keyboard-navigation/
Updated: October 25, 2026
Publisher: Jitsi Help (https://jitsi.help/)

## Which keyboard problem do you have?

| Symptom | Evidence and next check |
| --- | --- |
| Reaction or message menu appears with a pointer but cannot be reached with Tab | Issue #18101 reports hover-dependent rendering in the web chat message component. Test keyboard focus separately from pointer hover. [S1] |
| Escape does not cancel editing a message | Issue #18099 reports an input keyboard-event mismatch. Record whether editing remains active and preserve the unsent text before trying another control. [S2] |
| Arrow keys or Backspace do not navigate or remove poll answer fields as expected | The same report covers poll inputs. Verify ordinary typing separately from these non-printable keys. [S2] |
| A long message loses text while typing | Use the separate [chat truncation guide](/troubleshooting/jitsi-chat-message-cut-off/); it is a different input path |
| A Settings tab closes its dialog | See the [background preview failure note](/troubleshooting/jitsi-virtual-background-not-working/#settings-closes-when-opening-virtual-background) |

The reports identify Chromium web behavior. They do not establish that every browser, public service, older release or native app has the same failure.

## Make a small, private reproduction

1. Record the server/client version, browser and OS, and whether you use a screen reader. For self-hosted installations, use [version inspection](/guides/check-jitsi-version/).
2. Use a disposable test meeting with harmless text. Confirm that ordinary chat typing works.
3. Without touching the pointer, navigate through the chat using Tab and Shift+Tab. Record which eligible controls receive visible focus and what the screen reader announces.
4. Separately enter edit mode for your own test message. Press Escape once and record whether edit mode remains. Do not submit replacement text merely to escape the editor.
5. In a disposable poll draft, compare ordinary typing with arrow-key navigation and Backspace on an empty answer. Preserve a copy of draft text before closing or leaving.

These are recommended diagnostic steps, not a completed browser or assistive-technology test from this site. A pointer revealing an action is useful evidence of a keyboard-access gap; it is not an equivalent workaround for someone who cannot use a pointer.

## What the source review confirms

At Meet commit `189dc916` reviewed on 25 October, web `ChatMessage.tsx` conditionally renders message menus and reaction controls using `isHovered`. The base web `Input` exposes `onKeyPress` for its input/textarea, while chat editing checks Escape and poll handlers check non-printable navigation keys. Those source paths support investigating the reported failures. They do not establish an independently reproduced result on your deployed build. [S3]

Issue #18099 proposes forwarding `onKeyDown`; issue #18101 proposes making actions reachable on focus. Both were open at review. Do not replace production JavaScript, install an arbitrary branch or promise a version number based on those proposals alone. [S1][S2]

## Keep the meeting usable while investigating

Use an existing labeled cancel/close control only if your actual client exposes it and you can reach it. Preserve a draft before closing a panel or changing clients. If an essential action is unreachable, ask the organizer for an accessible alternative to that activity rather than assuming everyone can use a mouse.

An operator should compare the problem in the deployed client with the exact upstream report and collect a sanitized reproduction. A client source correction, if later merged, still needs release inclusion and a deployment check. There is no documented Docker environment variable in these reports that repairs the missing event or renders the hover-only controls.

## Verify a future correction

Repeat the same keyboard-only path on the candidate build. Check visible focus, announced names and state, Escape behavior, poll navigation and the existing permissions on message actions. Include an eligible and an ineligible action: a correction must not expose edit or delete actions to someone who lacks permission.

Recheck pointer behavior and any supported assistive technology on the intended browser. Keep web, native mobile and custom SDK acceptance results separate. This review did not complete a meeting, browser matrix, screen-reader session or fixed-build test.

## Sources

- **[S1]** [Chat action keyboard-access report #18101](https://github.com/jitsi/jitsi-meet/issues/18101), opened 24 October 2026, open when checked 25 October.
- **[S2]** [Input, Escape and poll-navigation report #18099](https://github.com/jitsi/jitsi-meet/issues/18099), opened 24 October 2026, open when checked 25 October.
- **[S3]** Immutable Meet commit `189dc916`: [chat message rendering](https://github.com/jitsi/jitsi-meet/blob/189dc91660395cc941c3345e42daa91c0aee9de6/react/features/chat/components/web/ChatMessage.tsx), [chat input](https://github.com/jitsi/jitsi-meet/blob/189dc91660395cc941c3345e42daa91c0aee9de6/react/features/chat/components/web/ChatInput.tsx), [base input](https://github.com/jitsi/jitsi-meet/blob/189dc91660395cc941c3345e42daa91c0aee9de6/react/features/base/ui/components/web/Input.tsx) and [poll creation](https://github.com/jitsi/jitsi-meet/blob/189dc91660395cc941c3345e42daa91c0aee9de6/react/features/polls/components/web/PollCreate.tsx).

## Frequently asked questions

### Is the chat keyboard problem fixed in a released version?

No released correction was established for issues #18101 and #18099 when reviewed on 25 October 2026. Both were open. A proposed source change is not proof that the client you use includes it.

### Will changing a keyboard shortcut fix an unreachable message menu?

Not necessarily. The message-action report concerns controls conditionally rendered on mouse hover. That differs from a shortcut conflict or a message input receiving the wrong keyboard event.

### Can I use these web findings to assess the native mobile app?

No. The cited chat and poll reports concern web components. Test TalkBack or VoiceOver separately on the exact native app or SDK build and do not infer a device compatibility result from a web source review.


---

Jitsi Help is an independent service. It is not affiliated with, endorsed by or sponsored by 8x8, Inc. or the Jitsi project. Jitsi and Jitsi Meet are trademarks of 8x8, Inc., used here only to describe the software we host and support.