Dictation as a Reasonable Accommodation: A Guide for Mac Users, HR, and IT

Dictation software is a recognized reasonable accommodation under the Americans with Disabilities Act (ADA) for employees with typing-related limitations — carpal tunnel syndrome, repetitive strain injury, arthritis, tendinitis, post-surgical hand recovery, dyslexia, dysgraphia, and others. The Job Accommodation Network (JAN), the U.S. government-funded service operated by West Virginia University under a cooperative agreement with the Department of Labor's Office of Disability Employment Policy, lists speech recognition as a standard accommodation across most of its A-to-Z disability conditions.

Voibe is our product. We make a Mac-only on-device dictation app. We have a clear interest in being recommended here, and this page does not hide that. The structural facts are independently verifiable: Voibe processes all audio on the employee's Mac and sends nothing to our servers, which is the property that matters most for accommodation contexts where the dictated content includes sensitive personal or medical information. For Windows fleets, mixed-platform organizations, or accommodations that need cross-platform tooling, this page covers the alternatives honestly.

This page is not legal advice. For specific accommodation decisions, consult JAN's free consultation, employment counsel, or your organization's ADA coordinator.

A reasonable accommodation under Title I of the ADA is a modification or adjustment to a job, work environment, or hiring process that enables a qualified individual with a disability to perform essential job functions. Speech recognition and dictation software are listed by the EEOC and JAN as standard accommodations across most typing-related disabilities. The process is well-established and the cost is typically modest — JAN's longitudinal study of more than 4,500 accommodation cases puts the median cost across all categories at approximately $500 per accommodation, and roughly half of all accommodations cost nothing beyond time.

The standard request process has four steps:

1. The employee makes a written request to HR. The request does not need to use specific legal language or invoke the ADA explicitly. It needs to identify a job-related limitation and propose (or ask for help identifying) an accommodation. JAN provides a free accommodation request template that employees can use as a starting point.
2. Medical documentation establishes the limitation. A treating clinician — hand surgeon, rheumatologist, neurologist, occupational therapist, or primary-care physician — provides a letter or form confirming the typing-related limitation. The documentation does not need to disclose the diagnosis in clinical detail; it needs to establish that the limitation exists and that the proposed accommodation is reasonable. Many employers accept a template letter or a JAN-style accommodation form.
3. HR engages in an "interactive process." The interactive process is a documented back-and-forth between employer and employee to identify an accommodation that works. For dictation, this usually involves: confirming the employee's platform (Mac vs Windows), confirming the workflow (writing-heavy vs occasional dictation vs sustained voice input), and selecting a specific product. The interactive process is a legal requirement — an employer who denies an accommodation without engaging in this process is on weaker legal ground than one who engages and reaches a different conclusion.
4. The accommodation is provisioned. For dictation, this typically means the employer purchases the license, the employee installs the software on their work Mac, and the employee receives any necessary training. License management varies by employer; some procure through standard software-purchasing channels, some reimburse the employee after purchase.

If an accommodation request is denied, the standard escalation is to JAN's free consultation (for both employees and employers), then to employment counsel, and ultimately to the EEOC. Denial on undue-hardship grounds is rare for dictation software given how inexpensive and well-established it is as an accommodation.

Dictation accommodates any condition that makes sustained typing painful, slow, error-prone, or physically impossible. The cluster below links to the condition-specific guides; this hub does not re-explain the conditions themselves. Use the guide for your condition for the clinical context, the specific Hands-Free workflow, hotkey-mapping guidance, and the relevant JAN page.

