> For the complete documentation index, see [llms.txt](https://carec.gitbook.io/carec-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carec.gitbook.io/carec-docs/documentation/autonomous-mobility/voice-and-alternative-controls.md).

# Voice and Alternative Controls

CAREC must not assume every user can operate a conventional joystick or touchscreen.

## Candidate inputs

* Existing manual joystick
* Large accessible touch targets
* External switches or scanning interfaces
* Caregiver destination selection
* Voice destination commands
* Preset destinations
* Smart-environment requests such as approaching an automated door

A command such as “take me to the kitchen” is a **goal request**, not a motor command. CAREC must confirm the goal, validate the operating domain, plan an accessible route, and preserve cancellation and takeover.

Ambiguous voice commands require confirmation and must never initiate unexpected motion. Local processing is preferred for privacy; any cloud service needs explicit consent and a safe offline fallback.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://carec.gitbook.io/carec-docs/documentation/autonomous-mobility/voice-and-alternative-controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
