Can AAC and Visual Supports Stay During Generalization Checks?

Supports during ABA generalization

For each probe, record the ordinary supports available, teaching prompts permitted, prompt actually used, client response, partner response, setting, and outcome. Test changes to a support only when the change serves the person's goal and the responsible clinician has planned it with applicable consent and assent.

Ordinary supports make participation possible or practical. Teaching prompts are added to evoke or guide a target response during instruction. The same item can serve different functions in different plans, so the team should define its role rather than assuming every visible aid reduces independence.

Separate access from instructional help

Examples of ordinary access can include:

• a person's AAC system and agreed backup
• glasses, hearing technology, mobility tools, or positioning supports
• a visual schedule, calendar, written checklist, or map normally used in daily life
• sensory supports, environmental modifications, or additional processing time
• language access or an interpreter when applicable

Teaching prompts may include an added model, gesture, verbal cue, physical guidance, or step-by-step coaching used to teach the response. Report the prompt level separately. A response completed with AAC and no added teaching prompt can still be independent under a well-defined goal.

Define the conclusion carefully

Removing access can change the task rather than test transfer. A person who communicates independently with AAC may become unable to respond when the device is removed. Report the skill with AAC available. If backup access is a meaningful goal, teach and measure that goal separately.

Define independence around the real outcome

Ask what the person is expected to do in ordinary life. An adult who uses a checklist to pack for work may be independently managing the routine. A child who uses AAC to ask an unfamiliar partner for help may be communicating independently. The goal can define initiation, timing, choice, and partner response while retaining the tool.

If the team wants to reduce an instructional prompt, name the prompt and the fading plan. Do not place AAC, mobility, prescribed health care, or another essential support on the prompt hierarchy merely because staff can remove it.

Plan backup access without sabotaging the probe

Backup communication, charging, positioning, and partner training can be legitimate goals. Teach them directly. A provider should not disable the primary tool to see whether the client can cope. Use planned, safe practice and the person's agreement, then measure the backup response under defined conditions.

When the primary tool unexpectedly fails, record the system failure, backup availability, client communication, and response. That incident is different from a scheduled generalization probe.

Use current clinical and measurement sources

The CASP public summary places assessment, planning, implementation, and evaluation within its autism-treatment scope. The BACB Ethics Code addresses client involvement, consent and assent when applicable, assessment-based intervention, risk, documentation, and evaluation for covered behavior analysts.

The BCBA Test Content Outline covers programming for generalization and maintenance as examination content. It does not create a universal probe count, maintenance interval, independence definition, or authority to practice.

Use the historical framework with current judgment

Stokes and Baer organized generalization-programming tactics in a 1977 conceptual paper. It remains historically influential, while current clinical use still requires individualized goals, evidence, supports, client choice, and review.

Keep ordinary access supports available

The ASHA AAC portal supports continuous communication-tool access. AAC, visual schedules, mobility supports, and other ordinary access tools can remain part of independent daily participation when they fit the person and goal.

Partners need preparation too. A new setting cannot show useful communication if the person receiving the message does not recognize the AAC output or wait for completion. Record whether the partner had the necessary instruction and whether the message was honored.

A practical example

Noor uses an AAC device and visual route card at school. The goal is to ask for directions in selected community settings with both tools available and without added teaching prompts. Across four probes, Noor asks in three. One partner responds before Noor completes the message, so partner response is 2 of 3 messages.

The team reports 3 of 4 independent responses with ordinary supports, one no-response opportunity, and the partner result. It does not describe the device or route card as prompts. Noor selects a quieter library information desk for the next probe, and staff prepare the partner to wait for the message.

A separate backup-access plan teaches Noor how to use a low-tech board when the device is charging. That work has its own opportunities and measures. The team does not remove the working device during generalization checks.

Questions for the plan meeting

Ask the team to label each support as ordinary access, environmental support, teaching prompt, or backup tool. Then ask who chose it, whether it stays available in daily life, how partner behavior is measured, and what evidence would justify any change.

Test a support change only for a meaningful reason

Sometimes a client wants a smaller checklist, a different device layout, or a backup that works during travel. The clinician can plan that change with the person, define the expected benefit, preserve a safe fallback, and compare each version. A support change should serve access or the client's goal rather than make a probe appear harder.

Record the support version, date, setting, client choice, opportunities, response, burden, and partner action. If several features change together, describe the package. A better result can support continued use without proving which feature caused it.

Keep support failures in the system record

A device with no charge, a visual stored out of reach, or a mobility route blocked by furniture changes the opportunity. Record who was responsible for readiness and what repair occurred. Do not exclude every failed setup after seeing the result.

Use separate measures when helpful: sessions with required support ready divided by sessions due for readiness review, and client responses divided by valid opportunities once the support is available. This keeps operational access and client performance distinct.

Prepare unfamiliar partners

Generalization may fail because the new partner does not recognize the response. Give partners the smallest necessary instruction about waiting, acknowledging the message, and providing the agreed outcome. Protect privacy and avoid asking the client to demonstrate private information for training. A partner can practice with fictional examples before the live interaction.

Questions families can use

Ask which supports belong in daily life, which are instructional prompts, whether any support was removed, how independence is defined, what the client prefers, and whether backup access has its own plan.