Before you invest in accessible forms

It comes up on almost every project, usually later than it should. Before you spend anything on accessible forms, it is worth confirming a few things are already true.

Most of it is correctness rather than charity: use the right element and much of it happens automatically. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

Prerequisites

• You can describe the outcome you want in one sentence
• Someone owns it after the work is done
• Every input needs a real label element
• You have a way to tell whether it worked

Where it usually goes wrong

Errors must be announced, not only coloured red. Where this goes wrong is almost never a lack of knowledge. If two people in the business would answer this differently, that gap is the actual problem.

Group related fields so the structure is clear. None of that requires a large budget, only a decision and someone to own it. Assume whoever inherits this will have half your context and none of your patience.

How to tell if yours is fine

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
• Every input needs a real label element — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.