The best voice experience leaves room for text

The same customer may want to speak while cooking, type on a crowded train, and read an answer later. A useful voice agent accommodates those situations without assuming that everyone can or wants to use a microphone.

When adding voice to your company website in September 2026, start with the conversation around the voice: how someone begins, interrupts, ends, and continues in text.

Keyboard access is part of the experience#

WCAG 2.2's keyboard criterion requires functionality to be available through a keyboard interface, with an exception for genuinely path-dependent input. Its no-keyboard-trap criterion requires users to be able to move focus away from a component. These principles apply to the controls around a voice conversation, too. Keyboard guidance, no-keyboard-trap guidance.

That is a reason to test the start, mute, end, and close controls with a keyboard. It is not a claim that adding a text box alone makes an entire website accessible.

A voice conversation needs an exit at every stage

1. 01 →Before the callMake the start control clear and keep text chat available.
2. 02 →During the callShow listening state and make interruption and ending obvious.
3. 03If voice failsExplain what happened and offer a usable text path.

Test meaning, not just sound#

A pleasant voice is not enough. Ask a question containing a date, a product name, or an address. Listen for whether the answer preserves those details. A misheard number can matter more than a slightly unnatural pause.

Try a short question and a longer one with a correction: “Do you open at nine—sorry, I mean on Saturday?” Interrupt an answer and check that old audio does not continue speaking over the next turn. Repeat with the languages your customers actually use; one successful English call does not establish quality in Korean or Uzbek.

The real website is the test surface#

A dashboard preview and an embedded widget run in different browser contexts. The host site's permissions and security settings can affect microphone access. A call that works in a preview still needs to be checked on the website your customers visit.

Make Agent Fast supports voice messages and live calls through configured voice providers. Availability depends on provider configuration, plan access, and available usage. Follow the voice setup guide, then check your actual embed on the browsers and devices your customers use.

Include a denied microphone permission, a noisy room, a slow connection, and a deliberate end-call action. These are ordinary customer situations, not unusual edge cases.

Keep the promise modest and useful#

Introduce voice as another way to ask a question. Avoid promising perfect recognition or uninterrupted availability. When audio cannot complete, a readable answer or a clear route to text gives the customer a way forward.

Before sharing your agent, hand your phone to a colleague. Ask them to start a call, stop it, and send a text question without coaching. The moment they hesitate is often more actionable than another round of voice tuning.