01 — The Problem
A tech watch tool that anyone can use — really.
Most resource management tools are either too complex, inaccessible, or dependent on heavy tech stacks. TAKTO was born from a simple conviction: a tool for organizing and sharing web resources should work for everyone — whether you use a screen reader, navigate by keyboard, have a slow connection, or simply prefer not to run JavaScript.
02 — Design Approach
Constraint 01
Minimal by principle, not by trend.
The design started from zero assumptions. No heavy framework, no imposed visual system. Every element had to justify its presence. The result: a two-column layout — fixed sidebar, scrollable content — that works identically in light and dark mode, with a favicon that adapts dynamically to the active theme.
High contrast ratios were non-negotiable from day one, not as an afterthought.
Constraint 02
Accessible by design, not by compliance.
Every interaction was designed to work without a mouse. Full keyboard navigation (Tab, Enter, Space), ARIA roles and labels throughout, semantic HTML structure, and compatibility with major screen readers — VoiceOver, NVDA, JAWS.
The app also functions entirely without JavaScript. The sidebar becomes static, the theme defaults to system preference, and every core feature remains accessible. This wasn't a fallback — it was a design requirement.
03 — Key Decisions
Why no framework. Why no server. Why no compromise.
Static over complex
A pure HTML/CSS/JS app means zero dependencies, instant load, and no build step. Anyone can open index.html in a browser and it works — including on a 10-year-old laptop with a 3G connection.
localStorage — privacy first
No server, no account, no data leaving the device. Your links stay yours. Export to JSON if you want to move them. This is a deliberate product decision, not a technical limitation.
PWA — offline by default
A service worker caches the app on first load. After that, TAKTO works offline. Add it to your home screen, open it on the train — it just works.
04 — Result