AAC for Kabuki Syndrome: Supporting Individual Communication Needs

Exploring AAC for Kabuki syndrome starts with a person’s communication—not with choosing a device. People with the same diagnosis can have different strengths, preferences, routines, and support needs. A useful plan asks what the person wants to express, how they can access communication, which language system makes sense, and how partners can make the system part of everyday life. The diagnosis can be part of a conversation, but it cannot stand in for learning about the individual.

Explore communication support resources

What should AAC support in daily life?

Augmentative and alternative communication (AAC) includes methods that supplement or provide communication when speech alone does not meet a person’s needs. It can include gestures, facial expression, writing, picture or symbol boards, and speech-generating devices. AAC does not have to be a last resort, and exploring it does not require setting aside speech. The aim is to give the person dependable ways to communicate across people and situations, including when speech is difficult to understand, tiring, or unavailable.

Begin by noticing what the person already communicates and what they might want to communicate more easily. A child may want to make choices, refuse, ask for help, comment on a favorite activity, or join a conversation with siblings. An adult may prioritize social connection, work, healthcare decisions, household responsibilities, or communicating privately. These are examples, not assumptions about what any person with Kabuki syndrome needs. Ask the person, using accessible ways to respond, and let their priorities guide the plan.

Turn broad hopes into specific situations without turning communication into a test. Instead of “use AAC more,” a family and SLP might ask how the person can tell a sibling which game to play, share an idea during a lesson, or ask a clinician to pause. The goal can be participation, not a certain number of button presses. Plan for spontaneous messages, including questions, jokes, comments, and “no,” rather than only answers to adult prompts.

Consider the full range of purposes communication serves. People communicate to request and reject, but also to greet, give information, tell stories, ask questions, express feelings, make social connections, and repair misunderstandings. A system limited to snack choices may not serve someone who wants to talk about a hobby or explain a problem. A conversation plan should protect opportunities to say something unexpected and to change the subject.

Why does an individualized approach matter?

Kabuki syndrome is associated with a range of possible developmental and health features, but the diagnosis alone does not tell a team how a particular person communicates or which AAC approach will work best. Do not infer a person’s understanding, language, hearing, vision, movement, learning profile, or preferences from the diagnosis. Observe the individual, ask the person and people who know them well, and coordinate with appropriate professionals when needed.

Communication can vary by partner and setting. A person may communicate differently with familiar family than with new people, or differently at home, school, work, and in the community. Fatigue, noise, positioning, time pressure, sensory demands, and a partner’s familiarity can all affect what is easy in a moment. A system that seems convenient in one room may need changes elsewhere. This is why a single brief demonstration should not be treated as a complete evaluation.

Build the plan around participation rather than a picture of how communication “should” look. Some people use speech and AAC together. Others may rely more on a device, writing, gestures, or communication boards in particular contexts. The methods a person uses can change over time, or from one activity to the next. That flexibility is not failure; it is a practical response to varied communication conditions.

It is useful to distinguish observation from interpretation. A person who does not select a symbol during one activity may be tired, unsure what is being asked, unable to reach the device, or simply uninterested in the proposed topic. Record what happened before concluding why. Ask what change—more wait time, a different position, a personally meaningful activity, or a more familiar partner—might make the next attempt more informative.

How can a team learn what the person wants to say?

People do not need to demonstrate a prescribed set of skills before their communication deserves support. A team can start by creating opportunities during familiar routines and noticing how the person responds. Include time to initiate, make choices, reject an option, ask questions, share an idea, and repair a misunderstanding. Avoid presenting a stream of questions that leaves no space for the person to lead.

• Ask the person.

  Use accessible questions, wait time, and the person’s current ways to respond. Offer meaningful choices, and include a way to decline both options.

• Listen to communication partners.

  Families, educators, support staff, and clinicians may notice different strengths and barriers. Treat their observations as useful information, not a substitute for the person’s preferences.

• Look across activities.

  Consider meals, play, learning, personal care, community outings, and conversations. Identify routine messages as well as less predictable topics.

• Notice repair.

  When communication breaks down, observe how the person signals they were misunderstood and what helps them try again.

