10 min read
Screen reader testing in 20 minutes
Most developers have never used a screen reader on their own site. Twenty minutes of actual use finds more accessibility issues than most automated audits. Here is the practical version, in detail.
Blog posts.
All posts
8 posts shown.
- 3 min read
prefers-reduced-motion: what it doesn't solve
Adding the media query is necessary and not sufficient. Here's what it covers, what it doesn't, and what you still have to design around.
- 3 min read
The overlay industry is selling compliance as a product
A line of JavaScript on your site promises to make it accessible. It doesn't. It sells your legal exposure down for a fee, and leaves actual disabled users worse off than before.
- 4 min read
AI alt text: what it still can't do
Every time a new multimodal model ships, someone claims alt text is solved. It isn't, and the reason is structural, not a matter of model quality.
- 3 min read
EN 301 549 compliance is a floor, not a ceiling
A product can pass a WCAG audit and still be unusable. Compliance is the legal minimum. Real accessibility lives on the other side of it.
- 3 min read
Focus management in SPAs: the actual rules
React, Next, Vue, and SvelteKit all ship focus management broken by default. Here's what to fix and why the frameworks haven't done it for you.
- 3 min read
The cognitive accessibility nobody talks about
WCAG has thin guidance on cognitive load. The population it serves is the largest of any disability axis. The guidance gap is not an accident.
- 3 min read
Keyboard-only users aren't edge cases
The stereotype of the keyboard-only user is a blind person with a screen reader. That user exists and matters. They are not most of the people who rely on keyboard navigation.