Getting started with ARIA labels
This is one of those topics that looks small until it costs you something. A short on-ramp to ARIA labels for teams who have not touched it before.
The cost of retrofitting accessibility is several times the cost of building it in. Assume whoever inherits this will have half your context and none of your patience.
Why it matters
No ARIA is better than wrong ARIA. Where this goes wrong is almost never a lack of knowledge. The version that survives contact with a real deadline is the simple one.
Your first week
- Find out what is already in place
- Use it only when native elements cannot do the job
- Change one thing and measure it
Labels must match what the control actually does. In practice this is a scheduling problem more than a technical one. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
In practice
Accessibility work almost always improves the experience for people who have no impairment at all. 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.