• Record context.

  Note the setting, partner, access method, topic, and what made communication easier or harder. A brief record helps a team compare experiences rather than rely on memory.

A simple observation note can be short and concrete. For example: “After lunch, at the kitchen table, Sam used a gesture to refuse another serving. The device was on a shelf across the room. When it was brought within reach and the partner waited, Sam selected ‘all done.’” The note does not prove that a particular system is best. It identifies a practical issue—availability—and a question to test again.

A communication profile can capture what matters to the person, familiar words and topics, languages used, preferred ways of interacting, and situations where support is needed. Include information partners can act on: where the system is kept, how the person signals “wait,” what to do when a message is unclear, and who can help with technical questions. Keep it concise enough to use and update it with the person. It should not reduce them to a checklist or imply a skill seen once will be available in every context.

Ask about privacy as well as participation. Some messages may be intended for a family member or clinician, while others are personal. The person should have a way to communicate privately where appropriate, and partners should not assume that every message must be announced or interpreted aloud. Discuss practical safeguards with the person and relevant support team.

What access options should be considered?

Access means how a person selects or communicates through a system. Touch is one possibility, but not the only one. A person may use a switch, head movement, eye gaze, or a combination of methods. The right approach depends on the individual’s movement, vision, positioning, stamina, preferences, and activity demands. Qualified professionals should assess these needs as appropriate; a product description cannot determine suitability.

When exploring direct touch, consider whether targets can be selected accurately and comfortably, whether the screen can be positioned well, and whether the person can use it long enough to participate. The evaluator can observe whether the person reaches consistently, whether accidental selections occur, and whether the device remains stable. A keyguard or positioning support may help some users, but accessories are not automatically appropriate or compatible with every device. Check the actual configuration rather than assuming a feature will fit.

Switch access may offer another way to select items. The team may need to consider a reliable movement, switch placement, timing, scanning style, and fatigue. Ask how many selections the person needs to make for a typical message and whether the pace leaves room for a real conversation. If the person can use a switch in one position but not another, test relevant settings and discuss a practical backup. Do not treat a slow response as lack of understanding or interest.

Eye-gaze access may be worth exploring when a person can control a selection with their eyes, but performance may depend on positioning, lighting, calibration, vision, and the demands of the environment. A useful trial tests more than whether the person can make one selection. Can they find vocabulary, build a message, look away and return, and use the setup during an activity they value? Does the system need recalibration when the person changes position? The SLP and other relevant professionals can help structure those observations.

For every access approach, ask whether it remains usable during ordinary routines. Can the person reach or orient to the device? Can it be mounted safely where needed? Is the method comfortable, and can it be used when the person is tired or seated differently? What happens if the primary method is unavailable? A low-tech board, gestures, writing, or another established method can provide a backup; no single tool needs to carry every communication situation.

Compare access by task, not by a single score. A person might touch a large target accurately while seated at a table but struggle to reach a smaller target in a wheelchair position. Eye gaze might work well in a quiet room yet need adjustment in a bright community setting. Record the conditions for each observation. This makes the comparison fairer and helps the team decide which questions require more assessment.

How should a language system be selected?

A language system is the way messages, words, and symbols are organized for communication. Systems can use text, symbols, or both, and layouts differ. The goal is not to match a layout to a diagnosis. It is to find an organization the person can learn and use to express a broad range of messages, with support that fits the person’s language and learning experiences.

During evaluation, consider current communication methods, languages, literacy experiences, familiar vocabulary, and opportunities to learn. Ask how the system supports greetings, opinions, questions, humor, storytelling, and new words—not only immediate choices. Can the person communicate about something that is not visible in the room? Can they say what happened earlier or ask about what might happen next? A system should support partner modeling without requiring the user to imitate every message.

Vocabulary organization affects everyday use. If a person needs several steps to find a familiar word, the team should examine whether that navigation is workable for them. At the same time, a layout should not be judged only by how quickly a partner can find a word during a demonstration. Let the person explore and learn, and observe how the system supports messages they actually want to communicate. Ask how vocabulary can be added or adjusted and who will support those changes.

