Accessible forms: the questions we get asked most

The gap between knowing this and actually doing it is where most teams lose ground. The questions about accessible forms that come up most often on our calls.

The cost of retrofitting accessibility is several times the cost of building it in. The version that survives contact with a real deadline is the simple one.

Do we need to care about this?

Every input needs a real label element. There is a version of this that is over-engineered, and it is worth avoiding. It rarely shows up as a line item, which is exactly why it slips.

Can it wait until after launch?

Occasionally. More often the post-launch version costs several times the pre-launch one. In practice this is a scheduling problem more than a technical one.

How do we know it is working?

Group related fields so the structure is clear. None of that requires a large budget, only a decision and someone to own it. If two people in the business would answer this differently, that gap is the actual problem.

In practice

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
• Group related fields so the structure is clear — 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.