Why accessibility testing matters more than it looks

There is no clever trick in this one, just a handful of decisions worth making deliberately. Accessibility testing 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. Budget a little time for it every quarter and it never becomes a project of its own.

Why it matters

Automated tools catch perhaps a third of real issues. The cost of getting this wrong is rarely visible on the day it happens. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Keyboard-only testing finds problems in minutes. There is a version of this that is over-engineered, and it is worth avoiding. Budget a little time for it every quarter and it never becomes a project of its own.

Warning signs

Testing with disabled users finds what nothing else does. None of that requires a large budget, only a decision and someone to own it. Budget a little time for it every quarter and it never becomes a project of its own.

What this looks like day to day

The cost of retrofitting accessibility is several times the cost of building it in. Three things worth confirming about accessibility testing before you move on:

• Someone can say what the current setup is without going to look
• Automated tools catch perhaps a third of real issues — 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.