Inclusive Design Isn't Charity. It's the Cheapest Way to Ship a Resilient Product.
Berkeley, California, 1972. A handful of disabled activists, led by Ed Roberts and the Center for Independent Living, got tired of arguing for wheelchair-accessible sidewalks and poured their own curb ramp at the corner of Telegraph and Haste, without a permit, because the city wasn't going to do it fast enough. That ramp is generally credited as the first modern curb cut in the country. It was built for one purpose: to let wheelchair users cross a street without leaving the road entirely.
Watch that same curb cut today and count who's actually using it. Parents with strollers. Delivery workers with hand trucks. Travelers dragging roller bags. Someone on a bike walking it across. Skateboarders. A kid on a scooter. The wheelchair user it was built for is one person in a rotation of dozens, most of whom never think about the ramp at all because it's just how the sidewalk works now. Researchers later gave this phenomenon a name — the curb-cut effect — and it's one of the most quietly useful ideas in design that most product teams still treat as a compliance checkbox rather than a method.
Compliance Framing Buries the Actual Insight
Say "accessibility" in most product meetings and you get one of two reactions: a shrug toward legal risk, or a nod toward doing the right thing, followed by a deprioritization the moment a growth feature needs the same sprint. Both reactions treat inclusive design as a cost center — a tax paid to avoid a lawsuit or satisfy a values statement, layered on top of the "real" product work rather than a source of it. That framing isn't just uninspiring, it's factually backwards about where the value actually comes from.
The compliance frame asks "does this meet the standard for people with disabilities." The methodology frame asks a completely different question: "what does designing for this specific, real, hard constraint force us to discover that designing for the median user never would." Those questions produce different artifacts. The first produces a checklist and an audit. The second produces captions that turn out to be how most people watch video in public without sound, voice interfaces that turn out to be how people cook with messy hands, and high-contrast modes that turn out to be how everyone reads a phone screen in direct sunlight. None of those were "for" disabled users in the sense of being scoped narrowly to them. They were built by taking a real disabled user's real constraint seriously enough to solve it properly, and the solution generalized because the constraint was never actually as narrow as the label made it sound.
Solve for One, Extend to Many
This is the operating principle underneath the curb-cut effect, and it's worth stating as a method rather than a slogan: pick a real constraint experienced by a specific, often-excluded user, design a genuine solution to that exact constraint, then look at who else the solution serves once it exists. Not "design for everyone" as a vague aspiration — that produces mush, because "everyone" isn't a real constraint anyone can design against. Design for someone specific and load-bearing, and let the generalization happen as a discovery, not a starting brief.
OXO's original line of kitchen tools is the standard example for good reason: the company's founder, Sam Farber, watched his wife struggle with a standard vegetable peeler because arthritis made the thin metal handle painful to grip. The team designed a peeler with a soft, wide, cushioned handle to solve that one exact problem for people with limited hand strength. It sold to everyone, disabled or not, because a comfortable grip is a better grip for a hand regardless of what's constraining that hand — arthritis, wet dishes, a kid's smaller fingers, or just an evening of chopping vegetables. The constraint was specific. The insight it surfaced wasn't.
That pattern — specific constraint, general insight — is the actual mechanism, and it's the reason inclusive design methodology tends to outperform generic usability testing at finding improvements nobody asked for. Median-user research optimizes around the center of a distribution that, by construction, already works reasonably well; you're polishing something that isn't broken. Designing against a genuine edge constraint forces you to solve the problem at its hardest, most honest version, and hard, honest versions of problems tend to expose assumptions baked so deep into the "normal" design that nobody thought to question them until someone who couldn't use it forced the question.
The Cost Argument Nobody Makes Correctly
Design teams debating whether to invest in accessibility work almost always frame the decision as spend now versus risk later — build it in or pay for a lawsuit and a retrofit. That's true as far as it goes, and retrofit costs are real: bolting accessibility onto a system that was never built around real constraints is reliably more expensive than building it in from the start, for the same reason design tokens implemented after the fact turn into a mess that a token system designed in from day one avoids. But the retrofit-cost argument still frames inclusive design as insurance — money spent to avoid a future loss, not money spent to generate a future gain.
The curb-cut framing is a different, better argument, and it's the one that should actually win the resourcing debate: constraint-driven design is a cheap, reliable way to find product improvements that benefit your entire user base, discovered by looking in a place your competitors, running the same generic usability tests as everyone else, systematically aren't looking. You don't need a bigger research budget to find these insights. You need to take a smaller, currently underserved slice of your existing users seriously enough to solve their actual problem, all the way through, instead of accommodating it halfway.
What This Looks Like Before the Retrofit
In practice this means treating accessibility requirements as a genuine design brief rather than a QA pass at the end. It means putting someone who experiences the constraint in the room before the first wireframe, not the usability test after the third one — the OXO peeler doesn't exist if the design process starts with a generic hand and adds "arthritis considerations" as an annotation afterward. It means asking, of any feature already in flight, who's currently working around a limitation this feature imposes, and treating their workaround as a design brief instead of an edge case to deprioritize.
The curb cut poured illegally at Telegraph and Haste in 1972 wasn't a compliance exercise. Nobody involved was thinking about a market. They were solving one specific, urgent, real problem as completely as they could, for the people who actually had it. Fifty years later almost nobody who uses a curb cut is the person it was built for, and that's not a story about mission drift. It's the whole method working exactly as it should.