Consistency may help partners model language across settings, while changes may be needed as the person’s access or routines evolve. Discuss what should remain stable and what can be personalized. Before changing a layout or removing vocabulary, consider whether the person relies on that organization and consult the team. A change that seems small to a partner can make a familiar message harder to find.

Language and culture matter. Ask the person and family which languages are used in daily life and what words, names, and expressions are meaningful. A system should support communication with the people and in the places that matter, not just fit the language of a formal evaluation. If the family uses more than one language, discuss how the system can reflect that and how partners can support communication in each context. Do not assume one language is the person’s only language or that a family member can always interpret.

Consider literacy and symbol preferences without making them a gate. Some people use text, some use symbols, and some combine them. A person’s needs may change across partners, topics, and environments. The team can test whether labels, symbol size, voice output, and vocabulary access are understandable and useful to the person. Keep evaluation focused on access to communication rather than a pass-or-fail judgment about reading or symbol knowledge.

What should a device or system trial include?

A trial is a structured opportunity to learn whether a particular setup supports meaningful communication. It is not a promise that a device will be covered or the right choice, and it should not be treated as a short pass-or-fail test. Work with the person’s speech-language pathologist (SLP) and other relevant professionals to decide what to try and what observations will help. The person’s preferences are central throughout.

Before a trial, choose several real activities and write down the questions the team hopes to answer. Include a familiar routine, a conversation with someone important to the person, and a less predictable activity if possible. Questions might include: Can the person independently get to useful vocabulary? Does the access method work in their usual seating position? Can partners model language? Is the system practical to carry or mount? What support is needed when a message is misunderstood?

1. Set goals with the person.

   Choose meaningful situations and messages, including ways to initiate and reject, rather than only scripted prompts. Ask what would make the trial worthwhile to them.

2. Check access and positioning.

   Test the setup where it will be used, with attention to comfort, accuracy, effort, and fatigue. Note which adjustments are needed and who can make them.

3. Explore language.

   Try familiar and novel messages. Observe whether the person can communicate beyond a small set of immediate choices and how easily partners can model.

4. Support partners.

   Show communication partners how to make the system available, model its use, wait, and respond to all communication attempts.

5. Review what happened.

   Gather the person’s feedback and partner observations. Decide what should be adjusted, tested further, or reconsidered.

For a clear comparison, keep the activity reasonably consistent when testing two options. For example, invite the person to choose and comment during a familiar music activity with each setup. Note whether the device was positioned equally well, whether the same vocabulary was available, how much help was offered, and whether the person seemed comfortable. If one option was tested in a noisy hallway and another in a quiet room, the result may tell more about the setting than the system.

Make a short trial log rather than relying on a general impression. Record date, activity, communication partner, access configuration, messages attempted, successful communication, breakdowns, and the person’s own feedback. Add observations about battery or mounting only when relevant to the activity. At review, look for patterns: perhaps a system works well for familiar messages but needs vocabulary changes for conversation, or perhaps access is accurate in the morning and less comfortable after a long day. Patterns suggest what to test next; they are not a clinical diagnosis.

Forbes AAC describes distinct evaluation pathways. A licensed SLP may request equipment for clinician-held sessions; that equipment stays with the SLP, with a standard loan term of up to four weeks subject to availability and conditions. A separate SLP-initiated home trial follows an insurance benefits check and confirmation; stated code timing begins after coverage confirmation, not at shipment. An evaluation kit is a conditional, no-cost loan of specified SoundPOD, FlexABLE, and limited keyguards for eligible SLPs or facilities that already have an iPad. It is not ownership of a speech-generating device. Ask the evaluator and provider which current process applies before planning around a trial.

Keep the trial question distinct from the purchase question. “Can we explore this setup?” and “Will a payer fund this configuration?” are not the same. The first concerns communication needs and practical use; the second depends on payer rules and documentation. A trial can inform evaluation without guaranteeing coverage, and coverage information does not establish that a system is the person’s preferred choice.

How can communication partners make AAC useful?

A system is more likely to become part of everyday communication when partners make it available, respond respectfully, and use it themselves as a model. Partners do not need to wait for a person to master a device before including them in conversation. They can point to words while speaking, pause for a response, and treat gestures, facial expressions, vocalizations, and device selections as communication.

