WebAble
Field notes

October 28, 2025 · 6 min read

The browser is the most wasted interface on the web.

Why we built into the browser instead of waiting for every site to fix itself, and what changes when you start treating the browser as a platform.

The web is a stack of layers, and the browser is the last one before the user. It’s the only layer that sees every site, every page, every interaction. It’s where the user actually lives. And for most of its history, it’s been treated like a dumb pane of glass: pass through, render, move on.

That’s a strange way to think about the single most-used piece of software on most people’s computers. The browser could be doing a lot more than rendering somebody else’s decisions.

Why we built into it

When we started WebAble, the obvious play was a service-side widget, a script the site owner adds, and it adjusts contrast and font size for end users. Plenty of products do that. The model has known problems: site owners have to opt in, which means most sites never get the fix, which means most users never get the adjustment.

The extension layer flips that. The user opts in once, and every site they touch picks up the adjustments, independent of whether the site owner cared, knew, or was even paid the courtesy of being told. That’s a structurally better deal for the user, and it changes who’s in charge of the experience.

What the browser actually unlocks

  • It sees the DOM. Real elements, not screenshots. That’s a precondition for any honest accessibility adjustment.
  • It has a privileged execution context. CSS, ARIA, focus, scroll, motion: all reachable from a content script.
  • It persists across sites. The user’s preference travels; the site doesn’t.
  • It doesn’t need the publisher to ship anything. The fix lands on day one.

The trade we’re making

Building inside the browser has a cost. Cross-browser packaging is fiddly. Store policies change. Manifest V3 was a year of work nobody wanted to do. None of that goes away, and we still think the trade is worth it. The alternative is asking the open web to fix itself one site at a time, and the open web has had decades of opportunity to do that.

The extension is the front door. The audit and the fix plans help sites improve from the publisher side. But the layer the user controls is the one that can’t be denied to them, and that’s the one we put first.