How to Build an AAC Access Appendix for an ABA Plan

An AAC access appendix for an ABA plan documents how the person communicates and how partners keep that communication available across plan activities. Record systems, positioning, access method, charging, vocabulary, backups, wait time, reliable messages, partner responses, repairs, privacy, and emergency communication. Build it with the AAC user and relevant communication professionals. The appendix supports access; it should never make device use, speech, eye contact, or one motor response a prerequisite for being heard.

Inventory communication forms

Record speech, signs, gestures, movement, writing, symbols, low-tech and high-tech AAC, partner interpretation boundaries, current vocabulary, and how Owen corrects a misunderstanding.

Build the inventory with Owen and the relevant communication professional rather than treating one device as his entire communication system. Describe which forms are reliable in different contexts and which partner interpretations require confirmation. Include unfamiliar or emerging messages without converting them prematurely into fixed meanings. Owen should have an accessible way to reject a partner's interpretation and offer another response.

Specify physical and technical access

Document positioning, mounting, motor access, sensory needs, device, app and version, voice, connectivity, charging, transport, passwords, updates, repair, and approved data practices.

Assign an owner for setup in every setting and test access from arrival through storage and return. Keep credentials and personal data within approved privacy and security routes while ensuring authorized partners can restore communication promptly. A charged device can still be inaccessible because of mounting, motor, sensory, vocabulary, or connectivity conditions. Record those states separately and route assessment questions to the qualified communication professional.

Define reliable messages

Include yes, no, stop, break, help, pain, discomfort, choice, refusal, emergency, privacy, correction, and context-specific messages with recognizable forms and partner response.

Describe what partners do after each message, including honoring refusal, obtaining urgent help, or confirming an ambiguous selection. Do not require speech, eye contact, or a single motor pattern for the message to count. Test these routes in ordinary and stressful contexts without deliberately creating distress. If a critical message is missing or slow to find, provide a usable backup and repair the system before the affected procedure proceeds.

Plan backup communication

Use an agreed backup available whenever the primary system is unavailable. State vocabulary, location, owner, testing, transition, and how partners avoid narrowing the person's options.

The backup should support more than basic compliance or emergency responses. Include choice, refusal, pain, privacy, correction, and the topics Owen needs in daily life. Keep it physically available and familiar to partners, and test the switch without waiting for an outage. Document when the primary system becomes unavailable, which backup was used, what communication was lost, and how repair status is shared.

Train communication partners

Teach access setup, wait time, aided language or other assigned support, message recognition, honoring refusal, repair, privacy, and escalation without taking authorship of the message.

Use demonstration and observation across the settings where partners will support Owen. Training should include an unrecognized message, device failure, request to stop, and need for private communication. Record competency separately from attendance and identify limits of each role. Repeated misunderstanding may indicate a partner-training, access, vocabulary, or plan-design problem and should trigger qualified review rather than being attributed automatically to Owen.

Measure system readiness

Report sessions with primary or agreed backup ready among all sessions involving the AAC user, plus message opportunities, partner response, outages, repair time, and the user's experience.

Keep the full session denominator visible, including sessions where no device was present or readiness could not be verified. Report critical-message access separately so a strong average does not hide a failed pain or stop route. Ask Owen about effort, privacy, usefulness, and preferred changes. Link outages and repair times to owners and verify the restored system in the setting where the failure occurred.

Build Owen's AAC access appendix

Owen's "AAC access appendix ABA plan" record begins with Owen's communication methods and instructions rather than a device inventory alone. It links the controlling plan to primary and backup systems, individualized signals, vocabulary, positioning, charging, transport, network and offline needs, partner response, repair, privacy, setting-specific owners, availability checks, outages, corrections, review dates, and unresolved limits. A reviewer should be able to reproduce each readiness check and confirm that the appendix protects communication across settings.

Work through Owen's example

Owen uses a tablet, a laminated core board, and two individualized gestures. Across nine observed sessions, the primary system is ready in seven, the agreed backup is ready in one, and neither is ready in one. Primary or backup access is therefore available in eight of nine sessions, or 88.9 percent after rounding. The inaccessible session remains in the denominator and opens a charging and handoff repair. This fictional home, school, and community example sets no universal format, clinical recommendation, legal conclusion, pass threshold, or outcome guarantee.

Address Owen's main access risk

A device list alone can miss positioning, vocabulary, partner timing, or the person's non-device messages. Owen's appendix covers the complete communication interaction. Test whether communication works in both directions and whether the complete clinical meaning survives the format. Technical availability, readability, understanding, agreement, training, competence, and correct implementation remain separate outcomes.

Choose Owen's next action

The team repairs the charging handoff, validates the backup with Owen, and checks access across people, settings, transitions, distress, and emergencies. Record the responsible role, authority, affected users and scope, interim accessible option, due date, correction evidence, communication, retest, version effect, and next review. Software may render and distribute content. Qualified clinicians retain responsibility for clinical meaning within scope.

Protect Owen's communication and privacy

Keep Owen's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Use approved systems and purpose-needed access. Offer a private way to ask, decline, pause, withdraw when applicable, report discomfort, and correct the record without making one response form the price of participation.

Apply current sources to Owen's access review

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, evaluation, and training context.

An evidence-based ABA framework and treatment-integrity practitioner guide, Essig review, impact study, and reporting review support contextual decisions, explicit procedures, implementation evidence, and bounded conclusions.

ASHA supports continuous AAC access. DOJ effective-communication guidance addresses covered Title II and Title III entities, while HHS language-access guidance addresses applicable HHS-funded programs and OCR authorities. Verify entity and rule scope.

Rehearse Owen's usability workflow

Test the AAC access appendix with a client request, visual impairment, hearing or speech disability, AAC outage, preferred language, low literacy, interpreter need, screen reader, magnification, phone, print, weak connection, EHR outage, stale cache, inaccessible table, missing stop rule, privacy limit, plan correction, and emergency. Confirm that effective communication, clinical meaning, safe action, version control, and follow-up remain intact.

Close Owen's access review

Review the AAC access appendix with Owen, the responsible clinician, representative users, and the specialists named by the manifest. Preserve source content, language and format choices, direct client input, tests, defects, corrections, limits, and open findings. Keep the page draft and noindex until required clinical, client or family, AAC, disability-access, language-access, interpreter, privacy, security, software, payer, and legal reviews are complete.