• Keep the communication system accessible during the routines where the person wants to participate.

• Model a few relevant words without demanding that the person copy them.

• Allow adequate time for the person to find and compose a message.

• Offer opportunities to comment, ask, refuse, and start a topic—not just answer questions.

• Confirm uncertain messages neutrally, and offer a way to clarify or try again.

• Share useful vocabulary and support strategies among family, school, and other settings, with the person’s preferences in mind.

Modeling can be small and natural. During a snack, a partner might select “crunchy” while describing the food, then continue the conversation without asking the person to repeat it. During a walk, a partner might model “look,” “stop,” or a person’s preferred comment. The point is not to turn every activity into a lesson. It is to show that the system can carry real messages and to make language available in context.

Waiting matters. A partner can ask a question, then pause long enough for the person to notice, decide, access the system, and respond. If the partner asks again immediately or answers for the person, the person may lose the opportunity to participate. The right amount of time varies. Observe what helps the individual rather than imposing a fixed timer.

When a message is unclear, acknowledge the communication attempt first. A partner might say, “I heard you start a message. I’m not sure I understood. Would you like to show me another way?” Avoid guessing repeatedly or treating an incorrect interpretation as the person’s intended message. Offer a calm path to repair, including a yes/no confirmation if that is accessible and appropriate.

Partners should avoid speaking for the person when they can wait for the person’s own response. They should also avoid treating a device as a reward that can be removed for behavior. AAC is a means of communication, so the person should have dependable access to it. If a system is difficult to use, investigate access, vocabulary, positioning, partner support, and technical issues instead of assuming a lack of interest.

Plan for availability in ordinary life. Decide where the device or board will be during meals, travel, school, appointments, and downtime. Consider charging, carrying, mounting, and what happens if the device is being repaired. A backup option should be known to the person and partners, not kept in a drawer where no one can find it. Make the arrangement practical, and revisit it when routines change.

How can a team compare options?

There is no universally appropriate device or language system. A comparison should connect the person’s goals to practical features and observed performance. A speech-generating device may use different operating systems and support different software or access features. Compatibility varies by model and accessory, so confirm details for the exact configuration being considered.

Area to compare	Questions to ask	What to observe
Communication goals	Does it support the person’s messages and daily contexts?	Initiations, choices, comments, questions, refusals, and repair
Access	Can the person use the input method comfortably and reliably?	Positioning, effort, accuracy, fatigue, and use across settings
Language system	Can the person reach useful vocabulary and grow expression?	Familiar and new messages, navigation, and partner modeling
Practical fit	Can it be carried, mounted, maintained, and supported?	Use in everyday routines, backup options, and partner confidence

Forbes AAC offers ProSlate devices in the iOS family and WinSlate devices in the Windows family, alongside software and accessories. These descriptions can help frame questions, but do not establish that a model will suit a particular person. ProSlate markets most compatible AAC apps rather than every app. WinSlate access and features vary by model, and some email, text, and Skype functions require a separately sold Feature Unlock Key. Some software and accessories are model-specific, and dedicated funded devices can have restrictions. Confirm the exact configuration, supported access method, software, and applicable funding requirements with the evaluator and provider.

Compare practical considerations beyond the screen. How will the device be carried? Does the person need a mount in a particular setting? Who can troubleshoot if the system stops working? Can a familiar partner help adjust settings, or does that require professional support? Is the system usable in the places the person wants to communicate? These questions do not outweigh communication needs, but they can reveal barriers before a decision is made.

It may help to create a short decision record with three columns: “must support,” “would help,” and “needs more testing.” For one person, access from a wheelchair position and a way to comment during class might be essential; a particular color or case style might be a preference; eye-gaze performance outdoors might need more testing. The person should contribute to the categories in whatever way is accessible. This record keeps the conversation anchored in their life rather than a feature checklist.

What should families and SLPs discuss about funding?

Funding is separate from whether a communication system appears useful. Coverage decisions depend on the payer, state, documentation, and device configuration. Do not assume that insurance, Medicare, or Medicaid will pay for a particular option. A benefits check can clarify a payer’s process, but it is not a guarantee of approval.

