Cooking Websites Need to Stop Ghosting Disabled Cooks

In 2026, the internet can deliver a perfectly seared steak recipe to a phone in seconds, but it still often slams the kitchen door in the faces of disabled cooks. Cooking is not just fuel. It is how people celebrate weddings and wakes, bribe coworkers with breakfast tacos, and teach communities to value them through the frenetic act of feeding. For disabled people—blind, Deaf, deafblind, print-disabled, chronically ill, neurodivergent, and more—food can be one of the most accessible ways to forge relationships. Yet many cooking websites remain stubbornly devoted to an archetype: the normal cook, who can watch an untranscribed video, hear a pan sizzle, and stay consistently present in the kitchen. What about everyone else?

The first obstacle is threshold design. Screen readers such as JAWS, NVDA, Apple's VoiceOver, and ZoomText need stable, uncluttered pages. Busy cooking sites, however, behave like a toddler who found the refresh button. A disabled cook might be reading letter by letter to catch a crucial comma when an ad changes in the background. Bang. The page refreshes. The screen reader cursor is knocked up, down, sideways, and into next week. Screen-reading software cannot scan and pan back as quickly as eyes. So the cook must decide: How much do they want this information? Is there a less troublesome source? Do they have the mental energy to text-search, arrow, or swipe back, assuming the page does not refresh again? For one deafblind immigrant of color, that calculus ended a reverse-sear article. Indifference toward steak and exasperation with the jittery page won. The cook navigated away.

Does that sound like a niche problem? Hardly. Ads bring revenue, yes. But people bring their retinues, and retinues attract advertisers. When disabled cooks get frustrated off a page, they remember. They recommend accessible sites to their networks. They warn people away from vexing ones. Some food websites have never been recommended by a dedicated food hound because their formats scramble screen readers. Serious Eats has been recommended, but only to people more active on Facebook via phones, since that has been the only reliable way to access a stable version, with help from Safari. Sites recommended unequivocally include King Arthur Flour, Cook's Illustrated / America's Test Kitchen when the recipe is outside the paywall, and Fine Cooking. More broadly, the keeper is whatever site appears within five to ten Google results that does not scramble a screen reader, crash a browser, or clutter the page with gibbering elements—and also knows the recipe's fundamentals. That is a low bar, and yet.

Once past the threshold, the question becomes whether recipes and techniques are presented accessibly. This changes by recipe, technique, and writer, even on one site. Take Serious Eats as a case study. Want to make sarde a beccafico, Sicilian stuffed sardines, because there is an Italian to woo? Daniel Gritzer's text tutorial is a marvel: precise directions, properly captioned photos, and multisensory cues. To pick a good fish, a cook can look for bright, silvery skin; feel for firm versus mushy flesh; look and feel for a peeling belly; smell for good fishy versus bad fishy, sushi versus seagull buffet; and look and feel for clear, plump eyes. His directions on scaling, decapitating, de-finning, eviscerating, and butterflying are simple yet thorough, with caveats about necessary and unnecessary worries. By the last step, the reader is flush with conferred competence. Another main course seems in order. Jerked chicken with mango salsa? Daniel has a mango-cutting how-to, and Kenji has a chicken breakdown.

But here comes the letdown. Both tutorials center on beautifully produced, highly instructive videos. Highly instructive—unless the cook is blind or visually impaired. Neither video is narrated or accompanied by a transcript. It is jaunty music all the way through and, for all anyone knows, dragons doing the anaconda. The text versions that follow are precise and multisensory, but the inaccessible linchpin videos still send a disabled cook running for a cookie. Specifically, the one Stella says is as big as her face. That video at least has narration, but good luck if the cook is hearing-impaired, Deaf, or allergic to music, because neither captions nor transcript is provided.

What is a cooking site to do? The answer is not mysterious. If a video or animation clarifies a technique, transcribe and caption it. Add at least a basic voice-over if it lacks a central narrator—and by basic, have Lin-Manuel Miranda rap the contents. If a photo collage scaffolds a finicky recipe, fill out alternative-text metadata for every photo and caption them with actual, informative descriptions. When writing a technique or recipe, think critically with at least five senses, if not all eleven, so the finished product is accessible from multiple sensory perspectives. King Arthur and Serious Eats already write recipes for people using different measuring systems or equipment. The same logic applies to disability.

It is beyond one cook's skill set to explain every design and coding minutia. Thankfully, disabled web-accessibility experts exist and are waiting to be asked. Organizations such as The Paciello Group and WebAIM provide consulting for companies that want their websites to be as accessible as possible. All cooking sites need to do is take a long, candid look in the mirror and ask, Am I the most accessible version of me? If the answer is negative or equivocal, reach out for help. In 2026, there is no excuse for treating disabled cooks as an afterthought. Food is connection. Accessibility is not a garnish. It is the table itself. Now, can everyone please make a Double-Caramel Flan accessible, despite all the gold we cannot see? 🍮