WebAble started as a browser extension. Reading mode, high contrast, dyslexia font, click-target enlargement, tooltip pinning, sticky-bar killer, voice control, image alt text: the kind of toolkit a user with a real accessibility need installs once and then forgets is there. We shipped 17 deterministic tools and three AI ones, scoped them across vision, reading, motor, cognitive, and privacy, and gave it away for free.
We could've stopped there. A free accessibility extension is a respectable product. But the extension wasn't the whole idea. It was the entry point.
What the extension actually proves
Every tool inside the extension is a piece of evidence. It says: the web doesn't need permission from a site to become more usable. The user can carry their own accessibility layer across every site they visit. Reading mode strips clutter on any page. Voice control drives any UI. The site doesn't have to know.
That's a small statement and a big one. Small because it's technically true and the prototypes work. Big because it inverts how accessibility is usually treated: as something the website owner provides for the visitor. WebAble treats it as something the visitor brings with them.
The longer arc
The browser is the first surface, not the only one. Behind the extension we're building:
- ClarityView: the reformat-and-focus surface, standalone
- EchoControl: voice control across any interface, not just browser tabs
- AutoFlow: teach it a task once, replay it on demand
- AbleMind: the memory core that learns user patterns over time
- GlassLayer: an OS-level assistant that floats above every app
All of these share the same underlying capability stack and the same accessibility-focused model we're developing in-house. The plugin is step one. Anything with a display and an OS is the long game.
Why not push everything at once
Because launches that try to push a six-product portfolio on day one mostly fail. Each surface needs its own quiet phase: pilot users, edge cases, the kind of feedback you can only get when someone actually relies on the thing. We'd rather earn the right to the next surface than ship a deck full of "coming soon" tiles.
So the extension is the front door. It's the only public-beta surface today. The rest exist, but they're behind early-access waitlists at /ecosystem. If you want in on a specific one, that's where the form is.
The business side rhymes
The same logic shows up in the B2B model. The audit at /analyzer is the front door: free, fast, honest. Paid plans live downstream of it. Most teams who run the scan never become customers, and that's fine. The free surface earns the right for the paid one to exist.
Front doors look small from the outside. They're what the rest of the building hangs off of.