Screen Reader UX, Vertical Slice Architecture, and AI Agents as Users

Published on 15.04.2026

motyl.dev<div></div></>FRONTEND

The Invisible Layer of UX Most Designers Ignore

TLDR: Screen readers translate your UI into a linear stream of announced roles, names, and states. Designers who only think visually are shipping broken experiences to assistive technology users. The fix doesn't require learning to code — it requires thinking in "role, name, state" while you design.

The invisible layer of UX most designers ignore

Minimum Viable Product: Definition

TLDR: An MVP is a structured experiment, not a stripped-down product. The usability of your MVP matters just as much as its functionality — if the interface is confusing, you're testing the wrong thing. Define clear hypotheses before you build anything.

Minimum Viable Product (MVP): Definition

Commercial vs Internal Products

TLDR: Internal products are hard, but commercial products are harder because you have to win in an open marketplace. With an internal product, users can't choose a competitor. With a commercial product, you need to be so much better that people will actively switch from whatever they use today.

Commercial vs Internal Products

Vertical Slice Architecture in Node.js

TLDR: Organize code by use case, not by technical layer. Each feature gets its own folder containing handler, validation, types, and tests. Adding a feature means adding a folder, not touching five different directories.

Vertical Slice Architecture in Node.js

AI Agents as Users

TLDR: AI agents now interact with digital interfaces alongside humans. They have goals, encounter interfaces, and succeed or fail based on how those interfaces are built. Accessibility fundamentals — semantic HTML, clear labels, logical hierarchy — are exactly what agents need too.

AI Agents as Users

Designers Will Never Have Influence Without Understanding How Organizations Learn

TLDR: What teams are shipping via vibe coding aren't prototypes — they're demos. Demos test whether stakeholders like what they see. Prototypes test something you don't know yet. Confusing the two means nothing gets learned.

Designers will never have influence without understanding how organizations learn