Here it is: uxdesign.cc/the-invisible-layer-of-u...

https://unicornclub.dev

Pretty UIs still break when semantics are missing

If role, name and state aren't there, a screen reader just gets vague buttons and links. Keep coming back to those three lately, catches a lot before handoff

There's a piece in this week's newsletter on role, name and state.

Kinda the invisible layer that decides whether a screen reader gets a proper interface or just vague buttons and links. Out tomorrow.

Vibe coding and genUI keep getting lumped together but they're asking a completely different question. Did the user decide to build this, or did the AI?

Who's making the design call, that matters way more than people think.

Here it is: smashingmagazine.com/2026/03/site-search-para...

Here it is: piccalil.li/blog/applying-accessibil...

I Google other people's sites more than I use their actual search. Half of all visitors apparently do the same thing and just leave when it doesn't speak their language.

Sneaking accessibility fixes into PRs without making it a whole conversation is genuinely the most effective way to get them shipped 🫡

Here it is: www.producttalk.org/ai-changes-everything-an...

"AI changes everything" and "AI changes nothing" aren't in conflict.

The capability floor has moved. Whether you're solving the right problem hasn't.

Here it is: tympanus.net/codrops/2026/03/18/build...

Someone built a gallery-style Webflow site where the 3D scene never reloads between pages.

More of a micro animations person but I found this interesting.

Full piece: nerdy.dev/everything-you-need-to-k...

Scroll entry/exit animations in CSS without intersection observer now.

Adam Argyle covered all the patterns at CSS Day. Properly documented.

Worth a read: css-tricks.com/whats-important-7/

Didn't know CSS had native random() and random-item() functions.

Been thinking about what that does for animation since reading this.

smashingmagazine.com/2026/03/anime-marvel-dc-...

Confetti before a confirmation is the same mistake as a joke in a payment error.

You're competing with the emotional state the user is already in.

Worth a read: www.nngroup.com/articles/genui-buttons-a...

unicornclub.dev/newsletters/2026-03-25-t...

Anime figured out emotional pacing years before product design did.

Most error copy gets written asking whether it's friendly enough. The better question is what state the user is actually in on that screen.

Here it is: cutlefish.substack.com/p/tbm-411-messy-docs-as-...

When you see a team's messy internal docs, instinct makes you wanna organise it.

John Cutler's write up makes a pretty decent case to just leave it alone. Organising it will probably do more harm than good.

This week's newsletter: unicornclub.dev/newsletters/2026-03-25-t...

Anime checks the emotional beat of the scene before writing the character's response.

Most error and confirmation copy gets written first and tuned for friendliness after. Not the same starting point.

Full piece: www.philmorton.co/the-design-to-code-ai-wo...

For me design-to-code doesn't quite have an end-to-end solution or tool that fully closes the loop between your production design system and your design software.

Morton maps it quite well though.

unicornclub.dev

There's a piece in this week's newsletter on why confetti before confirmation is the same mistake as jokes in a payment error.

In the newsletter tomorrow.