Keyboard shortcuts are available for power users
Why it matters
WCAG 2.2 SC 2.1.1 requires all functionality to be operable via keyboard. AI chat products that force mouse interaction exclude keyboard-dependent users — people with motor disabilities, power users, and developers who never leave the keyboard. The minimum bar — Enter to submit, Shift+Enter for newline — is so widely expected that its absence signals an incomplete implementation. Products missing it consistently receive poor reviews from technical evaluators and fail accessibility audits that gate enterprise procurement.
Severity rationale
Info because the gap is a polish and accessibility deficit rather than a data-loss or security failure, but it reliably signals to power users that the product is unfinished.
Remediation
Add an onKeyDown handler to the chat textarea that at minimum handles Enter (submit) and Shift+Enter (newline). Wire Escape to the stop handler when streaming is active. Both are zero-dependency additions to src/components/chat/ChatInput.tsx.
const handleKeyDown = (e: React.KeyboardEvent<HTMLTextAreaElement>) => {
if (e.key === 'Enter' && !e.shiftKey) {
e.preventDefault()
handleSubmit()
}
if (e.key === 'Escape' && isLoading) {
stop()
}
}
<textarea
onKeyDown={handleKeyDown}
placeholder="Message (Enter to send, Shift+Enter for newline)"
/>
Document the shortcuts in a tooltip or placeholder text — discoverability is half the value.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the AI UX Patterns Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 2.1.1 — Keyboard — all functionality operable via keyboard
Taxons
History
- 2026-04-18·v1.0.0·Initial import from ai-ux-patterns·automated