How to Share Sensory, Communication and Accessibility Needs With an ABA Team

Share needs before the affected event

Raise access needs during inquiry, intake, scheduling, assessment, and whenever circumstances change. Use the provider's designated channel and keep a record of the request, date, person contacted, response, and follow-up.

The CDC service-access page offers general guidance about accessing services. Providers should explain their own access process.

Use concrete descriptions

Instead of “sensory issues,” explain: “The waiting room hand dryer is painful for Aria; she covers her ears and asks to leave. A quieter waiting place and warning before entering the bathroom help.”

Useful areas include:

• spoken language, interpreter, reading, and plain-language needs
• speech, sign, gesture, writing, pictures, or AAC
• vision, hearing, mobility, positioning, and service-animal access
• noise, lighting, touch, crowding, scent, and transition needs
• food, bathroom, medication, pain, fatigue, and health supports
• schedule, transportation, caregiver participation, and telehealth access

Keep AAC available

The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Tell the team about charging, positioning, vocabulary, wait time, backup methods, and partner responses.

Avoid using a child's communication system as a reward or removing it to manage behavior. If a device creates an immediate physical hazard, provide accessible backup communication while addressing the hazard.

Ask for the implementation plan

The answer should identify what support will be ready, who prepares it, where it applies, and what happens if it fails. A note that says “family prefers quiet” may be too vague for consistent action.

The CASP ABA Practice Guidelines Version 3.0 public summary places individualized assessment and treatment planning within ABA behavioral health care. This page's access checklist is an editorial family tool.

Understand the public-access boundary

For private practices that are covered public accommodations, the DOJ Title III overview discusses equal opportunity, effective communication, reasonable modifications, and physical accessibility subject to the law's standards and defenses.

An access request and a clinical recommendation answer different questions. The practice should evaluate access through the appropriate route and clinical fit through qualified clinical review.

A fictional access plan

Aria is a fictional nine-year-old who uses speech and text-based AAC. Her family requests four supports for an assessment: a quiet waiting route, written schedule, AAC access, and extra response time.

Before the visit, three are confirmed. Readiness is 3 of 4, or 75%. The waiting route remains uncertain, so the family asks for an arrival contact and waits for confirmation rather than discovering the barrier at check-in.

During the assessment, all four supports are available. Aria uses the written schedule and requests two breaks. The team honors both and asks Aria and her family whether the plan worked.

Report barriers precisely

Record the date, requested support, expected plan, observed barrier, impact, immediate action, and person contacted. Urgent safety or medical needs use the appropriate immediate route.

Ask how the provider handles complaints and who can review an unresolved access decision. Keep the focus on the missing support and next action.

Recheck as needs change

Access needs can vary by setting, partner, time, health, technology, and activity. Review the plan before a new site, staff member, community visit, telehealth session, or schedule.

Invite the child's direct feedback through their accessible communication. Family observations add context, while the child's own response remains important.

Ask for a closed-loop response

After sharing accessibility needs with an ABA team, ask the provider to repeat the request in plain language, name the owner, and state what will be ready by which date. Confirm whether the support applies to intake, assessment, treatment, caregiver meetings, telehealth, community visits, billing calls, or every relevant contact.

Test the support before a high-stakes event when possible. A video platform may need captions, an entrance may need a different route, or backup AAC may need the correct vocabulary and positioning. Record the result as ready, partly ready, blocked, or awaiting confirmation.

If the first option cannot be used, ask about another effective option and the reason for the change. Keep clinical fit, payer rules, and accessibility decisions separately attributable. A child's disability, language, communication form, or need for support should not be rewritten as poor motivation or family noncompliance.

Bring the confirmed access plan to the visit in the format the child and relevant staff can use. Afterward, ask whether the support was present, effective, and acceptable to the child, then record any adjustment and owner.

Make the access request specific to an event

Name the appointment, form, phone call, portal task, meeting, location, or service the family needs to use. Describe the barrier and the aid, service, format, policy change, or physical feature that may provide access. Include the date by which an answer is needed and the family's usable contact route.

