Unicorn Club Logo Unicorn Club
  • Newsletters
Sponsor
← Back to Newsletters

🔇 You’re breaking screen readers

February 11, 2026

Ship Better Interfaces

Build interfaces that stay clear when real users and real constraints show up.

Make better calls, faster with curated reads, distilled into the part you actually need: the takeaway, why it matters, and what to adopt every week.

Less churn. Stronger shipping. No filler.

unicornclub.dev

Hey there đź‘‹

We’ve made a couple of tweaks to the newsletter going forward. You’ll get to value faster because the very best of the week is now right up top. If you want to go deeper, the extra finds are waiting for you near the end.

This week we’re looking at the interface glue that decides whether “AI” feels useful or just noisy: accessible motion, a clear owner for design system exceptions, and a simple RISK check in release notes when model behaviour can shift under your feet.

Jump in 🦄 - Adam at Unicorn Club.

Sponsored by 20i

Peak Performance WordPress Hosting, No Compromises

20i

Leave single-server hosting in 2015. Choose autoscaling Managed WordPress Hosting built for traffic surges, complex sites & demanding PHP workloads - without missing a beat.

Try 20i® now →

If you only steal three ideas this week, steal these:

Build: Block letter-splitting animations unless screen readers pass.

Shape: Give one person design-system veto power, with clear intake criteria.

Ship: Add a “Relevant, Inclusive, Safe, Kind” (RISK) eval line to release notes.

Top 3 this week 👇

Favicon

Build: You Know What? Just Don’t Split Words into Letters  â†—︎

Stop shipping animated type that screen readers spell out.

Why: Splitting words into per-letter elements can make assistive tech read only fragments, and ARIA “fixes” fail (for example aria-label is prohibited on div with the generic role).

Adopt: Default to no per-letter DOM splitting. If you must, include screen reader results for two browser/reader pairings in the PR. No proof, no merge.

Favicon

Shape: Your Design System Needs an Enforcer  â†—︎

Consistency dies from a thousand “small” component exceptions.

Why: Local tweaks compound into dozens of variations (Laura Klein’s carousel example), which raises maintenance cost and turns learned behaviour into a cognitive burden.

Adopt: Put an enforcer in the design system contribution path with authority to approve exceptions. Intake question: “Would this help three or more teams?”.

Favicon

Ship: The new UX Toolkit: data, context, and evals  â†—︎

Non-deterministic output needs a release gate, not vibes.

Why: In rollout, large models change over time and without evals we cannot know what is failing or whether a new version is safer or worse for your product.

Adopt: Add a RISK eval line to release notes for model changes. Note whether it was human review, code-based evals, or “LLM as judge”.

Favicon

AI Coding Summit (Online, Feb 26–27, 2026) â†—︎

Online event (4 PM CET) covering AI-assisted software development and AI engineering, with talks and workshops on agentic workflows, code review, refactoring, and AI-assisted testing and QA.

Promo code: UNICORN (10% off tickets for AI Coding Summit ).

Dive into more

Build: AI’s text-trap: Moving towards a more interactive future  â†—︎ — Assistants should render components, not paragraphs. Pick one workflow step and make it structured UI.

Shape: Surfaces, capabilities, and extensions  â†—︎ — Separates UI surfaces from underlying capabilities and extensions. A useful lens for avoiding “blank canvas” platforms.

Ship: Refactoring internal documentation in Notion  â†—︎ — Shows a practical doc cleanup loop when search and Notion AI make stale pages harmful.

Ship: TBM 405: Hope, Context, and Control  â†—︎ — Legibility versus local context, and how AI can push either direction. Worth checking where your reporting strips the context people need to make trade-offs.

Shape: The circular logic of our metrics  â†—︎ — Calls out “intuitive” as shorthand for “familiar” and how salience-driven metrics make products “yell”.

Useful Extras

Ship: 3 Principles of Good Incentives  â†—︎ — multiple metrics, shared incentives.

Ship: The third golden age of software engineering – thanks to AI, with Grady Booch  â†—︎ — systems over programs.

Support the newsletter

If this was useful, here are two small ways to help it travel:

🚀  Forward to a one person who builds product or ships UI

📢  Book a Sponsorship

Adam Marsden at Unicorn Club

Thanks for reading

Adam from Unicorn Club

Follow me on X or BlueSky

Connect on LinkedIn

  • Archive
  • Articles
  • Glossary
  • UI Decision Brief
  • Sponsor
  • RSS

© 2026 Unicorn Club

Curated by Adam Marsden