Voice control when speech itself is changing.

What this page is not

This is written by the maker of one piece of software, and it is not clinical advice. Assistive technology for ALS, MND and other progressive conditions is a specialist field with clinicians, assessments and funding routes attached to it, and the single most useful thing on this page is the recommendation to get an assessment rather than to assemble a setup from search results.

Fluent is not an AAC device, not a communication aid, not eye-gaze access, and not a switch access system. It is a voice and text layer for operating Windows. Anybody telling you that a voice assistant is an access plan for a progressive condition is selling something.

Voice banking and message banking are time-sensitive and are best started while speech is still clear. If that has not been discussed yet, it is a more urgent conversation than any software on this page.

What voice control can genuinely do, while it works

Fatigue is the thing worth targeting. Reducing the number of deliberate physical actions in a day is a real gain, and it is a gain that arrives immediately rather than after a procurement cycle. Voice is good at anything you can name and at long text, and poor at precision pointing and at anything needing silence.

The highest-value use is not dictation, which the free built-in Windows tools already cover well. It is the multi-step work: opening and arranging the applications, moving between them, filing and sending. Those are the sequences that cost the most actions, and describing an outcome once is fewer utterances than relaying eight commands.

• Windows Voice Access is free, on-device, and the sensible starting point for dictation and direct commands.
• Keep the keyboard and pointer paths working alongside it, never instead of them.
• Prefer setups where any one layer can fail without taking the others down.
• Measure fatigue, not just whether a task completed.

Planning for the part where speech changes

Dysarthria changes recognition accuracy, and a setup that depends on being understood will degrade before it fails outright, which is the difficult version: it gets frustrating long before it gets impossible. Fluent has not formally evaluated its recognition on dysarthric or accented speech. That is named as the largest open gap in its own accessibility conformance report, and it should be treated as unmeasured rather than as working.

Practically, that means test with the actual speaker rather than a demo, retest as things change, and never let voice become the only path to something essential. Fluent accepts every request typed as well as spoken, deliberately, and typed input keeps working when voice does not.

A layered setup, and why the order matters

Build from the layer that will last longest, not the one that is easiest today. Eye-gaze and switch access outlast speech in most progressive conditions, so they belong in the plan early even if they are not yet the primary input. Voice sits above them as an accelerator, not underneath them as a foundation.

Fluent is designed to sit alongside other access technology rather than to replace it: it drives Windows through the same accessibility interfaces a screen reader reads, so it does not take exclusive control of the input stack. That also means it inherits whatever the accessibility layer exposes, which is worth testing with the specific applications that matter.

What it costs, and what stays free

Speech, dictation, text-to-speech, hotkeys, window and accessibility navigation, settings and export never consult a licence in Fluent and stay free permanently. Only the multi-step agent runs are metered, and the allowance is never zero: an expired card is not allowed to take away somebody else's input device.

That is a deliberate product rule rather than a promotion, and it exists for exactly this audience. If a lapsed subscription could lock somebody out of their own computer, the software would be a liability rather than an aid.

Questions

Keep reading

• Does voice control help with RSI?Reduce keystrokes and clicks in the order that costs least. Voice is one layer of that, not the whole answer.
• Does Fluent have a VPAT or accessibility conformance report?A self-assessment that names its gaps is more useful than an audit-shaped document that claims everything. This is the first kind.
• Can Fluent control Windows by voice?Say the outcome you want. Fluent prepares the Windows route and keeps its progress visible.

Sources

• Microsoft: set up voice access — The free built-in Windows option and its requirements.
• Fluent accessibility conformance report — Including the unmeasured dysarthric-speech gap named above.
• Fluent hands-free computer control — The layered setup this page summarises, in more detail.
• Fluent privacy and safety disclosure — What Fluent shows, what it asks before doing, and where data goes.