AAC & Visual Supports

AAC Implementation in Schools: Getting Started the Right Way

A practical guide to implementing AAC in schools, covering evaluation, system selection, staff training, and strategies for embedding augmentative communication across the school day.

SM
Sarah MitchellM.S., CCC-SLP
13 min

AAC Implementation in Schools: Getting Started the Right Way

If I could go back and talk to myself in my first year as a school-based SLP, I'd say this: stop thinking of AAC as a last resort and start thinking of it as a first-line intervention. I spent too long waiting for students to "be ready" for augmentative and alternative communication. They were ready. I wasn't.

Twelve years in, I've implemented AAC systems for hundreds of students across every grade level and disability category. The ones that worked shared common features. The ones that failed shared common mistakes. This guide is the distillation of what I've learned. Not theory, but practical steps you can follow starting Monday morning.

What AAC Actually Is

AAC stands for Augmentative and Alternative Communication. Augmentative means it supplements existing speech. Alternative means it replaces speech when speech isn't functional. Most students I work with fall into the augmentative category: they have some spoken language, but it's not reliable enough to meet all their communication needs across all settings.

AAC is not one thing. It's a spectrum of tools and strategies, and most students end up using multiple forms. A student might sign "more" at snack, use a communication board during circle time, and speak in two-word phrases during play. That's not inconsistency. That's a multimodal communicator using whatever works best in each moment. Our job is to give them as many tools as possible.

Types of AAC: A Practical Breakdown

Unaided AAC

These are communication methods that use only the body, with no external tools required.

Gestures are the most natural form. Pointing, reaching, nodding, shaking the head, waving. Most students already use gestures before we introduce any formal system. Pay attention to what they're already doing.

Sign language (or modified signs) can be powerful for students with good motor imitation skills. I typically teach functional signs ("more," "help," "stop," "eat," "drink," "all done") rather than full ASL. The advantage is that signs are always available. The disadvantage is that communication partners need to understand them, and most general education teachers and peers don't know sign.

Facial expressions and vocalizations count too. A student who cries when frustrated is communicating. A student who laughs during a preferred activity is communicating. Our job is to honor those existing forms while building more sophisticated ones.

Aided AAC: Low-Tech

Low-tech AAC uses external tools that don't require electricity.

Communication boards display symbols, pictures, or words that a student points to. These range from a simple two-choice board to a comprehensive core vocabulary display with 60+ cells. I've written a detailed guide on building communication boards if you want the deep dive.

PECS (Picture Exchange Communication System) is a structured protocol where students exchange picture cards to make requests. It has six phases, progressing from simple exchanges to sentence construction. PECS has strong research support, particularly for initial requesting skills in students with autism.

Communication books organize vocabulary across multiple pages, often using a system like PODD (Pragmatic Organization Dynamic Display). These are more complex than single boards but offer far more vocabulary.

Eye gaze boards are clear acrylic boards with symbols placed around the edges. The communication partner holds the board between themselves and the student, and the student looks at the symbol they want. Essential for students with significant motor impairments who can't point.

Aided AAC: High-Tech

High-tech AAC involves electronic devices with speech output.

Dedicated speech-generating devices (SGDs) like those from Tobii Dynavox, PRC-Saltillo, and Forbes AAC are purpose-built communication devices. They're durable, often have robust language systems built in, and can be funded through insurance or Medicaid. The downside is cost and the sometimes lengthy funding process.

AAC apps on tablets (TouchChat, LAMP Words for Life, Proloquo2Go, TD Snap, CoughDrop) put robust language systems on iPads or Android tablets. These are generally less expensive than dedicated devices and more familiar to students who already use tablets. The trade-off is durability and the distraction of other apps on the same device.

Lite-tech speech output devices like the GoTalk or Big Mack are simple devices with pre-recorded messages. Press a button, hear a message. These are great for students at very early communication stages or for specific contexts (a Big Mack at the lunch table that says "Can I sit here?").

The AAC Evaluation Process

A good AAC evaluation answers three questions: What can this student do right now? What do they need to be able to communicate? And what system best bridges that gap?

Step 1: Gather Information

Interview everyone who interacts with the student regularly. Parents, teachers, paraprofessionals, related service providers. Ask: How does this student communicate right now? What do they try to tell you that they can't? When are communication breakdowns most frequent? What have you tried before?

Review existing records. Previous AAC trials, IEP goals related to communication, any assistive technology evaluations recieved. I'm always surprised by how often a student has had an AAC device in the past that was abandoned, and understanding why it was abandoned prevents repeating the same mistake.

