Choice, Communication, Privacy, and Technology Support

To build choice communication privacy and shared support into technology use, give Yael accessible ways to express choose, send, share, audience, private, suspicious, block, report, help, recover, wrong person, stop, and emergency. Define the partner response for each message. Protect AAC, authorship, consent, assent, refusal, credentials, account and content privacy, location, payment, and supporter boundaries. Record Yael's words and decisions separately from anything another person drafted, clicked, approved, or accessed.

Define the shared-support decision

To build choice communication privacy and shared support into technology use, define the person, purpose, device, account, content, audience, authority, access, authentication, privacy, security, supporter, release condition, stop rule, recovery route, and control-return condition. Support may include reading, explaining, positioning a device, or operating an agreed access control. Yael's message, consent, audience choice, discomfort, and incident report remain Yael's.

Protect communication, secrets, and ownership

Yael's support plan keeps AAC, device access, emergency help, private content, credentials, recovery secrets, identity data, and funds protected under the authorized arrangement. Yael's technology choice and communication plan cannot create account ownership, identity, platform permission, financial authority, cybersecurity, legal consent, or permission to inspect private content.

Build a technology choice and communication plan

Create one versioned record for the home, school, work, and community devices. Include Yael's purposes, emergencies, devices, accounts, content, audiences, ownership, authentication, access, communication, privacy, payments, supporters, restrictions, incidents, recovery, outcomes, missingness, and reassessment evidence. Use a message-by-supporter table with form, meaning, digital context, audience, expected response, window, privacy, authorized people, backup, observation, and repair.

Validate the counts and evidence

Reproduce 29 decisions, 25 with communication, 17 messages, 14 timely responses, two late responses, and one missed response.

Turn the evidence into a bounded action

The team repairs four access failures and three response failures. It records which device, account, content, contact, payment, and recovery actions each supporter may perform.

Work through a shared-support example

Across 29 planned digital decisions, Yael has the agreed communication or backup in 25. Yael sends 17 messages. Partners respond within the agreed window to 14; two are late and one is missed. Four communication failures remain system gaps. Preserve every planned and eligible unit, device and account version, authority, access, authentication, content and audience, communication, person choice, response, restriction, incident, recovery, repair, and endpoint. This fictional example supplies no account ownership, platform decision, identity determination, security assurance, treatment effect, compliance result, or promised outcome.

Avoid overreading response timing

Fourteen of 17 measures timely partner response within the agreed window. It cannot establish consent, authorship, account authority, security, safe content, independence, satisfaction, or intervention effect. Review immediate danger, account and platform rules, ownership, authentication, accessibility, privacy, security, financial boundaries, communication, supporter response, instruction, restrictions, person priorities, incidents, burden, missingness, and design strength separately.

Set ABA scope and ethics boundaries

Yael's technology choice and communication plan uses the CASP public summary only for high-level ABA behavioral-health-treatment scope for autistic people. The current BACB Ethics Code addresses competence, collaboration, consent and assent when applicable, confidentiality, assessment, risk, documentation, and evaluation for covered people. Device, account, platform, identity, cybersecurity, financial, emergency, safeguarding, employment, and legal authority remain with qualified owners.

Apply CISA's four practices to real accounts

CISA Secure Our World emphasizes recognizing and reporting phishing, strong passwords and password managers, multifactor authentication, and prompt software updates. These are general security practices, not permission to access Yael's account, hold credentials, choose an authenticator, or override accessibility. The technology choice and communication plan records which current service supports each control and who owns it.

Route suspicious messages through verified channels

The FTC phishing guide explains that deceptive emails and texts may seek passwords, account numbers, or other information. It advises contacting the company through a number or site already known to be real instead of using the message link. Yael's team may teach that bounded check with synthetic messages while leaving incident response, account action, and money decisions to authorized roles.

Use IdentityTheft.gov only after the right classification

IdentityTheft.gov recovery steps provide an FTC reporting and recovery route for U.S. identity theft, including contact with affected companies and credential changes. That route does not classify every suspicious message or authorize clinical staff to freeze accounts, access credit reports, file as Yael, or control funds. Preserve the person's authority and the qualified recovery owner.

Apply NIST digital-identity terms cautiously

Final NIST SP 800-63 Revision 4, released in July 2025, covers digital identity proofing, authentication, and federation for government information systems. It is a technical reference, not a universal consumer-account rule or clinical protocol. Yael's actual platform determines supported authenticators and recovery methods; account ownership, accessibility, risk, and delegated help remain separate decisions.

Treat cognitive accessibility as design evidence

The W3C cognitive-accessibility page distinguishes WCAG standards from supplemental informative guidance and describes needs involving perception, memory, language, attention, comprehension, and error correction. It cannot diagnose Yael, authorize account access, or guarantee usability. Testing for Yael uses the real interface, assistive technology, authentication, timing, and recovery path with the person.

Keep emergency action ahead of digital data

The National 911 Program says an emergency requiring immediate police, fire, or ambulance assistance belongs with 911 and that call-takers may provide instructions. Local systems differ, and the guidance is U.S.-specific. Yael's team follows qualified responders rather than completing a teaching trial, screenshot, percentage, or routine approval first.

Make digital communication accessible

The DOJ effective-communication guidance explains that covered entities consider the nature, length, complexity, context, and person's usual communication method. Platforms and account owners can have separate duties. Communication checks in Yael's technology choice and communication plan cover instructions, authentication, messages, warnings, reports, and recovery explanations while sending provider-access decisions to the responsible entity.

Preserve AAC and authorship

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Yael's primary and tested backup communication remain available during login, messaging, support, recovery, compromise, and emergencies. A supporter may facilitate access without supplying Yael's message, consent, audience, account answer, payment choice, or incident report.

Use technology evidence cautiously

A systematic review of assistive technology for practical skills included 18 studies involving autistic people or people with intellectual disabilities across varied targets and tools. It cannot establish that an app, reminder, password manager, passkey, filter, tracker, communication device, or recovery aid will teach Yael's skill, prevent compromise, generalize, or improve wellbeing.

Choose the next review trigger

Review after a device, account, communication mode, supporter, audience, credential, location feature, restriction, incident, or Yael preference changes. Record the qualified owner, current source, effective date, device and account version, ownership and access state, authentication and recovery arrangement, communication, intervention and restriction authority, implementation check, accessible explanation, complaint route, and reassessment date.

Close the personal-technology plan

Review the technology choice and communication plan with Yael, the qualified behavior analyst, authorized supporter when applicable, direct team, and specialists named in the manifest. Confirm that emergencies, account and platform decisions, identity, authentication, accessibility, privacy, cybersecurity, communication, assessment, teaching, restrictions, incidents, recovery, and outcomes remain separate; every denominator is reproducible; AAC, authorship, refusal, withdrawal, private content, secrets, funds, and emergency help remain protected; and conclusions stay bounded to sampled conditions. Keep this page draft and noindex until every required review is complete.

How to Build Choice, Communication, Privacy, and Shared Support Into Technology Use