For a funded purchase, an SLP and family may need to collect clinical documentation and complete payer-specific steps. Forbes AAC describes a Funding Portal for organizing packet documents and tracking steps. Direct-pay purchasers, including schools and other institutions, use a sales-assisted quote process rather than a public checkout. Ask which route applies, what documentation is needed, and what costs or terms should be confirmed before proceeding. Device prices and availability should be obtained directly from the provider rather than inferred.

When reviewing a proposed system, separate communication needs from payer rules. If a feature is not covered or is restricted on a funded configuration, ask the team what alternatives are available and how to preserve meaningful communication. Do not change a system in a way that undermines access or safety without guidance from the professionals involved. Keep copies of the information the team used to make the decision, including the model and configuration discussed, so questions can be followed up accurately.

Families can prepare questions before contacting a payer or provider: Which documentation is required? Who submits it? What is the process if the initial request is incomplete or denied? Which features are included in the proposed configuration? Are software licenses, accessories, mounts, or training handled separately? The answers vary, so these are questions to verify, not assumptions about a particular plan. A specialist or SLP can help clarify the process relevant to the individual.

What does a useful plan look like over time?

A plan is not finished when a system is selected. The person’s routines, interests, access, communication partners, and goals can change. Schedule check-ins around meaningful questions rather than waiting for a problem to become overwhelming. Is the system available where needed? Can the person express new interests? Are partners comfortable supporting communication? Are there recurring breakdowns that call for an adjustment or further evaluation?

Use a small review cycle. First, ask the person what is working and what is frustrating. Next, gather observations from a few partners in different settings. Then identify one or two changes to test, such as moving the device to a more accessible location, adding relevant vocabulary with appropriate support, or practicing a repair strategy. Finally, review whether those changes improved participation from the person’s point of view. Avoid changing many things at once if the team needs to understand what helped.

Keep the person’s agency at the center of adjustments. A partner may think a different voice or layout is easier, but the person should be invited to express a preference. If direct feedback is difficult, use accessible choices, observe acceptance and rejection, and avoid interpreting silence as agreement. Changes to a familiar system can be disruptive, so plan them with the person and explain what will happen.

There may be periods when the person uses AAC less often. Rather than treating frequency alone as success or failure, ask what communication opportunities were available and whether the system met the person’s needs. Perhaps partners did not bring it along, the activity did not invite interaction, or the access method was tiring. The next step may be environmental or partner support, not pressure on the user to demonstrate use.

Frequently asked questions

Does every person with Kabuki syndrome need AAC?

No single communication approach is right for everyone. AAC may be considered when a person wants or needs additional ways to communicate, but the diagnosis alone does not determine that need. Decisions should reflect the individual’s communication, preferences, and everyday goals.

Does using AAC prevent speech development?

AAC is used to support communication and can be explored alongside speech. A team should focus on giving the person reliable ways to express themselves, not require speech to stop before AAC is considered. Discuss questions about an individual’s communication development with the SLP who knows them.

How do we know which access method is suitable?

Explore access methods through individualized assessment and practical trials. Consider comfort, accuracy, positioning, vision, movement, stamina, and use across everyday settings. One successful selection in a brief demonstration does not settle whether a method is useful throughout the day.

Can a family borrow a device directly?

Trial arrangements differ. A licensed SLP may request clinician-held equipment, while a separate home trial is initiated by an SLP after an insurance benefits check and confirmation. The evaluation kit is a conditional loan of specified accessories for eligible SLPs or facilities with an iPad. Families should ask the SLP and provider which option applies rather than assume an unconditional home loan is available.

Who should be involved in planning?

Include the person, family or caregivers, and an SLP. Other professionals may contribute when relevant to access, positioning, hearing, vision, learning, or daily support. The team should make space for the person’s preferences and share practical strategies across settings.

Review AAC resources for your next conversation

A useful AAC plan is one the person can access, understands how to use, and can bring into the activities and relationships that matter to them. Start with their communication goals, learn through supported practice, and adjust the plan as those goals and needs evolve.