Mlola builds a UI system that solves accessibility instead of hoping for it, and a browser runtime that proves its work. Every claim is checked, most of them by a machine.
npx mlola-ui add button card✓ Added components/ui/button.tsx✓ Added components/ui/card.tsxnpx @mlola/browser-cli browser run --goal "Download the file hello-1.3.tar.gz" --url https://ftp.gnu.org/gnu/hello/→ NAVIGATE https://ftp.gnu.org/gnu/hello/ ⤓ downloaded hello-1.3.tar.gz ✔ verified: download evidence: 1 event(s), 1 artifactrun completed — verification verified · steps 2 in 3.5s
Products
Each one does one job completely, and shows its work.
UI system
Components for AI-native products on native CSS tokens. The theme engine solves contrast for every palette, and the code is copied into your project, so you own it.
Browser automation
Real browser tasks without a frontier model on every click. Mechanics, safety, verification and recovery are deterministic; a model is asked only for judgement.
How we build
The same rules hold in every product, and most of them are checked by a machine on every change.
When a product says it does something, a test, an audit or a verified run shows it. What cannot be shown is not said.
Safety, contrast and verification are code with known behavior. A model is asked for judgement, never given the last word.
Keyboard, screen readers, reduced motion, forced colors and both color modes are part of done, not a later pass.
Source you can read and keep, local-first by default, and no lock-in you did not choose.