AI Companion Accessibility: Check Before You Subscribe
Check AI companion accessibility by completing the tasks you need, on the device and interface you will actually use, before subscribing. A voice demo is not enough: you need to reach the chat, read replies, send messages and control any audio without an inaccessible button blocking the way. This guide provides a worksheet, not a ranking of apps we have not accessibility-tested.
Key Takeaways
- Screen-reader access, generated speech and speech input are three different things.
- Check setup and account controls as carefully as the conversation itself.
- Record pass, fail or unknown for each task; a workaround belongs in the record.
- Do not buy a subscription to discover whether its cancellation route is usable.
- No named app receives an accessibility endorsement from this guide.
Start with the interface, not the voice demo
Apple describes VoiceOver as a gesture-based screen reader that announces screen items. Google’s TalkBack guide explains how it speaks what is on an Android screen and changes how you move through it. Those are operating-system capabilities, not evidence that a particular companion app exposes usable controls.
Keep three questions separate:
| Capability | What you are checking | What it does not establish |
|---|---|---|
| Screen-reader interface access | Can you identify and operate the chat, settings and account controls? | Whether generated character speech is included in your plan |
| Generated speech or voice chat | Can you hear a reply, pause it and stop a session? | Whether setup, payment or deletion controls work with a screen reader |
| Speech input or dictation | Can you enter a message, review it and correct it before sending? | Whether the rest of the interface is usable without touch or a mouse |
An app may meet one need and miss another. Decide which tasks are essential for you rather than treating “has voice” as a universal accessibility label.
Our voice-companion guide covers interaction features. The text-only companion guide covers a different buying preference. Neither should be read as proof of assistive-technology compatibility.
Record your setup before checking an app
Use a harmless fictional conversation, not your personal history. For example, ask the character to discuss a fictional garden and suggest a name for a tomato plant. You can check message handling without sharing medical, relationship or financial details.
Copy these fields into a private note:
- App name and app version, or exact website address.
- Device model and operating-system version.
- Screen reader and version, if used.
- Browser and version for web use.
- Input method: touch gestures, keyboard, dictation, switch or another method.
- Display settings relevant to you, including text size or zoom.
- Account tier, language and date checked.
Treat the native app and website as separate entries. A result in one interface does not establish the result in the other. Keep iPhone, Android and desktop observations separate too.
If you are new to a screen reader, learn its controls before judging the companion app. Apple warns that VoiceOver changes the gestures used to operate iPhone and provides a practice area. Google documents TalkBack activation through Settings → Accessibility → TalkBack, while noting that details vary by phone and Android version. Use the linked official instructions for your device, including how to turn the feature off.
Do not change an experienced user’s preferred assistive-technology setup simply to make an app appear to pass.
Copy this task-by-task accessibility worksheet
The following is an editorial screening tool. Every result starts as unknown; no row reports a CompanionScout product test.
Use pass when you completed the task with your recorded setup, fail when a barrier prevented it, and unknown when it was not checked or the result was unclear. Record assistance separately: a task completed by someone else is not proof of independent access.
| Task | What to attempt | Result and barrier notes |
|---|---|---|
| Sign in and setup | Reach labeled fields, review errors and complete required onboarding | Unknown; replace after checking |
| Choose a conversation | Identify the intended character and open the correct chat | Unknown; replace after checking |
| Read a reply | Find the newest reply, identify its speaker and reread it | Unknown; replace after checking |
| Compose and correct | Enter fictional text, review it and fix a word before sending | Unknown; replace after checking |
| Send and confirm | Activate Send once and establish whether the message was sent | Unknown; replace after checking |
| Follow a new reply | Locate the response without losing your place in the conversation | Unknown; replace after checking |
| Control audio, if needed | Find play, pause, microphone and end-call controls where offered | Unknown; replace after checking |
| Adjust the display | Use your preferred text size or zoom without losing essential controls | Unknown; replace after checking |
| Change a setting | Locate a setting, identify its current value and save a change | Unknown; replace after checking |
| Review payment terms | Read the plan, renewal terms and any separate voice allowance | Unknown; replace after checking |
| Find the exit routes | Locate cancellation, account deletion and support instructions separately | Unknown; replace after checking |
For each failure, write what happened rather than guessing at the cause. “The focused control was announced only as button” is more useful than “the app hates screen readers.”
If a feature is not offered, note not offered rather than inventing a result. If a paid feature cannot be evaluated without purchase, leave it unknown and ask support for specific documentation or a demonstration. You do not owe the product a subscription to complete its sales pitch.
Check conversation flow, not just the first reply
The difficult part of a companion interface is not necessarily opening it. A useful check continues through a short exchange and then returns to an earlier message.
Try reading the latest reply, moving back to your own message and returning to the composer. Note whether speaker identity and message order are understandable. Check what happens when a new reply arrives while you are reading older text: can you finish reading, or does your position change unexpectedly?
Next, correct an unsent message. If the interface offers editing, regeneration or deletion, check those controls separately; do not assume they exist. Establish which message an action will affect before activating it.
Watch for: A reply being spoken aloud can conceal an unusable conversation history. Check whether you can revisit text and reach the composer independently, not merely hear the newest output.
Stop and record a barrier if essential actions depend on guessing an unlabeled control. An accidental Send or purchase is not an acceptable way to learn what a button does.
Check keyboard access and readable text on the web
For a browser-based companion, W3C’s Easy Checks recommends checking keyboard access, logical focus order, visible focus and whether you can move away from each control. Its guidance also covers text resizing. These are useful screening ideas, not a complete audit.
With your browser configured for keyboard navigation, put the mouse aside. Use Tab and Shift+Tab to move among controls, then the appropriate activation keys for the focused element. Can you reach the composer, send control, menus and any media controls? Can you leave a dialog or player without getting trapped?
If you rely on visible focus, check that you can tell which control is selected. With your screen reader, check whether its announced name identifies the action. These are related observations, not interchangeable ones.
Use your normal enlarged-text or zoom setup and repeat the essential chat tasks. Record clipped labels, overlapping text or controls you can no longer reach. For hearing access, also check whether the information you need remains available in text when audio is off; do not assume a voice session has a transcript.
A successful keyboard check does not establish touch-screen-reader access, switch access or usable voice control. Keep each untested method unknown.
Make stopping audio a condition of using it
Before starting a voice session, locate the controls that will stop it. If you cannot identify them, do not begin the session merely to see whether an exit appears later.
Where the product offers these functions, check playback pause, microphone mute and end call separately. Confirm the resulting state through the interface rather than assuming that silence means the microphone is off. Silence, muted input and an ended session are different observations.
Then check whether your preferred reading or input method remains usable while the companion speaks. Record overlapping audio or controls that become hard to reach. Do not turn a one-session success into a claim that every call, device or future app version will behave the same way.
For your buying decision, make any essential missing stop control a reason to pause. A convincing voice is not compensation for losing control of the session.
Include billing and privacy in the decision
Before paying, find the current plan terms and identify whether the voice functions you need have a separate allowance, credit charge or add-on. This guide verifies no app-specific price or entitlement. Our token-cost explainer gives you the questions to ask; the service’s current checkout and terms must supply the answers.
Find the cancellation instructions for the purchase route you intend to use. Read them without completing a purchase. Locate account deletion separately, because deciding not to renew and requesting deletion are different tasks.
For support, send the app version, device, affected task and minimal reproduction steps. Avoid attaching intimate transcripts, passwords or verification codes. The AI companion privacy checklist covers the broader data questions.
A useful support question is: “On this device and version, how can I identify and activate the end-call control with TalkBack?” A general reassurance that accessibility matters does not answer it.
Decide from essential tasks, not a total score
There is no useful average between “I can read a reply” and “I cannot stop the microphone.” Do not add worksheet passes into an invented accessibility rating.
Choose your essential tasks first. If one fails, pause the purchase and look for a documented solution or another interface you can evaluate. If it remains unknown, say so; a marketing claim cannot fill an empty result cell. If you use a workaround, note its burden and whether you are comfortable depending on it.
After an app or operating-system update, revisit the tasks you rely on. Keep the earlier result with its date rather than silently treating it as permanent compatibility evidence.
Use the main companion-app comparison only after this screening to weigh conversation, privacy and value. Accessibility is a condition of fit, not a bonus feature to trade away for a higher overall score.
Sources & references
Official documentation checked October 23, 2026. This is a research-based buyer’s worksheet: no logged-in companion-app, VoiceOver, TalkBack, keyboard or low-vision product testing was performed. No app compatibility, accessibility certification or WCAG conformance is claimed. W3C explicitly cautions that preliminary checks can miss significant barriers.
- Apple Support: Turn on and practice VoiceOver on iPhone.
- Google Android Accessibility Help: Turn on TalkBack.
- W3C Web Accessibility Initiative: Easy Checks: A First Review of Web Accessibility.
Frequently asked questions
Which AI companion apps work with VoiceOver or TalkBack?
We have not performed device-level accessibility tests that establish a winner or a compatible-app list. Check the exact app or web version with your own screen reader, covering setup, messages, settings and billing. Voice features alone do not establish screen-reader compatibility.
Is an AI companion with voice chat automatically accessible?
No. Generated speech, speech input and accessible interface controls are separate capabilities. You still need to reach the conversation, operate the microphone and stop playback or a call using your preferred controls.
How can I check an AI companion without sharing private chats?
Use a harmless fictional conversation and record task outcomes rather than transcripts. Note the device, software versions, input method and any workaround. Do not upload intimate messages or account credentials with an accessibility support report.
Does passing this checklist prove WCAG compliance?
No. This is a buyer's screening worksheet, not a comprehensive accessibility audit or certification. W3C's Easy Checks guidance likewise warns that passing preliminary checks can leave significant barriers undiscovered.