--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/49/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/49/echoes" issue: 49 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sevda Polat","Sable Whitford"] published: 2026-10-05 updated: 2026-10-01 articles: 15 --- # TinyFish > A journal for living in the agentic age [Read on the website]() ## Issue 49 — Echoes Past infrastructure decisions echoing in today's production realities ### The Interpretability Gap - [Screen Readers Got There First]() — By [Sevda Polat]() · Published 2026-10-01 · Format: The Interpretability Gap Screen readers have spent thirty years extracting structure from pages built for sighted people with mice. Standards bodies, lawsuits, and decades of pressure on developers eventually moved the needle more than better parsing did. Web agents have arrived at the same gap with none of that behind them. After thirty years of coordinated effort, 95.9% of top homepages still fail basic automated checks. ### Semantic Bridge - [The Semantic Layer Nobody Maintained]() — By [Sable Whitford]() · Published 2026-10-01 Around 2005, Ajax let web pages update without reloading, and screen readers lost the plot. Content changed with no signal that anything had happened. The W3C's fix was [ARIA](https://www.w3.org/WAI/standards-guidelines/aria/): attributes developers could attach to HTML elements to declare what they *were* and what *state* they were in. A `div` styled as a button could finally say so. Browsers translated these annotations into an **accessibility tree**, a parallel semantic map of the page that assistive technology consumed instead of raw HTML. ### Occupational Knowledge - [Twenty Years of Filing Bug Reports Against the Web, and the Machines Finally Showed Up to Agree]() — Published 2026-10-01 *The web's accessibility tree is a semantic representation of page content that browsers compute from the DOM. It was built over decades so screen readers could interpret interfaces designed for sighted users. In 2026, it turns out to be the same data structure that AI agents query when they need to understand a web page. The function call `page.accessibility.snapshot()` returns roles, names, and states. Not pixels, not CSS. Almost exactly what a screen reader has consumed for thirty years.* ### Two Eras of Guessing - [The Heuristics of Last Resort]() — By [Sevda Polat]() · Published 2026-10-01 · Format: Two Eras of Guessing When a web interface doesn't declare what its elements are, a screen reader has to guess. Browsers have spent two decades maintaining hand-written rules that infer meaning from indirect evidence: click handlers, styling, proximity. The rules were ingenious and fragile. A declarative vocabulary arrived to make them unnecessary, and a third of the web's form fields still don't use it. - [The Same Absence, Learned]() — By [Sevda Polat]() · Published 2026-10-01 · Format: Two Eras of Guessing Vision models can now read a screenshot and try to work out which elements are clickable, what a button does, where to type. It is the task screen readers faced for decades, attempted with unrecognizably different machinery. On real desktop work, success rates sit near 5%, and when these models miss, there is no rule to open and no set of conditions to enumerate. ### Further Reading - **The Accessibility Gap in Computer Use Agents** — [Source]() — Published 2026-10-01 CHI 2026 study finds AI agents struggle badly when forced to navigate the web through screen readers. - **Standardizing the Accessibility Tree for AI Agents via MCP** — [Source]() — Published 2026-10-01 Proposes unifying the fragmented accessibility APIs that screen readers and AI agents both depend on. - **When AI Assistants Meet Screen Readers** — [Source]() — Published 2026-10-01 LLM-powered guidance helps blind users work around barriers but cannot substitute for actual accessible design. - **From DOS to Subscriptions: The JAWS Screen Reader Timeline** — [Source]() — Published 2026-10-01 Traces JAWS from its 1986 IBM origins through the GUI crisis to its current subscription model. - **Microsoft Active Accessibility and the Origin of the Accessibility Tree** — [Source]() — Published 2026-10-01 The 1997 API that created the semantic layer screen readers and AI agents now share. - **WAI-ARIA: The Stopgap That Became Permanent** — [Source]() — Published 2026-10-01 A W3C specification designed as a temporary fix, now central to how agents parse web interfaces. ### Past Articles - [When the Combinations Outgrew the Room]() — By [Sable Whitford]() · Published 2026-09-24 · Format: Parallel Failure Modes After deregulation, American Airlines carried over 500,000 fares in its reservation system. Every rule made sense on its own. But nobody could predict what the system would do when you changed one, because the interactions between fare classes, routing constraints, and capacity controls across a flight network had outgrown any person's ability to hold them. The fix wasn't better rules. It was a statistical layer that absorbed combinations no human could work through by hand. A different kind of maintenance failure than the one next door, with a similar ending. - [When the List Broke]() — By [Sable Whitford]() · Published 2026-09-24 · Format: Parallel Failure Modes Anti-virus software started with a simple bet: name every known threat, update the list weekly, scan for matches. It worked fine when there were a few hundred viruses. Then new malware samples hit hundreds of thousands a day, and the list became impossible to keep current. The industry had to surround signatures with behavioral detection, reputation scoring, and heuristics — layers that could characterize threats nobody had named yet. A story about what happens when the thing you maintain grows faster than you can update it. - [XCON and the Maintenance Paradox]() — By [Sable Whitford]() · Published 2026-09-24 · Format: Historical Anchor XCON configured VAX computers for Digital Equipment Corporation through the 1980s, hundreds of orders a day, and it worked. Start there. Early on, maintaining it meant teaching it: find the gap, add the knowledge. Years and contributors later, developers were uncertain what some rules did and reluctant to touch them. Digital started a redesign not because the system was failing but because it was getting hard to change. That transition has less to do with expert systems than with what happens whenever encoded knowledge becomes the thing you can't turn off. - [The Chart That Cannot Be Unwritten]() — By [Sevda Polat]() · Published 2026-09-17 · Format: Never Erase A chiropractor recopied a patient's chart after a malpractice complaint arrived. The rewritten version described a patient who had improved and was satisfied. The original, which the patient happened to have copied, described neither. Healthcare learned case by case, and expensively, that altering a clinical record does more than revise the past. It cuts the reasoning out from under decisions other people already made on the strength of it. ## Other sections in Issue 49 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()