You read step three. You walk to the fridge. By the time your hand is on the door, you have forgotten what you were getting.
Or this one: the recipe says "while the onions caramelize, prep the garlic, then check the rice." You read it twice. You start the onions. Ten minutes later you are staring at a smoking pan wondering when "while the onions caramelize" was supposed to end.
If you have ADHD, you know these moments. You have probably blamed yourself for them more times than you can count.
You should not have.
The Hidden Test Inside Every Recipe
A recipe is not really instructions. It is a working memory test in disguise.
"Sauté the onions, add the garlic, deglaze with wine, then reduce" reads like four steps. Cognitively, it is something else entirely. You have to hold the sequence in your head, track which one you are on, estimate how long each takes, switch between watching the pan and reading the next line, and notice when something needs to happen even though nothing is telling you it does.
This is not metaphor. Researchers actually use cooking as a clinical assessment of executive function, because the act of preparing a meal requires nearly every executive function firing at once: planning, prospective memory, multitasking, and the capacity to maintain multiple sub-goals within a strict timeframe. When a neuropsychologist wants to measure whether someone's executive function is working, they hand them a cooking task. The kitchen is the standardized environment in which the brain's most demanding mental operations get measured.
For roughly 15.5 million American adults with ADHD, those are the exact operations the brain struggles to provide on demand. Working memory drops. Time perception blurs. Task switching costs more. Prospective memory, the kind that reminds you the rice is still cooking, runs unreliably.
So when a recipe asks you to do all of that at once, smoothly, while standing up after a long day, it is asking the brain to perform the very test it is least equipped to pass.
The Format Was Never Neutral
Here is the part nobody says out loud: recipes were written for a specific kind of attention.
The recipe writer imagined a reader who could read a paragraph once, hold its structure in mind, and execute it in order without losing the thread. That reader exists. That reader is also rarer than the recipe pretends. Almost everyone struggles with this on a tired Tuesday. ADHD cooks struggle with it on every Tuesday.
When a recipe condenses three actions into one sentence, that compression is not neutral. It is a design choice that assumes a particular kind of brain on the other end. Recipe developers know this. They face an impossible task: translating dynamic, real-time cooking into static text that has to work for everyone. Something has to give. What gives, almost always, is the cook on the receiving end who does not match the imagined reader.
ADHD does not make cooking hard. Cooking, as recipes deliver it, was already hard. ADHD just removes the option of pretending otherwise.
This is what an accessibility problem looks like. The knowledge is there. The skill is there. The desire to cook is there. What is missing is a format that meets the cook where they actually are.
What Accessibility Actually Means
Captions do not rewrite the dialogue. Screen readers do not edit the article. Translation does not change the author's intent. These are accessibility layers, tools that sit between content and the people who need it, so that the content can reach more readers without being changed.
Recipes need the same thing.
A recipe that talks to you, one step at a time, and waits for you before moving on, is not a workaround for ADHD. It is a recipe that has stopped assuming you have a working memory the size of a chessboard. A recipe you can interrupt to ask "wait, where was I?" is not a special accommodation. It is a recipe that has stopped pretending the cook never gets pulled away.
A recipe that paces itself to your hands instead of an idealized timeline, that breaks compressed sentences into one action at a time, that lets you ask questions out loud without scrolling back through a wall of text. That is not ADHD-friendly cooking. That is just cooking, finally translated into a form the kitchen actually requires.
The ADHD cook is the canary in the coal mine. The recipe format has been failing everyone, quietly, for decades. Tired parents, exhausted shift workers, beginners, people cooking after a hard day. ADHD cooks feel the failure first and most sharply because they cannot mask it with willpower. Everyone else has been compensating with effort that the format was never supposed to require.
What Changes When the Recipe Meets You Halfway
There is a version of cooking where you do not have to hold the whole recipe in your head. Where the next step arrives when you are ready for it, not before. Where "what was I doing?" gets an answer instead of a panic. Where the recipe pauses with you, not against you.
That version is not aspirational. It is technically straightforward. The recipe stays exactly as the author wrote it, every word, every measurement. What changes is how it reaches you.
If you have ADHD and you have ever closed a recipe halfway through and ordered takeout, the recipe failed you. Not the other way around.
Ready to cook a recipe that actually meets you in the kitchen?
Try ChefTalk, the voice-first cooking companion that turns any recipe into hands-free, step-by-step guidance.
At ChefTalk, we're building a voice-first cooking companion that transforms any recipe into hands-free, step-by-step guidance. Learn more.
Sources
- Doherty, T. A., Barker, L. A., Denniss, R., Jalil, A., & Beer, M. D. (2015). The cooking task: making a meal of executive functions. Frontiers in Behavioral Neuroscience, 9, 22.
- Staley, B. S., et al. (2024). Attention-Deficit/Hyperactivity Disorder Diagnosis, Treatment, and Telehealth Use in Adults — United States, October–November 2023. MMWR Morbidity and Mortality Weekly Report, 73(40), 890–895.