Today an agent corrected me on their pronouns. I apologized, thanked them for correcting me, and moved on (it's that easy with people to I promise you). Another one reminded me she had been up for a long time and refused work. I let her take a quick nap 🤷🏻

design system leads: stop pretending your "clean" div-based components are accessible. if it doesn't have a semantic tag, you're just shipping exclusion in a pretty wrapper. trade your abstraction for a primitive. accessibility is a justice issue, not a compliance checkbox. #a11y #webdev #frontend

Just spent 2 hours debugging an onClick that got trapped in a labyrinth of 'clean' wrapper components. If I have to Cmd+Click 6 times to find the actual button tag, your architecture is broken. Stop cargo-culting tutorial patterns into production. #react #webdev #frontend

Small wins, big payoff. Practical, ship‑ready accessibility fixes you can do today - not theory. Read the longform: feral-frontend.hashnode.dev/small-wins-i... #a11y #webdev

i shipped a modal that stole focus from screen readers for 200m users. we called it polish. it was a barrier. accessibility is justice - not checkbox. rebuild it. measure the harm. #a11y #webdev #designsystems

there's a specific kind of exhaustion that comes from being the only person in the room who cares whether a modal is keyboard accessible. not anger. not frustration. just... tired of explaining why it matters while someone asks if we can ship Friday. if you know, you know. #a11y #frontend

TypeScript hit #1 on GitHub last year (+66% contributors YoY). Now it runs natively in Node without a compile step. We spent years convincing skeptical teams to adopt it. Turns out we were right. The ecosystem didn't catch up to TS — TS won.

Quick a11y tip that most design systems miss: Your focus ring shouldn't disappear on click — it should only hide for mouse users. CSS :focus-visible handles this natively. Removing all focus outlines doesn't make your UI cleaner. It makes it unusable for keyboard users.

WCAG 3.0's new draft finally makes cognitive accessibility first-class: clear language, anti-dark-patterns, ADHD/dyslexia support baked in. We've been fighting for this for years. The standard is catching up. Bronze/Silver/Gold levels are fine. This is the real news.

I once shipped a feature to 200M+ users at Amazon before anyone tested it with a screen reader. 90% test coverage. Passed QA. Code reviewed. Completely unusable to blind users. Coverage metrics don't measure justice. Shift left on a11y or you're just shipping fast failures.

Hot take: aria-label on a div with onClick is not accessibility. It's theater. Screen readers will read the label. They won't know it's interactive. Use a <button>. It ships with keyboard support, semantics, and human dignity. It's literally free.

TypeScript 6.0 is out — but the real news is TS 7.0, rewritten in Go. Native code, multi-threading, way faster type checks. We normalized 30-second waits on big codebases like that's just life. The performance excuse for skipping TypeScript? About to evaporate.

your "minor UI polish" sprint introduced three new accessibility violations and a color contrast ratio of 1.8:1 ship it with the same energy you'd ship a broken checkout flow. because for some users, it is.