Here is the thing that surprised me most once WebAble was in real hands: people don’t reach for accessibility tools because they identify as disabled. They reach for them because the web is annoying.
They bump up text size because the body copy is 13px gray-on-gray. They kill the sticky header because it eats a third of the screen. They flip on reading mode because the article is buried under three newsletter popups and a chat widget. They ask the page a question because the answer is somewhere in 2,000 words and they don’t have the patience. None of those people would call themselves the target user for an “accessibility extension.” They’re just tired of friction.
That reframed the whole company for me. WebAble isn’t an accessibility tool that happens to be useful to everyone. It’s a web-interaction layer where accessibility is the sharpest, most underserved edge. Same tools, much bigger door.
The adjustment is the signal
Every time someone enlarges text, hides a sticky bar, turns on reading mode, asks a page a question, or pulls text out of an image, they’re doing something more interesting than fixing their own moment. They’re pointing at a place the website got the experience wrong.
One person doing it is a preference. A thousand people doing the same thing on the same kind of page is a defect report the website never knew it received. And the most valuable signal isn’t which tools people say they want. It’s the adjustments they make over and over, on completely unrelated sites, without being asked. Those repeated adjustments are the web quietly telling us what it should have supported natively.
The loop
Lay that end to end and it stops being a feature and starts being a flywheel:
- A user adjusts a page to make it usable.
- WebAble notices the adjustment, and notices it repeating across sites.
- The pattern becomes a sharper tool, a better audit check, and a known fix.
- A website owner runs the audit and ships that fix at the source.
- The next site that has the same problem gets fixed faster, because the pattern is already understood.
The consumer side reveals the need. The business side fixes the source. The data that connects them is the friction itself, not the person.
The button I keep coming back to
The cleanest version of this signal is intentional. A small control, always one click away:
Report this page as hard to use.
Then a short, honest menu: hard to read, hard to see, hard to click, too much noise, image text I can’t get to, form is broken or confusing. Optionally, “share the anonymized page structure to help improve the web.” That’s deliberate, consented, high-signal data about where the web breaks, contributed by the person who hit the wall, on purpose.
Patterns, not identity
I want to be exact about this part, because it’s the part that’s easy to do badly. WebAble learns from user-side adjustments, not from private user identity. We care about what got stuck and what fixed it, not who you are. We don’t need passwords, private messages, payment details, or the sensitive contents of a page to understand that a sticky bar is in the way or a button is too small.
So the rules are simple, and they come first:
- The core tools are free and stay private. Using WebAble never requires sharing anything.
- Any data program is separate, explicit, and opt-in. It is never the default behavior of the extension.
- What’s interesting is the friction pattern: which tool was activated, on what kind of page, whether the change was kept or reversed, whether it helped. Not your browsing identity.
- Anything richer (interaction trails, redacted clips) is gated behind its own clear consent, with aggressive redaction before anything leaves the device.
Down the road there’s a version where people who opt into deeper research programs get compensated for the contribution, because their input genuinely makes the web better and their time is worth something. But that’s a future, opt-in research panel with real consent, not a default, and not the pitch. We’ll be transparent about it when it exists. Until then, the only promise that matters is the first one: the tools work, for free, without taking anything from you.
Why this is the company, not a side quest
Most analytics tools watch one website and ask “how do we keep people on this page longer.” The interesting question is the opposite one, asked across the whole web: what do people keep having to fix themselves, everywhere, and what would it take to never have to fix it again?
Answer that with real signal and you don’t just have an extension or an audit tool. You have a live, growing map of where the web fails humans, and a system that turns that map into permanent fixes. The web breaks in patterns. We’re building the thing that reads them.