Accessible Online Forms: A Practical Checklist

An accessible form lets people understand each question, move through the controls, correct errors, and submit using their available input and assistive technology. A short checklist is a starting point, not proof of accessibility conformance.

Before you publish

1. Give every field a clear visible label. Placeholder text disappears as people type, so it should not be the only explanation.
2. Mark required fields and explain formats before submission. For example, show the expected date format next to the question.
3. Use choices that describe the answer, rather than relying on color or position alone.
4. Navigate the whole form with a keyboard. Check that focus is visible and that controls can be reached in a sensible order.
5. Submit with a required field empty. Check whether the error identifies the field and explains how to fix it.
6. Try a narrow screen and larger text. Check that labels, controls, and the submit button remain usable.
7. Test with a screen reader and ask people who use assistive technology to review the flow when possible.

The W3C explains how form labels connect a question to its control and why validation needs clear feedback. Its preliminary accessibility checks are useful for a first review.

Apply the checklist in Formify

Give each input a descriptive label in the builder, mark genuinely necessary fields as required, and preview the finished form. Run the keyboard and error checks on the published form as well as the preview. For a longer questionnaire, group related questions and test navigation across every page.

If a control or error cannot be used in your test, do not assume the form is accessible because it passed another check. Contact Formify support with the control and steps to reproduce. See also multi-page forms and conditional logic.

FAQ

Is a checklist enough to claim WCAG conformance?

No. A checklist can reveal common problems, but a conformance claim requires a broader evaluation of the relevant pages and interactions.