Tutorials·13 June 2026 · 8 min read
My practical accessibility smoke test before release
A ten-minute accessibility pass any QA can run before release — keyboard, focus, contrast, and the obvious screen-reader checks.
accessibilitya11ychecklist
Tutorials·13 June 2026 · 6 min read
Keyboard testing: the fastest accessibility check QA can run
Tab through the page. That single habit catches more accessibility bugs than most automated scans.
accessibilitykeyboarda11y
Tutorials·13 June 2026 · 8 min read
Screen reader testing without pretending to be an expert
Catch the blatant screen-reader failures in fifteen minutes with the reader already on your machine — meaningful names, sensible images, labelled fields, announced changes.
accessibilityscreen-readera11y
Tutorials·13 June 2026 · 8 min read
How to test forms for accessibility
Forms break accessibility hardest — labels, required state, announced errors, focus management, and keyboard-operable custom widgets. The form-specific pass.
accessibilityformsa11y
Case studies·13 June 2026 · 7 min read
The accessibility issue nobody noticed with a mouse
A custom dropdown worked for everyone who tested it — because everyone used a mouse. Keyboard users hit a dead end on a required field. The cheapest check would have caught it.
case-studyaccessibilitya11ybugs
Deep dives·13 June 2026 · 8 min read
Focus order bugs: small issue, big user impact
Focus order is the route a keyboard user takes through your page. When it's wrong the page looks perfect and becomes unusable — and scans don't catch it.
accessibilitya11ykeyboard-testingfocus-management
Tutorials·13 June 2026 · 9 min read
Accessibility test cases for login & checkout flows
Concrete, reusable accessibility cases for the two highest-consequence flows — keyboard completion, labels, announced errors, focus management — where a barrier blocks a core task.
accessibilitya11ytest-casesforms
Opinions·13 June 2026 · 8 min read
Accessibility in pull requests: what's realistic?
Automate the mechanical (axe/lint: alt, labels, contrast) and spot-check the obvious in a PR; route keyboard, focus, and screen-reader testing to QA on a real build.
accessibilitya11ypull-requestsprocess
Tutorials·23 December 2025 · 9 min read
Adding accessibility tests with axe — a practical walkthrough
axe-core is the engine behind most accessibility testing in 2026 — and it's surprisingly approachable. Here's a practical walkthrough of integrating axe with Playwright, what it catches, and what it misses.
accessibilityaxeplaywrighta11y
Opinions·16 December 2025 · 7 min read
Your Lighthouse score isn't an accessibility test
A 100 Lighthouse accessibility score doesn't mean your site is accessible. The score is a smoke alarm — useful, but not a test. Here's what it actually measures, and what you still need to check manually.
accessibilitylighthousea11y