How ABA May Support Managing Software and Device Updates

Classify the device and owner

Record who owns and manages the device, what essential functions it supports, whether it contains private information, and which organization, vendor, clinician, school, employer, or communication specialist controls updates or compatibility.

Verify the update and timing

Use the device's trusted settings, vendor site, or administrator route. Check power, network, storage, expected downtime, release source, backup, authentication, support availability, and whether travel, work, care, or communication makes another time safer.

Protect essential access

For an AAC or safety-critical device, confirm a tested backup communication or function before starting. Save approved vocabulary, settings, files, and access configuration through the responsible process. Never experiment with a needed device during an unsupported period.

Use current security guidance

CISA's Secure Our World lists software updates among four core actions because updates address security flaws. It also recommends phishing awareness, strong passwords, and MFA. ASHA supports continuous AAC access.

A practical example

Tobin reviews six devices. Owner, trusted update source, backup, power, and recovery contact are ready for five. Four update and pass access checks; one fails a display setting and remains open until restored.

Questions families can use

Who owns and manages the device? Is the update source trusted? What essential function could stop? Is backup tested? Who performs recovery? Which access checks must pass before the update is complete?