Support work shouldn't require both hands or both eyes.
Voice input and read-aloud are built into every chat — the agent console, the customer widget, and the help center. Keyboard shortcuts cover every common action. Screen readers are a first-class target, not an afterthought.
Five very different people, one set of features
Agents resting their wrists
An hour of typing replies turns into an hour of dictating them. The mic button is right where the keyboard would be.
Customers using screen readers
The chat widget on every brand's help center has labeled controls, live regions for new messages, and works without sight or pointer.
Anyone with one hand busy
Reply by voice, hear the next ticket read out. Useful when you're holding a coffee, a kid, or a phone in the other hand.
Low-vision agents
Read-aloud on every reply and help-center article. Focus rings are visible, not invisible — even on the brand colors.
Different attention shapes
Multi-tab persistence means context switches don't lose your place. Keyboard-first navigation cuts pointer fatigue.
Built in across the product
Not a separate accessibility plugin — these are how every chat surface works, all the time.
Voice input on every chat
Press the mic in the agent console, customer widget, or help-center search box. We transcribe locally where the browser supports it, server-side otherwise. Works in 60+ languages.
Read aloud on every reply
Tap play on a message, an article, or a draft to hear it back. Useful for proofing your own reply before sending, or just listening to a long thread while doing something else.
Keyboard-first everywhere
Switch tabs with ⌘1–9, open a ticket from the rail with arrow keys + enter, post a reply with ⌘↵, navigate the chat with j/k. Every common action has a shortcut, documented in the in-app help.
Screen-reader tested
Live regions on every chat thread, labeled buttons and form controls, focus management on dialog open/close, ARIA roles where they help. Tested with VoiceOver on macOS + iOS and NVDA on Windows.
Visible focus everywhere
Every interactive element has a visible focus ring. Brand colors are picked so the ring contrasts against any background — including the lime and peach accents.
Works across languages
Translate any customer message inline, draft in your own language, send in theirs. Voice input and read-aloud both follow your agent profile's preferred language.
Built against the spec, not the marketing tag
We target WCAG 2.2 AA across the workspace, customer widget, and help center. The EU Accessibility Act (Directive 2019/882, in force June 2025) references EN 301 549 → WCAG 2.1 AA — 2.2 AA is a strict superset, so the same work covers both. We publish a self-assessed conformance report covering scope, methodology, and open gaps. No NDA, no procurement gymnastics.
WCAG 2.2 AA
Targeted across the workspace console, customer widget, and help center. axe-core runs against the marketing accessibility surface in CI; coverage is expanding surface by surface, with each addition logged in the conformance report's changelog.
EU Accessibility Act
In scope under EAA Directive 2019/882 (in force June 2025). Voice input, read-aloud, keyboard-first navigation, and screen-reader support are built in — and the gaps we still have are listed openly in the conformance report.
Assistive technology
VoiceOver (macOS / iOS), NVDA + JAWS (Windows), TalkBack (Android), Dragon for dictation. Spot-checked during feature review; no formal scripted test matrix yet — and we'd rather say so than overclaim.
Try a helpdesk that doesn't fight your accessibility tooling.
Voice input, read-aloud, keyboard navigation, screen-reader support — every chat surface, every brand, every language. No add-on, no extra plan.