kitchen captions: live text for instructions cooked over a running tap. Set the screen where a wet hand can still catch the next step. Say every time aloud as you set it so the countdown stays in text.

The kitchen is the worst room in the house for speech. The exhaust fan runs at a steady drone, the tap runs through half the conversation, the timer beeps over the punchline, and the cook is usually looking at a pan with their back turned. Kitchen talk is also short and functional: a third of a cup, turn the heat down, taste it now. Every one of those lines is spoken while the speaker is doing something else, which means a deaf partner lip-reading gets a profile of a head, a glimpse of an eye, and a sentence that is already gone. That is exactly where kitchen captions come in: they put those short lines somewhere they can actually be caught, on a screen in the sightline.
The second problem is sequence. Cooking is a chain of instructions where each step depends on the one before: salt the water first, then the pasta, then taste before you drain. If the deaf partner misses one link, the meal continues but the timing breaks, and the potato soup that was supposed to simmer for ten minutes simmers for ten more because nobody said when to stop. The speech that matters in a kitchen is not the chit-chat, it is the sequencing, and sequencing is the part that gets lost first when the room is loud and the speaker is busy. Every cook knows the feeling of the dinner that continues anyway, heading toward a table where the potatoes will arrive at different temperatures, and the sequence gap is why.
There is also the matter of who talks in a shared kitchen. Often both people cook, and the speech becomes a two-directional stream: the hearing cook gives directions while the deaf partner receives them, and both are moving at once. The workable model is the one this article describes: one glanceable screen, one confirmed stream, and a convention that the next instruction lands as text before the hands move on. Not a slower kitchen, just a kitchen where the instructions have a visible place to be. That single change removes most of the re-asking that quietly eats up a recipe evening.
The placement rule for a kitchen screen is brutally simple: it must sit where the eyes already go. That spot is usually the counter between the stove and the sink, because hands move between the two all night, and a screen at the far end of the counter would be a head turn, not a glance. The best setups are a tablet on a small weighted stand, or a phone propped against a spice jar, sitting at about the height of the counter's back edge, tilted toward the cook. If the kitchen has an open shelf at eye level, that shelf is even better, because it takes the text off the cluttered counter entirely and puts it at the exact height where the eyes pass while reaching for the salt or the cutting board below it.
The second rule is cleanliness. A screen on a counter suffers oil, steam, flour dust, and the occasional splash, so the stand should have a small raised lip, the device should have a case with a glass protector, and the screen should be wiped once during the meal rather than after it. A device that needs a ten-minute rescue because a spoon fell on it will stop being used within a week, and the place where the screen lives should be dry enough that no one thinks twice about reaching past it for the salt. Dryness and reach are the two design rules: the screen must be safe to lean over, and it must never block the cutting board.
The third rule is the sightline test, done in two minutes while the water is still heating: stand at the stove, then at the sink, and see whether the text is readable from both without leaning. If the message is not readable from the stove, move the screen ten degrees toward it. The rule of thumb is that the screen should be readable from the two positions where the deaf partner spends ninety percent of the meal, and if that requires the screen to sit right next to the simmering pot, so be it, because kitchen captions belong to the cook, not to the dining table.
Sequence talk has a grammar that captions handle well and lip-reading handles terribly. The grammar is short imperative sentences: add the soy, lower the flame now, drain in thirty seconds. Each one is a complete instruction with a number attached, and the numbers are the whole point. A deaf partner reading a captioned kitchen stream catches half a cup and not the mouth shape that said it, which changes what goes into the pan. The habit that makes this work is one spoken number at a time: the hearing cook says half a cup, pauses for the glance, then continues. The pause feels unnatural for exactly one dinner.
Timers and overlapping steps are the harder case. A modern dinner has three things happening at once: rice on the back burner, vegetables in the skillet, and a sauce that needs stirring every two minutes. The cook announces the overlaps as they happen, and the caption stream handles it if the speech is kept to single lines, because text cannot follow a run-on the way ears can. Kitchen captions reach their limit when three instructions arrive in one long breath, so the deaf partner's contribution to the system is a small one: call the overlap, just say one step at a time, and the kitchen slows to the speed of the text.
There is a second layer to sequence talk: the corrections. A cook who says one teaspoon and then sees the spoon on the scale says no, a bit less, half. The correction is the hardest line to caption, because it arrives as an edit after the fact. The reading habit that solves this is treating the latest line as the truth, not the accumulation: whatever the stream says now is what the dinner should do. The hearing cook helps with a single word, confirming the newest line once, and the two of them cook from the stream rather than from the spoken history.
One couple tested captions on a Wednesday dinner, a stir-fry with four moving components, and the test had a hard rule: the deaf partner would not ask what? once. The first ten minutes surprised both of them. The hearing cook had always known, in an abstract way, that her partner missed a line here and there, but watching the meal run on text showed her the scale: salt, timing, and two instruction corrections had all slipped by in a normal evening. With the tablet between the stove and the sink, she began speaking single lines, and the recipes that had taken a lifetime to get right suddenly transferred in a night.
The second surprise was the timing. The deaf partner read the text and acted without the nervous glance, so the dinner actually moved faster, not slower. The cook's line the garlic goes in now landed as text in the same second the voice crossed the room, and the garlic went in at the correct moment rather than at the moment the deaf partner decided she had probably understood. The dish came out on time, which had never been a guaranteed outcome, and the two of them noted the strange truth of accessible design: a system designed to remove the friction of one user made the whole pair faster.
What the text did not carry was equally instructive. The cook's tone, the hurry in her voice when the garlic started to brown, lives in rhythm and not in letters, and the deaf partner asked once about it. The answer, garlic burns fast, teaches a deeper lesson than any word: the cook can say the worry out loud, and the text will carry it. The dinner ended with the pair agreeing that captions had changed the kitchen from a place of one-way instructions to a place of two cooks, and that was the real result, stronger than any single recipe.
Kitchen captions grow into a habit the way any kitchen gadget does: quietly, through repeated use, until the screen is a thing that is simply part of the kitchen. The first step past the test dinner is the grocery debate. That argument, whether to buy the fresh mushrooms or the canned ones, happens at the store, where the aisle is loud and both partners push carts. The screen there is a phone in the cart holder, and the debate resolves in text in the same way it resolves at home: the reasons get read, the choice gets made, and nobody walks a lap around the produce section to recover a lost argument.
The second step is adjustments. No dinner goes exactly to plan, and the adjustment lines, we could use less ginger next time, are the ones that make the meal better the following week. Kitchen captions catch those lines too, because they come from the same stream, so the deaf partner becomes a full participant in the tuning, not a receiver of the result. Some couples keep the last line of the evening, the note about what to change next time, as the seed of the next shopping list, and the meal improves on a visible litany rather than on a memory.
The last step is sharing the load, which is the true test of whether the habit has settled. When both partners cook, the captions serve both directions: either person can speak, and the text carries the instructions, so the roles of cook and reader blur. A good convention is that whoever is the lead cook for the night sets the screen, and the partner takes the support role, which means the screen is always where the work is. Two Wednesdays a month with roles swapped, and kitchen captions stop being an accessibility feature belonging to one person and become the house's way of cooking.
On the counter between the stove and the sink, tilted toward the cook, at about the height of the counter's back edge. Open shelves at eye level are even better. The rule is that the text must be readable from the two positions where the deaf partner spends the most time, without leaning or turning.
It can, but the fan affects the mic less than you would expect when the phone sits on the counter near the speaker. Choose a tool with decent noise handling, and keep the device roughly a meter from the cook's mouth. Where the fan still wins, move the screen, not the fan, and keep instructions to single spoken lines.
Speak in single instructions with the number first, half a cup of rice, then pause for the glance that reads it. When correcting a step, say the new version plainly and let the text show it. One step at a time is the whole adjustment, and it feels awkward only for the first dinner.
They help when the cook announces overlap one line at a time. The reader treats the newest line as the truth rather than accumulating everything said before. For crowded moments, asking the cook to slow to the text's speed for three seconds keeps the sequence intact.

Place the screen between stove and sink and start cooking in single spoken lines.
Use it across macOS, Windows, iOS, and Android