No certification fluff. No recycled WCAG summaries. Just real-world insights from 25+ years of daily screen reader use.
Subscribe for updatesFeatured article
WCAG 2.2 added 9 new success criteria and removed one. But which ones actually matter for your users? After testing them all with JAWS, NVDA, and VoiceOver, here's what I found actually makes a difference in the real world.
Filter posts by category
The latest NVDA release introduced changes to how it handles ARIA live regions and modal dialogs. If you haven't updated your test workflows, you may be missing real user bugs.
After 40+ accessibility audits, certain ARIA patterns appear again and again — and they're almost always wrong. Here's what to look for and how to fix each one.
The 2024 ADA Title II rule is now in effect for large entities. Here's a plain-language breakdown of what it requires, who it covers, and how to get compliant before your deadline.
WCAG 2.2 SC 2.4.11 and 2.4.12 tightened focus indicator requirements significantly. Most sites I test still haven't updated their CSS — here's exactly what's required.
VoiceOver on iOS behaves differently from desktop screen readers in ways that surprise even experienced accessibility testers. This is the workflow I use for every mobile audit.
The new target size criterion trips up a lot of developers — especially around what counts as "spacing" vs. actual target size. Here's the clearest explanation I can write.
Modal dialogs are one of the most commonly broken UI patterns I test. Focus trapping, role=dialog, aria-modal — here's the complete pattern that actually works with all major screen readers.
Missing labels, broken associations, and vague error messages — form accessibility failures are among the most common and most fixable. This checklist covers everything.
Reading about accessibility is a start. Working with someone who lives it is another level.