Step 2: Assess Current Communication

Document every form of communication the student currently uses. Spoken words, signs, gestures, leading, pointing, eye gaze, challenging behavior that serves a communicative function. Map these to communicative functions: requesting, rejecting, commenting, greeting, answering, asking questions.

Most students I evaluate can request effectively (even if it's through behavior) but have limited ability to comment, ask questions, or engage socially. This tells me the AAC system needs to prioritize those underserved functions, not just make requesting easier.

Step 3: Feature Matching

This is where you match the student's abilities and needs to system features. Consider:

  • Motor skills: Can the student point accurately? How large do targets need to be? Can they navigate between pages?
  • Vision: Are there visual impairments that affect symbol recognition or screen visibility?
  • Cognition: Can the student understand symbols? Combine symbols? Navigate a multi-level system?
  • Portability needs: Does the system need to travel between classrooms, to the bus, home?
  • Communication partners: Who will the student communicate with? Are those people trained in the system?

Feature matching is not about finding the "best" AAC system in general. It's about finding the best match for this specific student in their specific environments.

Step 4: Trial Period

Never commit to a system without a trial. Most device companies and app developers offer trial periods. Use them. Put the system in front of the student, model its use, and observe over 2-4 weeks. Does the student engage with it? Can they learn the motor patterns? Does it work in the noisy cafeteria and the quiet library?

I've had students who looked great with a high-tech device in my quiet therapy room but couldn't manage it in a loud, busy classroom. I've had others who seemed overwhelmed in week one but were navigating independently by week three. The trial period reveals what no amount of testing in a clinic can predict.

Choosing the Right System

There is no single best AAC system. There's the best system for a particular student at a particular point in their development. Here are the principles I use:

Start with something, not the perfect thing. A low-tech communication board implemented today is infinitely better than the perfect high-tech device that might arrive in four months after funding approval. Get communication happening now. Upgrade later.

Prioritize robustness. A robust system allows a student to say anything, not just make pre-programmed requests. Systems based on core vocabulary with the ability to combine words (like LAMP, Unity, PODD, or Proloquo2Go's Crescendo) give students generative language. Simpler systems with only pre-stored phrases hit a ceiling quickly.

Consider the long game. A student who is 5 today will be 10, 15, 25. Choose a system that can grow with them. Systems that allow vocabulary expansion without changing the motor patterns for existing words protect the student's investment in learning.

Don't let funding drive the decision. I've seen too many teams choose a system because it was easy to get funded rather than because it was the best fit. Advocate for what the student needs. Fund it afterward.

Implementation Across the School Day

This is where most AAC implementations fail. The device gets recommended, purchased, programmed, and then it sits on a shelf because nobody embedded it into the student's actual day. Here's how to prevent that.

Create an AAC Implementation Matrix

List every activity in the student's day down one side. List communication functions across the top (request, reject, comment, greet, answer, ask, direct). For each cell, identify specific vocabulary the student can use and how they'll access it. This matrix becomes the blueprint for every adult who works with the student.

Embed AAC Into Routines, Not Just Therapy

AAC use should happen during morning meeting, reading, math, snack, recess, lunch, specials, and dismissal, not just during the 30 minutes of speech therapy per week. I structure it this way: I model and teach new vocabulary during therapy, then I support the classroom team in creating opportunities for the student to use that vocabulary all day.

Create Communication Opportunities

Don't just wait for the student to use their system. Engineer situations where communication is necessary and motivating. Hold up two snack options and wait. Start a preferred activity and then pause. Give the student the wrong item on purpose. These are contrived moments, yes, but they're the practice reps that build fluency.

Designate an AAC Champion

Every classroom needs one person (teacher, para, or therapist) who is responsible for making sure the AAC system is charged, available, and being used. Without a designated champion, the system gradually migrates from the student's desk to a shelf to a cabinet to a closet.

Model AAC before expecting the student to use it. This is the single most important implementation strategy, and it's the one teams skip most often. Aided language input (also called modeling or aided language stimulation) means pointing to symbols on the student's system while you speak. When you say "Do you want more?" you simultaneously point to "want" and "more" on the board. Research consistently shows that students need to see AAC modeled by competent communicators before they'll use it independently. Plan for at least 8-12 weeks of consistent modeling before expecting spontaneous use. I tell teams: if the student isn't using their system yet, the first question isn't "Is this the right system?" It's "Are we modeling enough?"

Training Staff and Families

An AAC system is only as good as the people around the student who know how to support it.

Staff Training Essentials

Every adult who interacts with the student needs to know:

  1. What the system is and where it lives. Sounds basic. You'd be amazed how often a substitute teacher or a new para has no idea the student has a communication device.
  2. How to make it available. Turn it on, open the right app, position it within reach.
  3. How to model. Point to symbols while speaking naturally. Not "now touch 'want.'" Just use it as you talk.
  4. How to respond. When the student uses the system, respond as you would to speech. If they press "bathroom," say "You need to go to the bathroom? Let's go." Don't quiz them or make them repeat it.
  5. How to troubleshoot. Battery dies, the app crashes, the board gets wet. Have a backup plan and make sure everyone knows it.

I run a 30-minute training for classroom teams at the start of each implementation. Then I do weekly check-ins for the first month, biweekly for the next two months, and monthly after that. The check-ins aren't optional. Without them, implementation fidelity drops off a cliff by week four.

Family Training

Families need the same information as staff, plus: how to use the system at home, how to program new vocabulary for home contexts, and how to set up communication opportunities during family routines (meals, bath time, bedtime, car rides, grocery shopping).

I always ask families what they most wish their child could tell them. That answer drives the home vocabulary programming. One family said "I just want to know if he had a good day at school." We programmed "good day" and "bad day" and "tell you about school" that afternoon.

Common Myths, Debunked

"AAC will prevent my student from learning to talk." The opposite is true. Over 25 years of research shows that AAC either has no effect on speech development or actually increases verbal output. A meta-analysis by Millar, Light, and Schlosser (2006) found that AAC intervention was associated with gains in speech production in the majority of participants studied.

"The student isn't ready for AAC." There are no prerequisite skills for AAC. A student doesn't need to demonstrate cognitive prerequisites, sit still for a certain duration, or show "intentional communication" before getting access. If a student has unmet communication needs, they're ready.

"We should try everything else first." AAC is not the last resort after sign language failed and PECS didn't work and verbal imitation therapy stalled. It should be introduced alongside those approaches. A multimodal approach (speech, sign, low-tech, high-tech) gives the student the best chance.

"It's too complicated for our staff." Then simplify the system or improve the training. The answer to "staff can't implement this" is never "take away the student's communication tool." It's "support the staff better."

Measuring Progress

AAC implementation is not a "set it and forget it" intervention. Track:

  • Frequency of use: How often is the student using the system per day? This should increase over time.
  • Variety of functions: Is the student only requesting, or are they also commenting, rejecting, greeting, and asking?
  • Vocabulary growth: How many words/symbols is the student using meaningfully?
  • Communication partner response: Are adults responding to AAC use as communication? Are peers engaging?
  • Independence: Is the student initiating communication without prompts, or only using the system when directed?

I track these monthly and adjust the implementation plan based on the data. If frequency isn't increasing after 8 weeks, I look at whether the system is available, whether adults are modeling, and whether the vocabulary matches the student's needs. Usually the issue is one of those three things, not the system itself.

Key Principles for Successful AAC Implementation

Start now, not later. Every day without functional communication is a day of frustration, missed learning, and missed connection. Low-tech options can be implemented today while you pursue higher-tech solutions.

Model first, expect second. Consistent aided language input by every adult in the student's life is the foundation of AAC learning. Budget 8-12 weeks of heavy modeling before evaluating whether the student is "using" the system.

Train the team, not just the student. The most common reason AAC fails is not the student or the system; it's lack of implementation fidelity by the adults. Invest in staff and family training as aggressively as you invest in programming vocabulary.

Make AAC available everywhere. Communication is not a subject that happens during speech therapy. The system needs to be present and accessible during every activity, in every setting, every day.

Be multimodal. Most successful communicators use a mix of speech, gestures, low-tech, and high-tech. Don't limit a student to one mode. Give them options and let them use whatever works best in each moment.

Review and adjust regularly. AAC implementation is iterative. Collect data, listen to the team, observe the student, and adjust. The system that's perfect in September may need significant changes by December. That's not failure; that's responsive practice.

AAC implementation in schools is not easy. It requires coordination, training, patience, and a willingness to keep adjusting. But when it works, when a student who has been silent or frustrated suddenly has a way to say "I want that," "Stop," "That's funny," "I love you," it is the most rewarding work in this field. Every student deserves a voice. Our job is to make sure they get one.