Why accessible forms matters more than it looks

The gap between knowing this and actually doing it is where most teams lose ground. Accessible forms is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Accessibility work almost always improves the experience for people who have no impairment at all. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

What it costs to ignore

Every input needs a real label element. Where this goes wrong is almost never a lack of knowledge. Budget a little time for it every quarter and it never becomes a project of its own.

Errors must be announced, not only coloured red. It is worth being explicit about, because assumptions differ quietly. If it only works because one person remembers to do something, it does not work yet.

What to watch for

Group related fields so the structure is clear. This is the sort of thing that compounds, quietly, in both directions. It rarely shows up as a line item, which is exactly why it slips.

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
• 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

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.