Passwords, PINs and security codes can be unusually demanding for a person with aphasia. The problem is not necessarily understanding what an account is for. The difficulty may be reading a dense login screen, remembering a sequence long enough to type it, switching between an app and a text message, or explaining a problem to support when the account is locked.
A useful goal is not to remove security. It is to reduce the language and memory load around security so the person with aphasia can keep as much control as possible. A good setup makes the correct action easier to recognise, creates a reliable recovery path, and avoids sharing passwords unnecessarily.
Why secure logins can be harder with aphasia
Aphasia can affect reading, writing, speaking and understanding in different combinations. One person may read a six-digit code accurately but struggle to copy it before it disappears. Another may recognise familiar words but find a long password impossible to type. Fatigue can make a system that works in the morning much harder later in the day.
Numbers can also be difficult even when everyday conversation is relatively strong. If this is a recurring issue, the strategies in Numbers and Aphasia: Practical Strategies for Money, Dates, Phone Numbers and Medication Labels can help with PINs, verification codes and account numbers.
Start with the easiest secure sign-in method the service supports
Many accounts now offer more than one way to sign in. Depending on the device and service, a person may be able to use a fingerprint, Face ID, a passkey, a password manager, an authenticator app or a traditional password. The best option is the one that is both secure and realistically usable by that person.
- Biometric sign-in: can remove repeated typing, but the person still needs a recovery method.
- Password manager: can fill long unique passwords without requiring them to be memorised.
- Passkeys: can reduce dependence on typed passwords when supported by the account and device.
- Authenticator app: can be safer than SMS for some accounts, but switching apps and copying codes may be difficult.
- SMS code: may be familiar, but the short time limit and number copying can be challenging.
Do not change every account on the same day. Start with one low-risk account, practise the sequence, and only then repeat the system elsewhere.
Create a login routine that uses the same visual order every time
A predictable routine reduces the need to solve the whole screen from scratch. For example: open the account from the same bookmark, tap the same sign-in button, use the saved password, then complete the second step. If a caregiver is helping, use short prompts rather than taking the device and finishing the task automatically.
Helpful prompts can be concrete: “Find the blue Sign In button,” “Now look for the six numbers,” or “The code is in Messages.” Give enough time for the person to complete each step before adding more language.
Make two-factor authentication easier to manage
Two-factor authentication adds a second proof that the person signing in really controls the account. The extra step is valuable, but it can create a barrier when the code arrives somewhere else.
Practical adjustments include:
- using a device with a larger text size;
- keeping the Messages or authenticator app in a predictable place on the Home Screen;
- using split-screen or nearby devices when that makes copying easier;
- turning off unnecessary notifications so the security message is easier to see;
- writing a simple one-page sequence such as “1. Open bank. 2. Tap Sign In. 3. Open Messages. 4. Read six numbers. 5. Return to bank.”
If account verification already causes difficulty on the phone, see Using Customer Service With Aphasia for ways to prepare for identity questions, phone trees and escalation.
What should be written down — and what should not?
A person with aphasia may benefit from written cues, but a cue does not need to contain the full password. A safer support sheet might identify the correct account, the sign-in method, where the second code appears, and the recovery contact. It can also use screenshots with arrows showing which button to press.
Avoid keeping a visible list that pairs account names with complete passwords and PINs. If passwords must be stored, a reputable password manager is usually a better system than notes left on a desk, in a wallet or beside the computer.
Build a recovery plan before an account is locked
Recovery is often harder than normal login because the screens contain more text and unfamiliar choices. Set up recovery options while the account is working normally.
| Recovery item | Why it matters | What to check |
|---|---|---|
| Recovery email | Receives reset links and alerts | Is it still accessible? |
| Recovery phone | Receives verification codes | Is the number current? |
| Trusted device | May approve a new login | Can the person recognise and use it? |
| Backup codes | Can restore access if the phone is unavailable | Are they stored securely and labelled clearly? |
| Support contact | Helps when automated recovery fails | Is there a written script for asking for help? |
How can a caregiver help without taking over the account?
Support should match the person’s actual communication needs. It may be enough to read a difficult sentence aloud, point to two options, slow the process down or write down a code while the person enters it. The person with aphasia should still be included in decisions about who can access the account and what information can be shared.
For financial accounts in particular, avoid informal arrangements where another person simply learns every password. If ongoing help is needed, ask the bank or service about formal authorised access, trusted contacts or other supported arrangements. The broader principles in Money and Numbers With Aphasia can help families separate communication support from financial decision-making.
Use short written messages when support asks complicated questions
Live chat and email can sometimes be easier than a fast phone call because the person has more time to read and respond. Prepare a short message that explains the communication need without disclosing unnecessary medical details. For example, the person can state that they have aphasia, need one question at a time and may need extra time to type.
Templates, dictation and proofreading strategies are covered in Writing Emails and Text Messages With Aphasia.
Watch for scams that exploit confusion around security codes
A verification code should be treated as sensitive. A caller who creates urgency and asks for a one-time code may be trying to take over an account. When a message or call is unexpected, stop and open the official app or website independently instead of following a link or calling a number supplied in the suspicious message.
A simple household rule can help: unexpected request + urgency + code = stop and verify. This rule is easier to remember than a long list of scam types.
A practical setup checklist
- Choose one primary device for important accounts.
- Increase text size and simplify the Home Screen if needed.
- Use unique passwords stored in a password manager where possible.
- Enable the easiest secure second factor the person can use reliably.
- Update recovery email and phone details.
- Create a short visual login guide without writing the full password.
- Practise recovery on a low-risk account before an emergency.
- Agree how a family member or caregiver will help while preserving the person’s choices.
Frequently asked questions
Is it safe to turn off two-factor authentication because aphasia makes it difficult?
Usually the better approach is to change the method rather than remove the protection. Biometrics, passkeys, trusted devices or a more accessible authenticator setup may reduce the burden.
Can a caregiver keep the person’s password?
That depends on the account, the person’s wishes and any formal authority the caregiver has. For important financial or health accounts, formal delegated-access options are preferable to casually sharing credentials.
What if the person can read words but keeps mixing up numbers?
Use larger spacing, group digits, read one pair at a time and allow extra time. A second device or written scratch card can reduce the memory load when moving a code from one app to another.
What if login works on good days but not when the person is tired?
Build the system for the harder days: fewer steps, saved credentials, predictable visual cues and a documented recovery process. Fatigue can change communication performance, so consistency is valuable.