If you could only practice AAC in one situation, make it mealtimes.
Mealtimes happen two to three times a day, every day. They're naturally motivating (the child wants the food). They're repetitive (the same words come up at every meal). And they have built-in consequences for communication ("I pressed 'more' and I got more crackers").
That combination of frequency, motivation, and repetition makes mealtimes the single best opportunity to build AAC skills. Here's exactly how to do it.
Why Mealtimes Work So Well for AAC
Most AAC practice opportunities are engineered. You set up a game, create a communication temptation, and hope the child is motivated enough to participate. Mealtimes are different. The motivation is already there.
A hungry child has a reason to communicate. They want something, and you have it. That natural motivation is more powerful than any contrived activity a therapist or parent can design.
Mealtimes also have a predictable structure. The routine is roughly the same each time: sit down, choose food, eat, ask for more, finish. That predictability helps children learn because the same words show up in the same context over and over. Repetition in context is how all language is learned.
Vocabulary to Prepare
Before your first AAC mealtime, make sure these words are accessible on the device. They cover the core communication functions that happen at every meal.
Essential mealtime words
| Word | Function | When to use it |
|---|---|---|
| want | Requesting | "I want crackers" |
| more | Requesting | "More milk please" |
| all done | Finishing | "All done eating" |
| eat | Action | "Time to eat" |
| drink | Action | "I want to drink" |
| yummy | Commenting | "Yummy banana" |
| yucky | Protesting | "Yucky, I don't want that" |
| help | Requesting | "Help me open it" |
| open | Action | "Open the yogurt" |
| hot | Describing | "Careful, it's hot" |
Nice-to-have words
| Word | Function | When to use it |
|---|---|---|
| cold | Describing | "Milk is cold" |
| please | Social | Polite requesting |
| my turn | Social | Serving themselves |
| pour | Action | "Pour the juice" |
| cut | Action | "Cut my food" |
| different | Choosing | "I want something different" |
| no | Protesting | Rejecting an offered food |
Don't worry about having every food noun programmed. Core words like "want," "more," "that," and "different" combined with pointing are more flexible than individual food pictures. A child who can say "want that" while pointing at the cheese is communicating just as effectively as one who presses a "cheese" button.
Step-by-Step: Breakfast
Breakfast is often the calmest meal. The house is quiet, the routine is predictable, and you're not rushing between activities. This makes it the best meal to start AAC practice.
Before sitting down
Show the child two options. Hold up cereal in one hand and toast in the other. Pick up the AAC device and tap "want." Ask: "What do you want? Cereal or toast?" You can also use SabiKo's Choice Maker to present the two options on a clean screen. If they reach for one or tap their choice, model it: "You want cereal." Tap "want" on the device.
During the meal
Offer small portions. This is the most important mealtime strategy for AAC. Instead of filling the bowl, give a small amount. When it's gone, the child needs to communicate for more. This creates natural communication opportunities without withholding food.
Model "more" each time: "You want more cereal. More." Tap the button. Pour a little more.
Narrate with the device. "You're eating. Cereal is yummy." You don't need to narrate every bite. A few models per meal is plenty.
Wait. When the food runs out, pause. Look expectant. Give the child 5 to 10 seconds to attempt communication before you jump in. If they reach toward the cereal, model "more" and give it. If they press the button, celebrate and give it immediately.
Wrapping up
When the child pushes food away or seems done, model "all done." Tap the button. "All done eating. All done cereal." Then end the meal.
This is important: respect "all done." If you model it and then keep offering food, the word loses its meaning. When they say all done (or you model it for them), the meal ends.
Step-by-Step: Lunch
Lunch offers different opportunities because there are usually more choices and components to the meal.
Choosing the meal
Lay out two or three options. "Do you want sandwich or soup?" Model "want" on the device. If your child can handle a more complex exchange: "What do you want to eat?"
During the meal
Lunch often has multiple items on the plate: a sandwich, fruit, a drink. This is a great time to practice "want" plus pointing. Hold up the drink, tap "drink" on the device. Hold up the fruit, tap "eat."
If something is in a container the child can't open: wait. They'll look at you, reach toward it, or get frustrated. Before the frustration peaks, model "help" and "open." Then open it.
Social modeling
If other family members are at lunch, use the device socially. "Daddy's sandwich is yummy." "Sister wants more milk." Seeing the device used about other people (not just directed at the child) normalizes it as a communication tool.
Step-by-Step: Dinner
Dinner is the most socially complex meal. More people are usually present, there's more conversation, and the child may be tired from the day. Adjust your expectations accordingly.
Keep it simple
If your child is worn out by evening, don't push for new vocabulary at dinner. Stick with the basics: "want," "more," "all done." Consistency with a few words is better than overwhelm with many.
Family modeling
Dinner is a great time for other family members to use the device. If a sibling presses "more" to ask for more pasta, it shows the AAC user that the device isn't just "their thing." It's a communication tool anyone can use.
Commenting on food
Dinner often involves new foods or foods prepared differently than usual. This is a chance to model "yummy," "yucky," "hot," and "different." "This soup is hot. Let's wait."
Table Setup Tips
Small physical adjustments make a big difference.
Place the device within reach but not on the plate. A stable spot to the left or right of the plate works well. If the device tends to slide, a non-slip mat helps.
Use an angled stand. Having the device at a slight angle makes it easier to see and tap, especially for children with motor challenges. A tablet stand or a propped-up case works.
Protect the device. A waterproof case is worth the investment if your child is young. Spilled milk and mashed sweet potato will find their way to the screen.
Keep it on. Don't turn the device off between communication exchanges. Having to wake up the screen, enter a passcode, and open the app creates a delay that kills communication momentum.
Handling Picky Eaters
Picky eating and AAC can actually work well together. AAC gives a picky eater the vocabulary to express what they do and don't want, which reduces the frustration that often makes mealtimes miserable for the whole family.
Give them "no" and "yucky"
A child who can press "no" or "yucky" when offered broccoli is communicating clearly and appropriately. That's a win, even if you wish they'd eat the broccoli. Respect the communication.
Offer controlled choices
"Do you want carrots or peas?" Having two options (even if neither is preferred) gives the child practice with "want" and a sense of control. Control reduces anxiety, and less anxiety often means more willingness to try new things over time.
Don't require AAC use to get food
Never make a child use the device before they can eat. "You need to press 'want' before I give you your dinner" turns communication into a gatekeeping exercise. It breeds resentment toward the device. Instead, model "want" as you give them the food. They learn the association without the demand.
Mealtime Scripts
If you're new to AAC modeling, it helps to have some phrases ready to go. Here are scripts for common mealtime moments.
Offering food: "Do you want crackers? Want crackers." (Tap "want")
Child finishes a portion: "Crackers are gone. Do you want more?" (Tap "more")
Child rejects food: "You don't want that. No peas. That's okay." (Tap "no")
Something is hard to open: "You need help. Help open." (Tap "help," then "open")
Ending the meal: "All done eating. All done lunch." (Tap "all done")
Commenting: "Banana is yummy! You like banana." (Tap "yummy")
You don't need to follow these exactly. They're just a starting point so you're not staring at the device wondering what to tap.
When They Just Want to Eat
Some meals, your child will be starving and will not want to pause for communication practice. That's fine.
On these days, keep the device visible but don't push it. Model a word or two casually. Give them the food they need. There will be another meal in a few hours.
AAC is a marathon. Missing one mealtime practice session means nothing. Creating negative associations with the device at mealtimes can set you back weeks.
Tracking Progress
You don't need formal data collection at meals, but it helps to notice patterns.
After a week or two, ask yourself:
- Does my child look at the device when I model?
- Have they touched the device intentionally during a meal?
- Are they reaching for the device when they want something?
- Have they used any word independently, even once?
If you're seeing any of these, you're on track. If not, consider whether you're modeling consistently (at least once per meal) and whether the vocabulary matches what your child actually wants.
Getting Started
- Download SabiKo for free
- Program 5 mealtime words: want, more, all done, yummy, help
- Set the device next to your child's plate at the next meal
- Model one word at a time, starting with "more"
- Keep it light. Keep it fun. Keep it consistent.
Mealtimes happen every day, which means you have built-in AAC practice sessions already on your calendar. All you need to do is bring the device to the table.
Download SabiKo free and start modeling at your next meal.