What we’re learning.
Short essays on accessibility, product, and the small decisions that make a site usable.
WebAble’s field notes explain the bigger thesis: accessibility is the entry point, adaptive interfaces are the category.
- 00
AI Should Not Just Do Tasks for Us. It Should Help Us Know What to Do Next.
Most AI tools are built around a simple idea: you ask, and the model answers. But what happens when you don't know what to ask? That's where productivity actually breaks down.
- 01
The web breaks in patterns.
Every adjustment a person makes to a webpage is a signal about what the page got wrong. Those signals repeat across unrelated sites, and the repetition is the whole company.
- 02
Audits should be free.
Why the WebAble analyzer doesn't cost anything, and why the rest of the model works because of it.
- 03
The extension is the front door.
How a browser-based accessibility toolkit became the lead surface for a much bigger interaction-assistance platform.
- 04
Automation first. Humans when it matters.
The operating principle behind WebAble's pricing, product, and how we decide when to put a person in the loop.
- 05
Voice isn't a feature. It's an entry point.
Speech-driven interaction gets framed as a productivity gimmick. For a huge slice of the population, it’s the only way the web works.
- 06
The best interface is the one you don’t see.
Why we’re building a layer that sits above the OS instead of yet another app, and what that means for people who never wanted to learn a new tool.
- 07
A second brain isn’t a productivity toy.
The “second brain” movement reframed memory as a productivity hack. We’re building one for the people whose first brain has good days and bad days.
- 08
Calm is an accessibility feature.
The “calm tech” movement is mostly a designer’s aesthetic. For users with cognitive load issues, it’s table stakes.
- 09
The bottleneck isn’t speed. It’s the interface.
Web performance has spent twenty years getting faster. The actual ceiling on what users can do hasn’t moved much, and it isn’t bandwidth.
- 10
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.
- 11
The web was built for the median user.
Standards, frameworks, and design systems all optimize for the same imaginary person, and that person is a smaller share of the audience than anyone wants to admit.