In this guide
Ask what will be spokenConsider the wider interactionKeep explanations non-secretUse practical communication preferencesReview after a meaningful changeA screen can be private to the person using it while its spoken output reaches everyone in the room. An audio setting, support call or recording can change the audience for an account value. Plan the interaction so accessibility remains usable and unnecessary secrets are not announced.
Google TV documents TalkBack configuration including spoken-password settings. Other platforms and apps can behave differently, so use the actual first-party guidance.
Ask what will be spoken
Profile labels, field values and confirmation messages can have different privacy implications. A non-secret local nickname is usually less revealing than a complete connection address. Do not assume that a password field behaves identically in every app. Review the relevant accessibility settings and the user’s preferred way to complete the task.
Consider the wider interaction
A remote helper may receive audio as well as a screen view. A screen recording can preserve a spoken value after the session ends. A visitor may be close enough to hear a code. These are reasons to choose an appropriate supported entry method, not reasons to disable the user’s assistive technology indiscriminately. The person should retain usable control of the account task.
Keep explanations non-secret
A helper can say which field is being requested and what action the official prompt describes without repeating the actual password or recovery code. The owner can complete the protected step. If a spoken value was disclosed to an unintended audience, identify which account and type of secret were affected and use that provider’s legitimate security process.
Use practical communication preferences
A case note can state that the customer prefers written steps during credential entry or a particular supported assistive method. It need not include a diagnosis. Keep the preference purposeful and current. If the platform lacks a suitable option, ask its developer for an official alternative rather than improvising a bypass or asking another person to take broad account control.
Review after a meaningful change
A new app or device may not inherit the earlier speech settings. Recheck the relevant boundary using ordinary authorised operation. Record what was reviewed without claiming a universal privacy guarantee. The useful outcome is an account owner who can complete the task through a supported accessible method with an understood audience for the information involved.
Before recording a support walkthrough, agree which part of the task actually needs recording. Pause or avoid capturing protected entry through the tool’s supported controls where appropriate. A non-secret written summary may be sufficient. Keep any retained recording under suitable access and do not claim that removing the local clip invalidates a secret that was already disclosed.
Questions about this guide
Is using a headset always sufficient?
It may help in a supported setup, but the actual device, audio routing and user needs determine the result. Follow the platform’s documentation and check the intended output. Do not claim privacy from an accessory alone without understanding what the session or recording can capture.