Why screen readers matters more than it looks

The gap between knowing this and actually doing it is where most teams lose ground. Screen readers is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Accessibility work almost always improves the experience for people who have no impairment at all. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

The reason this keeps coming up

Test with one and the theory becomes obvious. The teams that handle this well are rarely the ones with the biggest budgets. Assume whoever inherits this will have half your context and none of your patience.

Correct markup does most of the work. The teams that handle this well are rarely the ones with the biggest budgets. The version that survives contact with a real deadline is the simple one.

The mistakes we see most

Announced changes need live regions. Getting it slightly wrong is survivable. Ignoring it entirely is not. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

How to tell if yours is fine

Most of it is correctness rather than charity: use the right element and much of it happens automatically. Three things worth confirming about screen readers before you move on:

• Someone can say what the current setup is without going to look
• Correct markup does most of the work — and you know whether that is true here
• There is a way to tell whether the last change to this helped

None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.