Lightning Rambles
Introducing:
Lightning Core
The Lightning Core Pageset is a passion project that completely redefines and reimagines what a robust AAC pageset looks like. Many robust systems currently offer beginning pagesets that have 500 to 2,000 words- a miniscule percent of the 20,000 to 35,000 words a typically developing person knows. The Lightning Core Pageset aims to start with around 7,000 words- hitting anywhere from 20,000, to 30,000 words when word form combinations are taken into consideration. This challenges previous systems that have ranged from 5,000 to 7,500 words, even when including word form combinations. Ultimately this is still a small percent of what a typical developing person has access to- 20% to 35% to be exact- but is a major improvement from the around 5% of words AAC systems have previously represented.Â
Goals
As the Lightning Core grows and expands, it will focus on a few different goals in a different directions. The three main goals Lightning Core is focusing on are varying grid sizes, accessible and diverse designs, and expanding vocabulary options. Lightning Core would love to eventually pursue goals in multilingual responsiveness, but does not have the capacity to do so at this time. Any interest or expertise in this goal would be greatly appreciated, as there is a deep desire for that to be a focus goal.
Prototype
Before any of these goals can start, the prototype of the Lightning Core must be finished. This prototype is being developed by SLP graduate student Remiel Cooper (they/any neopronouns). Remiel Cooper is an Autistic multidisabled part time AAC user and this design comes from them completely gutting their old AAC system to create one that works for them. This project began on Avaz’s AAC system, which is evident by the current pageset’s distinct 8x12 grid size. It is currently being developed in TD Snap due to customizability of features and access to TD Snap’s Pageset Central- a hub for sharing pages and core boards. This will be used as one of the places this completed project will be posted. Remiel Cooper expects this prototype to be finished in the Spring of 2027. It will launch as an 8x12 board with both an adult and child version. After this first prototype is completed, development will continue targeting the three main listed goals.
Goal One
One of these targeted goals is varying grid sizes. Remiel Cooper firmly believes that the best grid size is the largest grid a person can see and/or access efficiently and effectively. Within the profession, there has been a long history of prioritizing smaller grid sizes and making assumptions about what AAC users can and cannot do. Lightning Core is working to take an opposite approach, with larger grid sizes being prioritized first. The hope is that this will encourage exploration into larger grid sizes that may have been initially dismissed and foster success with tools like motor planning in attempts to reduce cognitive load. Some current grid sizes being considered for exploration are 10x12, 8x14, 8x10, 7x9, and 7x7.
Goal Two
Another targeted goal is accessible and diverse designs. This goal focuses on making this pageset accessible to a wider set of users, including those with CVI, those who may be using eye gaze or scanning, and those who are young children. There are a variety of best practices for color contrast, design implementation, background colors, and more based on diagnosis, age, and other compounding factors. A current goal is to review relevant literature and follow best practices to ensure the Lightning Core is accessible. This also means keeping this pageset diverse, using diverse symbols that represent a wide range of people and experiences. It means being culturally considerate and conscious. It means listening to other AAC users when they discuss what they want in their systems and on their devices- within their pagesets. Many of the Lightning Core takes symbols directly from the AAC Image Library- an Image Library created by disabled people, mostly AAC users- for AAC users.
Goal Three
Finally, a goal is to prioritize vocabulary. While a keyboard will always be available, a keyboard is not always an accessible option for users for a variety of reasons. This means that every word- yes every word- should exist in an AAC users system. The Lightning Core aims to one day hit that 20,000 to 35,000 goal and then surpass it. Regardless of if an AAC user is literate, regardless of if they can use a keyboard, they should have the option and the availability of every word in their AAC system. We can still teach adaptive skills such as describing options and focusing on core words, but that doesn’t mean fringe words aren’t important or should be left to be forgotten. As words are realized to be missing from the Lightning Core, they will be added though patch updates. How these words will be added might pose a challenge, as the intent is not to replace the system each time an update so that customization within pagesets isn't disturbed. The current plan is to have two separate releases- a complete patch update for new users, and a vocabulary ‘booster’ for current users that will allow them to sort new vocabulary words into current folders as needed.
Developmental Focuses
Development for the prototype is currently being focused in three areas- vocabulary expansion, cultural responsiveness, and a blended model of motor planning and context dependent categories. These three areas represent the core of what Lightning Core is- a tool for accessibility. Vocabulary increases the options that are available to people. It gives opportunities to share opinions, give dissent, and communicate needs. A culturally responsive program ensures that this pageset is meeting the needs of those it serves. Instead of creating a pageset that then expects people to fit it, this pageset brings people to it and adjusts to them. It responds and adapts as needed to people, their culture, and their communities. Finally, it takes the approach that pure motor planning or pure context dependent categorical location is not the solution. As humans we are not either or, and for AAC users this is true as well.
Vocabulary expansion has and continues to be a key point of this operation. AAC users should have the opportunity to talk about anything. The right and access to this is essential. The development for this is perhaps the easiest. If it is a word that exists, it should exist in the AAC system. Due to the team size and timing, vocabulary size will have to start smaller, so some of this task is prioritizing words and cutting losses. It is keeping track of words, finding synonyms and antonyms, and keeping track of spelling variants.
Next is culture responsiveness. This program has to represent the user which is why symbols created by disabled people are being used and words used to accurately represent these communities are used. Words and categories that have previously been shied away from in AAC systems like race, culture, sex, queer identities, and more are being directly addressed and focused. AAC users have the right to these topics and the right to agree, support, disagree, and attack these identities. It is a goal to continuously involve and get feedback from AAC users as this project continues, as well as from a wide range of humans to ensure cultural responsiveness is taking place.
Finally, this system does not focus on solely motor planning or context dependent categorical locations. It uses both systems. When it makes sense for words to appear twice, they do. When possible and for ease of use, motor planning is used to create efficient systems that reduce cognitive load. Rarely is alphabetical organization used in order to prevent recategorization during updates. Users are welcome to customize this further so no alphabetical use occurs. Learning motor planning can create significant mental strains, but long term AAC use without motor plans can do the same. This pageset attempts to balance these two, using motor planning when it becomes natural to do so, and being more context dependent when that is more natural as well.