# **Summary** Keyboard shortcuts for microphone, video and fullscreen will follow a consistent three modifier pattern (Ctrl+Shift on Windows/Linux, Ctrl+Cmd on macOS) instead of unreliable single key presses, preventing accidental triggers while typing and eliminating conflicts with browser shortcuts such as Ctrl+F for search. Push to talk for microphone (Spacebar, only while muted) and whisper (W) will remain single key holds, since sustained key pressure makes accidental activation unlikely. The shortcut list will be renamed from "Hotkeys" to "Shortcuts" and is ordered by expected usage frequency. ## **Which problem are you trying to solve?** Current shortcuts follow a consistent internal pattern but deviate from established conventions used in comparable tools: * Single-key shortcuts like "m" or "v" trigger accidentally during typing * No distinction between toggle (persistent) and hold (temporary) interactions, both mapped to the same key with timing-dependent behavior, which is error-prone * Conflicting shortcuts override browser defaults (e.g. Ctrl + F is currently used for fullscreen instead of browser search) * Terminology ("Hotkeys") is non-standard This leads to unreliable keyboard control during live meetings. ## **Which solution would you like to see?** Users can reliably control all core meeting functions via keyboard. Shortcuts are predictable, prevent accidental input, and align with common patterns used in comparable tools. # **Target Users** All end users, particularly those relying on keyboard interaction during meetings. # **Scope** * Microphone (toggle + push-to-talk) * Video * Fullscreen * Whisper (push-to-talk only, when active) Out of scope: Talking stick is excluded due to low usage frequency. # **Benchmark** Zoom, Google Meet, Microsoft Teams, Jitsi Meet, Whereby, Cisco Webex, Slack Huddles, Discord, BigBlueButton (detailed command overview see comments) # **Requirements** The tool runs in the browser, where shortcut conflicts are a structural constraint. Chrome and Firefox reserve a significant share of Ctrl + Key combinations; a consistent 3-modifier pattern (Ctrl + Shift + Key on Windows/Linux, Ctrl + Cmd + Key on macOS) is the most reliable way to avoid collisions across browsers and operating systems. All toggle shortcuts in this ticket follow this pattern. Push-to-talk interactions use a single held key without modifier. This is intentional: hold interactions require sustained key pressure, which makes accidental triggering unlikely, and modifier combinations are ergonomically impractical to hold for extended periods. **Toggle (On / Off)** | Function | Windows / Linux | macOS | |----------|-----------------|-------| | Microphone | Ctrl + Shift + M | Ctrl + Cmd + M | | Video | Ctrl + Shift + V | Ctrl + Cmd + V | | Fullscreen | Ctrl + Shift + F | Ctrl + Cmd + F | **Push to Talk (Hold to activate)** | Function | Key | Condition | |----------|-----|-----------| | Microphone | Spacebar | When muted (no effect when microphone is active) | | Whisper | w | When whisper group is joined (fires regardless of mute state) | * Windows and Linux: share the same modifier pattern, as most Linux desktop environments follow the same browser shortcut conventions. * Shortcut notation uses the form Ctrl + Shift + M; uppercase letters are used throughout, since Shift is already part of every combination. ### Additional requirements: * Push-to-talk via Spacebar (hold), available when microphone is muted * Toggle and hold interactions are mapped to separate keys with no timing dependency * No conflicts with browser or system shortcuts (Ctrl + F / Cmd + F must remain browser search) * UI labels use "Shortcuts" throughout; overlay title is "Keyboard Shortcuts" * Tooltips display the current action label with shortcut in parentheses, updating with state: "Turn off audio (Ctrl + Shift + M)" / "Turn on audio (Ctrl + Shift + M)" * Shortcut list ordered by expected usage frequency (microphone first) ### **Known Limitation** Push-to-talk via Spacebar requires focus outside any text input field. When the chat input is focused, Spacebar types a space — PTT will not fire. The user must click outside the chat field first. This behavior is consistent with how comparable tools handle the same scenario and is intentional. # **Acceptance Criteria** * Given the user presses Ctrl + Shift + M / Ctrl + Cmd + M, the microphone toggles on or off * Given the user presses Ctrl + Shift + V / Ctrl + Cmd + V, video toggles on or off * Given the user presses Ctrl + Shift + F / Ctrl + Cmd + F, fullscreen toggles on or off * Given the user holds Spacebar while muted, the microphone is active only while the key is held * Given the user holds Spacebar while the microphone is active, no action is triggered * Given the user holds W while a whisper group is joined, whisper is active only while the key is held, regardless of microphone mute state * Given the user types text without modifier keys, no shortcut is triggered * Given the user presses Ctrl + F / Cmd + F, browser search is triggered * Given the shortcut list is displayed, labels use uppercase notation, correct terminology, and are ordered by usage frequency * Given the user hovers over a meeting control, the tooltip displays the current action label with shortcut in parentheses * Given the system state changes (e.g. audio on → off), the tooltip action text updates while the shortcut remains unchanged # **UX / Notes** {width="900" height="585"} This mockup illustrates **structure and placement only,** so no final spacing, colors, or typography. It shows: * Shortcut list separated into two sections: Toggle (On / Off) and Push to Talk (Hold to activate) * Ordering by expected usage frequency # **Definition of Done** * Shortcuts implemented consistently across all three listed functions * No single-key triggers remain for critical actions * No conflicts with browser or system shortcuts * PTT limitation documented in UI (e.g. tooltip or help text) * Acceptance criteria fulfilled * Reviewed and tested ### Out of Scope * screen sharing and raise hand are covered separately in https://git.opentalk.dev/opentalk/product/tickets/-/work_items/180