How ABA May Support Using Email

Define the email purpose

Use a real task such as asking a question, confirming a plan, sending an approved file, or following up. State what the recipient needs, what response is expected, and which information should stay out of email.

Build an accessible compose-and-review flow

Offer speech-to-text, AAC, keyboard access, templates, contact favorites, readable layout, and a recipient check. Review subject, body, attachment, audience, tone only where relevant, and whether reply-all or forwarding would expose others.

Add a suspicious-message route

FTC explains that phishing messages may seek passwords, account numbers, or other sensitive information and may use links or attachments. Its phishing guidance recommends using known contact information rather than the message's route when verifying.

Protect privacy and authority

The Ethics Code addresses understandable communication, confidentiality, client involvement, and documentation for covered analysts. ASHA supports AAC access. A draft or template does not authorize the disclosure.

A practical example

Maya completes six approved emails. Recipient, purpose, privacy check, and accessible compose tools are ready in 5/6. Maya sends 4/5 and saves one draft for review. The missing authorized address remains a setup hold.

Questions families can use

Who owns the account? What is the purpose? Is the recipient verified? Which information and attachment are permitted? Can the person save, revise, or stop? What trusted route checks an unexpected message?