Actually respecting prefers-reduced-motion
How to respect prefers-reduced-motion across a full animation system, with a live comparison.
Quality guides
Motion preferences, keyboard behaviour, native scrolling, resilient forms, and software built to last.
Accessibility and performance are properties of the whole system, not a checklist added before launch. These guides show the small implementation choices that keep interfaces usable under different inputs, preferences, and network conditions.
They also explain the tradeoffs behind choosing native browser behaviour and established tools when a more fashionable option would make the experience less reliable.
How to respect prefers-reduced-motion across a full animation system, with a live comparison.
The three things a mobile nav overlay has to get right that most tutorials skip. Tap the icon below, then try pressing Escape.
Scroll hijacking is the reason your arrow keys and Page Down "randomly stop working" on some sites. Feel the difference between the two below.
The honeypot field we actually ship instead — invisible to you, irresistible to a bot.
Why we default to boring, well-worn tools instead of whatever launched on Twitter last week — and the one time we don't.
A practical buyer's guide to the Equality Act, WCAG, reasonable adjustments, procurement, testing and maintaining an accessible website.
Understand LCP, INP and CLS, the difference between field and lab data, commercial symptoms, priorities and questions for your web team.
A buyer's acceptance checklist for rendering, crawlability, metadata, redirects, structured data, performance, measurement and handover.
On a dark interface, the difference between readable and legally inadequate is invisible to the person choosing the colour.