Examples include an interpreter for a consent discussion, captioning for telehealth, an accessible entrance, large-print forms, AAC access, a lower-sensory waiting option, added processing time, or another effective communication method. Ask the organization to confirm the implementation owner and backup plan.

Keep access separate from clinical appropriateness

An access need should route to accommodation or implementation work, while a qualified clinician separately reviews the clinical service. Avoid language that turns disability, communication, language, mobility, or sensory needs into a poor-fit result. Ask which requirement is clinical and which is operational or access-related.

Some requested approaches may need discussion about effectiveness, safety, or applicable legal limits. The provider should explain the proposed solution and how it will work for the event. The family can clarify why an alternative does or does not provide effective access without having to disclose an entire history.

Track the request through implementation

Track request received, clarification, assigned owner, proposed solution, family response, implementation test, approved plan, event result, correction, and review. “We noted it” is not an implementation plan. Ask who will arrange the support, how staff will know, what happens if it is unavailable, and when the family will be updated.

Record sent, delivered, acknowledged, and reached separately. If the provider uses a channel the family cannot access, preserve that failure and request a usable route. Do not let failed communication close the request as no response.

Test the plan before the important event

For a new location, telehealth platform, interpreter, AAC setup, or alternate format, arrange a brief access check when practical. Confirm login, device, sound, captions, positioning, vocabulary, entrance, bathroom, waiting area, and staff understanding. Use dummy information for a technical test when live sensitive details are unnecessary.

Record what worked and what remains unresolved. A successful platform login does not prove that the full clinical visit, communication, or physical environment will be accessible. Keep a backup method available.

Document a fictional access request

Leila's family is fictional. Her caregiver requests an interpreter and text reminders for an assessment. The request record has eight required steps: receipt, language confirmed, interpreter assigned, clinician notified, translated arrival instructions, reminder test, event support, and family follow-up. Six are complete three days before the visit.

Readiness is 6 of 8, or 75%. The practice keeps the visit under review until the reminder test and translated arrival instructions are complete. It does not treat the interpreter assignment alone as full access. After the visit, the family reports that interpretation worked but the check-in kiosk did not, creating a separate corrective action.

Respond when an access barrier occurs

Write the date, event, requested support, observed barrier, people contacted, immediate effect, and proposed correction. Ask the provider to protect urgent health and safety, restore communication, and decide whether the event can proceed. Avoid requiring the child to complete an inaccessible activity to prove the barrier.

Use the provider's access, complaint, clinical, privacy, or safety route based on the actual issue. External legal rights depend on the organization and circumstances, so seek qualified help for a case-specific legal conclusion. Keep the practical request and next event moving while that review occurs.

Access-planning checklist

• Name the exact event and barrier.
• Request a specific support or ask the provider to propose an effective alternative.
• Confirm owner, deadline, communication route, backup, and test.
• Keep AAC and other ordinary access tools available.
• Separate access work from clinical, payer, and scheduling decisions.
• Document the event result and family feedback.
• Reopen the plan after a failed support, new setting, or changed need.

Prepare an access summary for recurring visits

Create a short, dated summary with the child's communication tools, positioning, sensory or mobility supports, interpreter or language needs, usable contact routes, event-specific modifications, backup method, and who maintains each item. Ask the family and responsible provider roles to review it.

Keep detailed medical or legal records in their restricted locations. The recurring-visit summary should tell staff what to implement, not expose an unnecessary history. Recheck it after a new site, staff member, platform, device, health change, or failed support. Retire obsolete versions so the schedule does not keep copying an old access plan.

Confirm the support on the day of service

Use a brief check before the event: support assigned, staff informed, equipment or format ready, backup available, and family reached through a usable channel. If one element is missing, name who can correct it and whether the event can proceed safely and accessibly.

Record the actual result after the visit. “Support arranged” and “support delivered effectively” are different states. Family and client feedback can reveal timing, vocabulary, positioning, privacy, or partner problems that a scheduling record cannot show. Carry those findings into the next version.