Writing on front-end development, accessibility, performance, and the craft of building for the web.
The W3C Community Group published a Design Token spec that standardizes how tokens are expressed in JSON. Style Dictionary v4 adopted it — and it's a breaking change from v3.
Read article →After auditing accessibility on large enterprise codebases, the same failures appear every time. Here's the list — with the WCAG criterion, the real impact, and the fix.
Read article →toDataURL() blocks the main thread. toBlob() is async, integrates with the File API, and produces a proper binary Blob — use it for anything the user will download or share.
Read article →The Chrome UX Report API returns 28 days of real-world performance data for any sufficiently-trafficked public domain — no API key, no account, just a POST request.
Read article →Setting scrub: true ties animation directly to the scroll position with no smoothing — which sounds great until you realize what it does to mobile frame budgets.
Read article →Removing the browser focus ring without replacing it is one of the most common accessibility violations on production sites. Here's the right pattern.
Read article →You don't need to run a dev server to share a Storybook. One build command produces a static HTML/JS bundle you can deploy to any host — Netlify, GitHub Pages, S3.
Read article →CSS custom properties are powerful, but they're a delivery mechanism, not a system. Design tokens give you a source of truth that generates CSS, JS, and TypeScript from a single spec-compliant file.
Read article →Accessibility is not a feature — it's a foundation. Here's how to build React components that work for everyone from day one, with real code patterns you can use today.
Read article →
