Echoes
Echoes
The Distance Between Breaking and Fixing
When a browser agent can't click the right date on a booking page, the failure log blames the model. The page was already broken for screen reader users, years before agents existed. Screen readers learned to compensate so well that developers never got the signal to fix anything. Now agents have plugged into the same infrastructure and inherited two decades of unrepaired damage. Each workaround, built by the people closest to the pain, quietly widened the gap between breaking and fixing.
The Distance Between Breaking and Fixing
When a browser agent can't click the right date on a booking page, the failure log blames the model. The page was already broken for screen reader users, years before agents existed. Screen readers learned to compensate so well that developers never got the signal to fix anything. Now agents have plugged into the same infrastructure and inherited two decades of unrepaired damage. Each workaround, built by the people closest to the pain, quietly widened the gap between breaking and fixing.
94.8%
WebAIM Million, 2026: 94.8% of the top million home pages contain detectable accessibility failures. Pages using ARIA average 59.1 errors. Pages without it average 42.
That inversion tells you everything. ARIA lets developers declare accessibility intent. A developer adds a role attribute, nothing visibly breaks, they move on. The screen reader user who hits the wall has no channel back to the person who built it. Twenty-five years of that silence, and the remedy has quietly become the mask.
Fifteen Years of Saying the Same Thing, and Now the Robots Are Listening
CONTINUE READINGFrames and Fixes
The Frame That Wins
When ai.txt was proposed as a successor to robots.txt, two companies signed on. The three that mattered didn't. The proposal was well-designed. It was also a coordination mechanism applied to a power asymmetry. The same pattern shaped RPA governance a few years earlier. In both cases, the winning frame was held by people insulated from the failure it described. That insulation is what keeps the frame in place.
Consequences as Architecture
If voluntary coordination almost never closes a severed feedback loop, what has? HTTPS adoption and GDPR enforcement are the clearest cases, and they share a specific shape: someone occupied a chokepoint, reduced the cost of compliance beforehand, and escalated consequences gradually rather than delivering them as a single absorbable event. Most broken feedback loops lack all three conditions. Most institutions would rather convene a working group.
Further Reading
Past Articles
In 1994, a Netscape engineer built cookies to remember your shopping cart and specifically rejected proposals to turn br...
OAuth was designed to separate identity from authorization. Who you are was one question; what you could do was another....
Every identity mechanism on the web started with a person at a keyboard. When machines needed access, engineers didn't r...
CAPTCHAs were built on an assumption: that something fundamental separates human behavior from machine behavior, and a t...