The sidewalk and the stage
The whole story, written down: the sidewalk in San Francisco where it started, the five rules that came before any code, the doors for the crew who never got a login, and the mango tree. About ten minutes.
Free and open source, for any workplace
Ask for what you need at work, in your own words, without ever saying why.
First place · Builder Track · Agentforce for Good · Dreamforce 2026
The parent who needs to leave at four for pickup. The expecting mom who could use a little logistical grace. The new hire who'd do better work with a bigger monitor, and never says so, because asking means justifying yourself to the person who decides your career.
The cost lands hardest on disabled workers. More than one in four US adults has a disability, yet at a typical large employer only 3.5% of staff have told their employer about one. And of employers who told the Job Accommodation Network what an accommodation cost, 61% said it cost nothing.
Money is rarely the barrier. The hard part is the asking.
Say what's hard in your own words and see what others have asked for, with usual costs and a source on every option, ranked by the same code the live product runs. It happens entirely in your browser: no server, no account, nothing stored, nothing sent.
Everything in this walkthrough is the live product, unedited. The corner label says so on every frame.
Captions are built in. The film works with the sound off, on purpose.
Clips from the film, captions built in. Pick a door, press play.
No login, no account, no name. Four steps, three presses.
Say what's hard in one sentence. See what others have asked for, with usual costs. If you want to ask, it writes the request in your words, and nothing is sent until you clearly say yes.
Every ask arrives as a structured record in Salesforce with a committed answer-by date and an audit trail, instead of a hallway remark that evaporates. One volunteer on the access desk answers.
A cleaner, a picker, a contractor mid-shift can text or call from the most basic phone. No internet, no app, no account. The number lives on a break-room poster.
Wheelchair users fought for curb cuts, and now everyone rolls through them: strollers, suitcases, delivery carts. Build for the people who get left out, and it gets better for everyone.
Every number below is the output of a command in the repository, run against the deployed system.
| 129 | Apex tests, all passing |
| 521 | structural invariants, including the one that fails the build if a diagnosis field ever appears |
| 517 | accessibility checks against the live pages |
| 122 | Sa11y checks with Salesforce's own axe-core matcher, zero WCAG violations |
| 23/23 | adversarial scenarios against the live agent: prompt injection, a manager demanding a roster, a volunteered diagnosis, a hedged yes |
Honest gaps are published too: no daily screen reader user has tested it yet, and the security policy lists the hardening still ahead.
The whole story, written down: the sidewalk in San Francisco where it started, the five rules that came before any code, the doors for the crew who never got a login, and the mango tree. About ten minutes.
The code is free under Apache 2.0 and installs into the Salesforce org you already run. Web and email work with nothing else; text and voice need your own Twilio number and a small relay; Slack installs from a manifest in two minutes. Four settings carry your number, site and mailbox.
What it truly needs is one volunteer willing to be the person on the other end. Technical skill is secondary. If only one thing can be asked of an organisation, it's willingness.
If you run a nonprofit, or your plate is simply full, write to my channels are open and we'll walk the setup in with you. For a good cause, the help is free too.
An Agentforce agent with deterministic Apex deciding what's stored and sent, a headless REST door every channel shares, MCP tools that can never send, an agent-to-agent handover contract, and Twilio voice and text relays. Take it apart, make it better.
Under the workplace words is a pattern: say what's hard in your own words, see real options with sources, send nothing without a clear yes, reach a human always. Swap the library and it fits a food bank's requests, a shelter's intake, a school's parent line. If you serve people who find asking hard, this is yours to reshape.
A chatbot can tell you what an accommodation is. It can't file your request with the desk that has to answer, and it can't promise what happens to your words. Here the AI only talks; deterministic code decides what's stored and sent, and those rules are tested on every change.
Curb Cut doesn't grant anything. It helps a person ask, in their own words. Your access desk still has the conversation and makes the call, and the person gets the date the desk committed to answer by.
There's no field to keep it in, and a build check fails if anyone adds one. Condition words are stripped before anything is saved. Early on, the agent promised not to record a condition while an action saved the words anyway; that's the day every safety rule moved out of instructions and into code.
The code is free, Apache 2.0, and installs into the Salesforce org you already run, so what it stores stays under your roof. The platform under it is licensed, and the guide says so plainly. What it truly needs is one volunteer willing to be the person on the other end. Technical skill is secondary; willingness is the whole requirement.
Not yet someone who uses one every day, and that's the gap we most want to close. The automated checks pass, and a scripted screen reader walk exists, but those can't tell us what a real person finds hard. If that's you, we'd be grateful.