When accessible forms is worth the effort

Teams tend to reach for this after something has already gone wrong. Accessible forms is not free, and pretending otherwise leads to bad decisions.

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.

When it is worth it

Every input needs a real label element. 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.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. Where this goes wrong is almost never a lack of knowledge.

How to decide

Group related fields so the structure is clear. There is a version of this that is over-engineered, and it is worth avoiding. Check it against what you would want a competitor's site to get wrong.

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 accessible forms before you move on:

• Someone can say what the current setup is without going to look
• Errors must be announced, not only coloured red — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.