Three myths about accessible forms

We end up explaining this on discovery calls often enough that it deserved writing down. A few things about accessible forms that get repeated more often than they get checked.

The cost of retrofitting accessibility is several times the cost of building it in. Write the reasoning down alongside the decision, because the reasoning is what changes first.

“It only matters for big sites”

Every input needs a real label element. The teams that handle this well are rarely the ones with the biggest budgets. Budget a little time for it every quarter and it never becomes a project of its own.

“We can deal with it after launch”

Sometimes true, usually expensive. None of that requires a large budget, only a decision and someone to own it.

“Our platform handles it”

Group related fields so the structure is clear. Small and consistent beats large and occasional here. Budget a little time for it every quarter and it never becomes a project of its own.

How to tell if yours is fine

Accessibility work almost always improves the experience for people who have no impairment at all. 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

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