The real cost of ignoring ARIA labels

There is no clever trick in this one, just a handful of decisions worth making deliberately. Nobody bills you for neglecting ARIA labels. The cost shows up somewhere else.

Most of it is correctness rather than charity: use the right element and much of it happens automatically. If two people in the business would answer this differently, that gap is the actual problem.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• No ARIA is better than wrong ARIA
• Rework, once the problem is finally visible

Use it only when native elements cannot do the job. In practice this is a scheduling problem more than a technical one. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

Turning this into a decision

Labels must match what the control actually does. In practice this is a scheduling problem more than a technical one. Check it against what you would want a competitor's site to get wrong.

The short version

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

• Someone can say what the current setup is without going to look
• Use it only when native elements cannot do the job — 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.