• Carpal tunnel syndrome (CTS) — median-nerve compression at the wrist. Best Dictation Software for Carpal Tunnel · How to Type With Carpal Tunnel · JAN: Carpal Tunnel Syndrome
• Arthritis (rheumatoid, osteoarthritis, psoriatic) — inflammatory or degenerative joint disease affecting the hands. Best Dictation Software for Arthritis · Typing With Arthritis Guide · JAN: Arthritis
• Tendinitis (de Quervain's, ECU, flexor, intersection syndrome) — tendon inflammation and tenosynovitis. Best Dictation Software for Tendinitis · JAN: Tendonitis (JAN uses the "Tendonitis" spelling)
• Post-surgical hand recovery — carpal tunnel release, trigger finger release, de Quervain's release, Dupuytren's, tendon repair, fracture pinning, CMC arthroplasty. Best Dictation Software After Hand Surgery · Recovering From Hand Surgery: The 4-Phase Recovery Framework
• Repetitive strain injury (RSI) / cumulative trauma — soft-tissue injuries from sustained repetitive motion, often a mix of conditions. JAN: Cumulative Trauma Disorders / RSI
• Hand pain without a single diagnosis — overlapping, undiagnosed, or pattern-based hand pain. Best Dictation Software for Hand Pain
• Dyslexia and dysgraphia — reading and writing differences where voice output can sidestep the typing bottleneck even though the limitation is cognitive rather than physical. JAN: Dyslexia
• Mobility and dexterity limitations — broader motor conditions (stroke recovery, cerebral palsy, multiple sclerosis, spinal cord injury) that limit fine-motor keyboard control. JAN maintains accommodation pages by condition; the activation model considerations on the accessibility dictation hub apply.

The unifying property across all of these is that typing is a friction or pain source, and voice input removes that friction for the dictated portion of the workday. None of these conditions require Voibe specifically — they require dictation as a category. Voibe's case is that the activation model (no held key) and the data path (on-device) match accommodation contexts better than the cloud-by-default alternatives, and that the price is below JAN's median.

An accommodation request involves disclosing a medical limitation to an employer. The dictated content that follows often references the underlying condition — emails to HR about the accommodation, doctor's notes the employee drafts and forwards, medication names the employee is learning to pronounce, descriptions of symptoms in messages to a partner or care team. None of this content is automatically protected health information under HIPAA when the employee creates it on a work device, but most employees would prefer it not to leave their machine.

Cloud-based dictation tools transmit the audio to a vendor's servers for transcription. The audited cloud tools (Wispr Flow, Aqua Voice, Otter Enterprise) have SOC 2 and ISO compliance posture; some offer HIPAA BAAs for covered entities. The audit posture is not nothing. But the architectural fact stays the same: in a cloud pipeline, the audio of an employee's voice talking about their health condition transits an internet connection and is processed on infrastructure the employee does not control. The audit reduces the surface area; it does not eliminate it.

On-device dictation eliminates the surface area instead of governing it. Voibe processes audio on the employee's Mac using OpenAI's Whisper models running on Apple Silicon's Neural Engine. The audio is converted to text on-device and discarded after transcription. There is no Voibe server in the path. There is no Voibe account that could be subpoenaed. There is no subprocessor chain that could be compromised. For IT-security review, the question "what is your data residency for employee dictation content?" has the answer "the employee's Mac" — which is a substantially simpler review than the cloud equivalent.

For the broader privacy framing, see the Why Offline Dictation Matters explainer and the Dictation Privacy Hub. For HIPAA-specific contexts (covered entities with PHI workflows), see the dedicated HIPAA Dictation Guide.

Voibe is macOS-only and runs on Apple Silicon. Set fleet expectations honestly up front; this disqualifies most Windows and Linux deployments.

• Hardware: Apple Silicon Mac (M1, M1 Pro, M1 Max, M1 Ultra, M2, M2 Pro, M2 Max, M2 Ultra, M3, M3 Pro, M3 Max, M4, M4 Pro, M4 Max). Intel Macs are not supported.
• Operating system: macOS 13 (Ventura) or later. Most modern accommodation contexts will be on macOS 14 (Sonoma), macOS 15 (Sequoia), or macOS 16 (Tahoe).
• Permissions: Microphone (required), Accessibility (required for system-wide text insertion), Notifications (optional). No Screen Recording, Full Disk Access, Camera, or Contacts permissions.
• Network: Not required for dictation itself. Network is used only for license validation at install/registration time and for periodic check-ins if the license is subscription-based. Audio transcription does not use the network.
• Disk space: Approximately 1.5 GB for the application and Whisper model files, downloaded once during install.
• What is NOT supported: Intel Macs, Windows (any version), Linux, iPad (the macOS app does not run under Designed-for-iPad mode), and macOS earlier than 13.

If the employee in question is on a Windows or mixed-platform fleet, the right path is a different product. See Honest Fit Guidance below for the platform-by-platform recommendations.

This section is written to be forwarded as a single link to a security reviewer. It documents the data path, permissions, and posture of Voibe so an employee can send one link to security and receive a yes — instead of receiving a security questionnaire that delays the accommodation by weeks. The facts below are independently verifiable on getvoibe.com and in the macOS permission UI.

What Data Leaves the Device

Nothing. Voibe processes all speech locally on the employee's Mac using OpenAI's Whisper models running on Apple Silicon's Neural Engine. The audio is captured by the microphone, transcribed on-device, typed into the active application's text field, and discarded. No audio is uploaded. No transcription is uploaded. No dictation content reaches a Voibe server because there is no Voibe server in the transcription path. The privacy policy at getvoibe.com/privacy documents this verbatim.

Network Traffic Generated by Voibe

The application generates network traffic in two specific cases:

• License validation at install and on a periodic schedule. The application contacts the Voibe license server with the license key to confirm validity. The license-validation request contains the license key and a machine identifier. It does not contain any dictation content.
• Application updates. The application checks for newer versions and offers updates. This is standard macOS application behavior.

Both can be observed in the operating system's network-activity inspection. Neither carries dictation audio or transcribed text.

Permissions Voibe Requests (and Why)

• Microphone (required) — to capture the audio for transcription. The microphone is active only when the user explicitly activates dictation, not in the background. macOS displays a microphone-active indicator in the menu bar at all times during use, which the user can verify visually.
• Accessibility (required) — to insert transcribed text into the active text field of whatever application the user is working in. macOS gates this permission specifically because it allows an application to send keystrokes to other applications. It is the standard permission used by every system-wide dictation tool (Apple Dictation, Wispr Flow, SuperWhisper, VoiceInk) and by accessibility tools generally. Voibe uses this permission to type the transcribed text; it does not read keystrokes from other applications.
• Notifications (optional) — to surface status messages (license-expiry reminders, update availability). Voibe functions without this permission; it is a UX nicety, not a requirement.

Voibe does NOT request: Screen Recording, Full Disk Access, Camera, Contacts, Calendar, Reminders, Photos, Location, or any of the other gated permissions macOS exposes.

Account and Identity

Voibe does not require an account. There is no Voibe user identity, no email/password, and no profile. License management is via a license key entered once. This eliminates an entire category of account-compromise risk that exists for cloud-based dictation products.

Telemetry on Dictation Content

Voibe does not transmit dictation content as telemetry. Voibe does not train AI models on user dictation. Voibe does not maintain a server-side copy of dictated text or audio. This is not a configurable setting — it is an architectural property of how the product is built (no server in the path).

Telemetry on Application Health

The application collects standard crash-reporting telemetry (the macOS crash log that the system generates on application crashes), which is sent to Voibe only if the user opts in when prompted by macOS. This telemetry does not contain dictation content. It contains stack traces, application version, and operating system version.

Compliance Posture

Voibe does not maintain a SOC 2 attestation or a HIPAA BAA framework. The architectural design of the product — no server-side processing of audio or transcription — makes these frameworks largely non-applicable. A BAA is required when a vendor receives or processes PHI on behalf of a covered entity; Voibe receives neither. A SOC 2 attestation evaluates controls on systems that handle customer data; Voibe's transcription system does not handle customer data because it runs entirely on the customer's device. For procurement processes that require a SOC 2 report regardless of architecture, contact hi@getvoibe.com — we will provide the architectural-attestation language that customers have used successfully in prior procurement reviews.

Subprocessors

Voibe's transcription path has no third-party subprocessors. The Whisper models are bundled with the application and run on Apple Silicon's Neural Engine via Apple's Core ML framework — Apple is the platform vendor, not a subprocessor of Voibe in the data-processing sense. License management uses standard hosting infrastructure (the license-key transit and validation), which does not carry dictation content. There is no transcription subprocessor chain to disclose.

Data Retention and Deletion

Voibe does not retain dictation audio or transcribed text on Voibe-controlled systems, because none reaches Voibe in the first place. The transcribed text is inserted into whatever application the user is dictating into; the audio is discarded after transcription. Any retention of the resulting text is governed by the application the user dictated into (e.g., if the user dictates into Slack, the resulting message is retained per Slack's retention policy). This is the same posture as any other input method (typing, clipboard paste, Apple Dictation).

Vendor Continuity Risk

Voibe is a small indie product. Customers reasonably ask what happens to the dictation capability if the company stops operating. The architecturally relevant fact: because the application runs entirely on the user's device, an existing installation continues to function regardless of Voibe's operational status. The license-validation server affects new installations and license renewals, not in-use installations. For accommodation contexts that require maximum continuity assurance, the lifetime license is the appropriate purchase tier.

If you are an employee on Mac who needs dictation as an accommodation, follow this four-step process. The template below is a starting point — adapt it to your situation.

Step 1: Identify Your Condition and the Workflow Impact

Before writing the request, get clear on three things: (1) the typing-related limitation you have, (2) the specific work tasks that are affected, and (3) why voice input would mitigate the limitation. You do not need to disclose your diagnosis in the request itself, but you need to be able to describe the limitation in functional terms.

Step 2: Draft the Request

Send a written request to HR (email is fine). The request needs to identify the limitation, propose the accommodation, and ask to begin the interactive process. A starting template:

Subject: Request for reasonable accommodation under the ADA

Dear [HR contact],

I am writing to request a reasonable accommodation under the Americans with Disabilities Act. I have a [typing-related condition / hand-pain condition / cognitive-processing condition that affects typing] that limits my ability to [describe the functional limitation — e.g., "type for sustained periods," "type without pain," "type accurately under time pressure"]. I am asking that the company provide dictation software as an accommodation so I can use voice input as a primary text-entry method.

I work on a [Mac model and macOS version, e.g., "MacBook Pro M2 running macOS 15"]. The dictation tool I am requesting is Voibe, which is a Mac-only on-device dictation application designed for users with typing-related limitations. The cost is $149 lifetime (one-time). The vendor has materials prepared for IT security review at getvoibe.com/resources/dictation-reasonable-accommodation-mac that I can forward to IT.

I have supporting documentation from [treating clinician — e.g., "my hand surgeon," "my rheumatologist," "my occupational therapist"] that I can provide as part of the interactive process. I would like to begin the interactive process as soon as is practical.

Thank you,
[Name]

Adapt the bracketed sections to your situation. If your employer is small or does not have a formal accommodation process, the same letter works — "HR" becomes your manager or the founder.

Step 3: Provide Medical Documentation

Your employer will typically request medical documentation from a treating clinician. The documentation needs to establish the limitation and confirm that voice input is a reasonable mitigation. Many clinicians have a standard form they use; if not, a one-page letter on letterhead is sufficient. JAN offers a free guidance page on documentation if you or your clinician have not been through this before.

Step 4: Engage in the Interactive Process

Once HR has the request and documentation, they will engage in the interactive process. For dictation accommodations, this is typically short — confirming the platform, the workflow, and the tool. Forward the IT-security brief above to whoever in IT or security needs to approve the software. The accommodation is usually approved within a week or two of the initial request.

If the request is denied, contact JAN's free consultation for individuals before escalating. JAN consultants have seen the same denial patterns repeatedly and can suggest the most effective next step for your situation.

For HR partners, ADA coordinators, and accommodations specialists provisioning dictation for one or more employees, the path is straightforward.

Approval

The accommodation request typically includes the employee's platform, a description of the limitation, and supporting medical documentation. The interactive-process conversation should confirm: (1) that the employee is on Mac (otherwise, Voibe is not the right product), (2) that the proposed tool addresses the limitation in question, and (3) any workflow-specific considerations (does the employee need custom vocabulary for domain-specific terminology? does the activation model fit their condition?).

For Mac employees with hand-related conditions, the most common approval question is whether the activation model works. Voibe's Hands-Free Mode activates with a configurable double-tap and does not require holding a key. For employees who cannot reliably double-tap (severe arthritis, fine-motor limitations), the hotkey is remappable to a single key, an external hardware switch, or a foot pedal. The condition-specific guides linked above cover the activation choices for each condition.

Funding

The standard approaches are: (a) the employer purchases the license directly through the procurement process, (b) the employee purchases and the employer reimburses, or (c) the employer assigns from a pool of licenses if the organization has provisioned multiple accommodations. For one-time accommodations, the $149 lifetime license is typically the simplest line item — appears once in the budget, does not require renewal management, is well below JAN's $500 median accommodation cost. For organizations provisioning multiple seats, the Team plan amortizes lower per-seat; contact hi@getvoibe.com for volume quotes at 10+ seats.

Provisioning

Provisioning is per-employee. The employee installs Voibe on their work Mac and enters the license key once. There is no central admin console, no SSO integration, and no MDM-deployable package. For accommodation contexts these are usually not blockers — the accommodation is per-employee by definition. For organizations that require MDM-deployable installers or SSO-managed entitlements, the workflow is different from a standard SaaS provisioning and should be discussed with us before purchase; we can usually accommodate.

License Portability for Employee Turnover

A standard lifetime license is tied to the original purchaser. For accommodation contexts where the employer wants the license to be reassignable to a new employee if the original employee leaves, contact hi@getvoibe.com before purchase — we will issue a reassignable license scoped to the employer's organization. This is a common request from accommodation-funded purchases and we have a standard handling for it.

Auditing and Reporting

The architectural choices that make Voibe a good accommodation tool (no server, no telemetry, no central console) also mean there are no central usage reports. For accommodation programs that require usage metrics for reporting purposes, this is a constraint — usage data lives only on the employee's device. If your accommodation program requires this kind of reporting, set expectations with the employee and HR ahead of purchase; the alternative is to track accommodation usage at the program level (number of seats approved, number of employees served) rather than at the per-license behavioral level.

Whether you are an employee evaluating dictation for yourself or an HR partner evaluating it for an employee, the 4-Question Accommodation Audit is the structural test for whether a dictation tool is the right accommodation. Run through it before committing to a specific product.

Question 1: Is the limitation typing-related?

Dictation accommodates typing-related limitations. If the limitation is something else — reading, hearing, cognitive load that is not text-input-related, motor limitations that affect mouse use but not typing — the accommodation may need to include other tools alongside or instead of dictation. For mouse-and-navigation limitations, see Talon for full hands-free OS control. For screen-reading or magnification needs, macOS includes VoiceOver and Zoom; the JAN page for the specific condition will list the relevant tools.

Question 2: Does the employee have an Apple Silicon Mac?

Voibe is Mac-only and requires Apple Silicon (M1 through M4) on macOS 13 or later. For Intel Macs, Windows, Linux, or iPad-only deployments, Voibe is not the right product. The platform-by-platform alternatives are in the next section. If platform fit is uncertain, confirm before approval — provisioning the wrong-platform tool is a frequent waste of approval cycles in accommodation contexts.

Question 3: Is the dictated content sensitive enough that data path matters?

For accommodation contexts where the employee will dictate medical context, mental-health content, personal disclosures, financial details, or confidential business material, the data-path question is structural. On-device dictation keeps that content on the employee's device. Cloud dictation transmits it to a vendor. The audited cloud tools have compliance frameworks that reduce the surface area, but the architectural fact — content transits an internet connection and is processed on infrastructure the employee does not control — does not change. For most accommodation contexts, this argues for on-device. For workflows where cross-platform reach matters more than data path (e.g., the employee needs to dictate on both Mac and iPhone), Wispr Flow with Privacy Mode and an organizational BAA is the standard cloud alternative.

Question 4: What is the employee's activation tolerance?

Dictation tools differ on activation model. Most require holding a hotkey (Wispr Flow default, SuperWhisper default, Aqua Voice default, VoiceInk default). Voibe defaults to a double-tap (no held key) and can be remapped to a single key, external hardware switch, or foot pedal. For employees with hand pain, sustained key-holds defeat the purpose of switching to voice — the held-key activation reintroduces the exact joint or tendon stress the accommodation is supposed to mitigate. The activation model is the single most common reason a generic dictation tool fails as an accommodation; verify before approval.

Voibe is right for: Mac employees on Apple Silicon, on macOS 13 or later, with typing-related limitations, who do not need cross-platform reach to non-Mac devices for the accommodation in question. Within that scope, the on-device data path and the no-held-key activation model are accommodation-grade fits.

Voibe is not right for several common situations. Be honest about these up front rather than discovering them during the interactive process.

• Windows or mixed-platform fleets — Voibe is Mac-only. For Windows employees, Dragon Professional v16 is the established on-device alternative ($699.99 one-time). For cross-platform needs, Wispr Flow with Privacy Mode and an organizational BAA is the standard cloud option.
• Intel Macs — Voibe requires Apple Silicon. For Intel Macs that cannot be upgraded, Apple Dictation (built in) and VoiceInk (open-source) are the candidates; both run on Intel Macs.
• Linux deployments — There is no native Voibe equivalent. The category for Linux is sparse; the most common path is a Whisper-based open-source tool the employee configures themselves, or remote access from a Linux workstation to a Mac that runs the dictation.
• Full hands-free OS control (mouse, keyboard, navigation) — Voibe is the dictation layer. For employees who need to control the operating system without touching the keyboard or mouse at all, pair Voibe with Talon. Talon is more powerful, fully hands-free, and has a steeper learning curve. The two coexist cleanly — Talon handles mouse and navigation; Voibe handles the dictation. We respect Talon.
• Conditions where typing is not the bottleneck — Some disabilities affect text input in ways that voice does not solve. Severe dysarthria, for example, may make voice input less effective than typing. Aphasia may affect both. For these conditions, the accommodation may need to be different (predictive text, AAC tools, human note-taking support). JAN's condition-specific pages are the best reference.
• Centrally managed enterprise environments that require MDM-deployable installers and SSO entitlements — Voibe is a per-user install with license-key registration. If your accommodation program requires central deployment infrastructure, contact us before purchase; we can sometimes accommodate, but the standard product is per-employee.
• Procurement processes requiring SOC 2 reports as a precondition — Voibe does not maintain a SOC 2 attestation, by architectural choice (no server in the data path). For procurement contexts where SOC 2 is non-negotiable, see the architectural-attestation language in the IT-security brief above and contact hi@getvoibe.com.

Acknowledging these constraints up front is part of the credibility of an accommodation recommendation. Voibe is the right tool for a specific cohort. For everyone else, the cohort-appropriate tool is the right tool — and we will tell you which it is if you ask.

The Job Accommodation Network's longitudinal cost study (the most-cited authoritative figure for accommodation pricing) puts the median accommodation cost across all categories at approximately $500 per accommodation. About half of all accommodations cost nothing beyond time.

Voibe pricing relative to that baseline:

For most accommodation contexts, the lifetime license is the appropriate purchase tier — it appears once in the budget, requires no renewal management, and stays well under the JAN median. Many employers process it as an equipment or accessibility-tool purchase rather than as a software-subscription line item.

Voibe is not the only dictation tool that can serve an accommodation; it is the one with the structural fit closest to accommodation contexts (no held key, no cloud, Mac-native, below JAN median). The Mac alternatives and their tradeoffs:

Apple Dictation (Built In)

Cost: Free. Activation: Fn key or configurable shortcut (held). Data path: On-device on Apple Silicon (undocumented cloud fallback in some configurations). Fit for accommodation: Partial. The 30-second session timeout makes it unsuitable for sustained dictation; the absence of custom vocabulary limits domain-specific accuracy. Good for occasional use within a broader accommodation; usually not the only tool an employee with a typing-related limitation will rely on. See the Apple Dictation pricing breakdown for the hidden-cost framework.

SuperWhisper

Cost: $249.99 lifetime, $84.99/year. Activation: Held hotkey by default; configurable. Data path: Hybrid — on-device modes (Tiny, Base, Small, Standard, Parakeet) plus optional cloud modes (Ultra, Super Mode) that proxy to third-party LLM providers. Fit for accommodation: Strong on the on-device modes if held-hotkey activation is acceptable. The most flexible mode system in the category. Higher price than Voibe lifetime. See the Superwhisper safety investigation for the cloud-mode subprocessor details.

VoiceInk

Cost: $25–$49 on Mac App Store, or free GPL v3.0 build from GitHub. Activation: Held hotkey by default. Data path: Fully on-device. Fit for accommodation: Strong on data path and cost; less product polish, smaller support surface area, and held-hotkey activation. For organizations comfortable with open-source software and employees comfortable with somewhat less polish, this is a credible budget option.

Wispr Flow

Cost: $144/year Pro, with a free tier (2,000 words/week). Activation: Held hotkey by default; configurable. Data path: Cloud, with Privacy Mode opt-in for individuals and default-on for accounts with a signed BAA. SOC 2 Type 2, ISO 27001:2022, HIPAA BAA available. Fit for accommodation: The right choice when cross-platform reach matters and the organization can sign a BAA. Architectural cloud-by-default posture is the structural consideration regardless of audit posture. See the Is Wispr Flow Safe? investigation for the full data-handling framing.

Dragon (Windows-Only Reference)

For comparison: Dragon Professional v16 is the Windows on-device incumbent at $699.99 one-time. Dragon discontinued the Mac product in 2018; there is no current Dragon-on-Mac offering. For organizations with both Mac and Windows employees, the standard accommodation pattern is on-device per platform — Voibe on Mac, Dragon on Windows — rather than a single cross-platform cloud tool. See the Dragon NaturallySpeaking alternatives guide for the Mac migration framing.

Common questions from HR partners, ADA coordinators, and benefits teams provisioning dictation as a reasonable accommodation, organized by topic.

Legal and Process

Does an employer have to approve dictation if an employee requests it?
Employers must engage in the interactive process and provide an effective accommodation unless doing so imposes an undue hardship. They are not required to provide the specific tool requested if a different tool is equally effective. Denial on undue-hardship grounds for dictation specifically is uncommon given the low cost and well-established efficacy. JAN's free consultation is the standard escalation if a denial is contemplated.

What documentation should we require from the employee?
Documentation from a treating clinician establishing the typing-related limitation and confirming that voice input is a reasonable mitigation. The documentation does not need to disclose the diagnosis in clinical detail — it needs to establish that the limitation exists. JAN's documentation guidance covers acceptable forms.

Can we require the employee to use a specific tool we choose, rather than the one they requested?
If the alternative is equally effective for the limitation, yes. For dictation, "equally effective" usually means same data-path posture, same activation model fit, and same workflow compatibility. If the employee requested Voibe because of the on-device data path and you propose a cloud-based alternative, you may need to demonstrate that the cloud alternative is equally effective for their specific accommodation needs — which often means signing a BAA and configuring privacy modes.

Privacy and Security

Do we need IT security to review Voibe before approving the accommodation?
Most organizations require it. The forwardable IT-security brief above is designed for that review — one link to security, intended as a one-pass review rather than a multi-week questionnaire process. For organizations that require formal questionnaire responses (SIG, CAIQ, custom), contact hi@getvoibe.com; we have completed questionnaires for prior customers.

What happens if the employee dictates HIPAA-protected content (e.g., they work for a covered entity)?
Because Voibe processes audio on-device and discards it after transcription, no PHI reaches Voibe. There is no business-associate relationship to establish and no BAA to sign. For covered-entity workflows that still require explicit framework documentation, see the HIPAA Dictation Guide; the architectural posture is what matters legally, not a BAA that would govern a data path that does not exist.

What about employee dictation of mental-health or other sensitive content?
Same answer. The architectural property — no audio or transcription leaves the device — applies uniformly across content types. For accommodation contexts where the dictated content is mental-health, financial, legal-privileged, or otherwise sensitive, the on-device posture is the conservative default.

Provisioning and Cost

What's the simplest way to fund a one-time accommodation?
The Voibe lifetime license at $149 is typically the lowest-friction line item. It appears once in the budget, does not require renewal management, and stays well under the JAN $500 median. Process as an accessibility-equipment or accommodation purchase rather than as a software subscription.

Can we provision multiple seats centrally?
Yes, via the Team plan (3+ seats) or volume pricing for 10+ seats. Provisioning is per-employee (each employee installs on their own Mac), but license management can be centralized. There is no MDM-deployable installer or SSO entitlement system; for organizations that require those, contact us before purchase.

What if the employee leaves the company?
For licenses purchased through accommodation funding where portability matters, contact hi@getvoibe.com before purchase. We issue reassignable licenses scoped to the employer's organization in those cases — a common request from accommodation-funded purchases.

Fit and Alternatives

What if the employee is on Windows or Linux?
Voibe is Mac-only. For Windows, Dragon Professional v16 ($699.99 one-time) is the established on-device option. For Linux, the category is sparse; the most common path is a Whisper-based open-source tool or remote access from Linux to a Mac running the dictation tool.

What if the employee needs cross-platform dictation (Mac and iPhone, or Mac and Windows)?
The standard cloud option is Wispr Flow with Privacy Mode and an organizational BAA. The architectural tradeoff (cloud-by-default for cross-platform reach vs on-device per platform) is the decision the interactive process needs to make. For most accommodation contexts where the limitation is platform-specific, per-platform on-device is the more conservative pick.

What if the employee needs full hands-free OS control, not just dictation?
Pair Voibe with Talon. Talon handles mouse and navigation; Voibe handles dictation. Talon is more powerful and has a steeper learning curve. Both are accommodation-grade tools for different aspects of the same underlying limitation.

• Accessibility Dictation Hub — The condition-by-condition guide for users self-installing dictation, the sibling to this buyer-facing hub.
• Best Dictation Software for Carpal Tunnel — Median-nerve framing with night-splinting integration.
• Best Dictation Software for Arthritis — Joint-protection-aligned activation framing.
• Best Dictation Software for Tendinitis — Hotkey-by-inflamed-tendon mapping.
• Best Dictation Software After Hand Surgery — One-handed install and post-op hotkey mapping.
• Best Dictation Software for Hand Pain — Pattern-based decision tree for undiagnosed or overlapping conditions.
• HIPAA Dictation Guide — For covered entities and PHI workflows.
• Why Offline Dictation Matters — The privacy framing of on-device vs cloud processing.
• Cloud vs Local Dictation — The architectural tradeoffs between the two approaches.
• Dragon NaturallySpeaking Alternatives — For organizations migrating off discontinued Dragon-on-Mac and for Windows-Mac mixed fleets.
• Dictation Privacy Hub — Deeper coverage of voice-data privacy.
• Job Accommodation Network (JAN) — Free U.S. consultation for employees and employers on workplace accommodations under the ADA.
• EEOC: Reasonable Accommodation and Undue Hardship Under the ADA — The authoritative federal guidance.
• ADA.gov — The Department of Justice's ADA portal.

Dictation is a standard, well-established ADA reasonable accommodation for typing-related limitations. The decision an employer or HR partner needs to make is not whether to approve dictation in principle — JAN, the EEOC, and four decades of case law settle that question. The decision is which tool, for which employee, on which platform.

For Mac employees on Apple Silicon with typing-related conditions, Voibe is the tool we built specifically for this fit: Hands-Free Mode with no held key, on-device processing that keeps employee health context inside the device, and pricing well below the JAN accommodation median. Try Voibe for free on the free tier (300 words/day, no account) to verify the activation model and workflow fit before committing to the license purchase.

For Windows employees, mixed-platform fleets, or employees who need full hands-free OS control beyond dictation, the alternatives above are the right tools. The point of this page is not to push Voibe into accommodations it does not fit — it is to make the right tool obvious for the right cohort.

For accommodation provisioning at scale, volume quotes, license portability, or formal procurement processes, contact hi@getvoibe.com. We will respond and work with you directly.