Every field must have a visible, descriptive label.

What to do

• Use proper field labels (for example “Email address” or “Department”).
• Do not rely on placeholder text inside fields as the only label.
• Place instructions before the field they relate to.
• Group related questions under clear headings.
• Use plain English and avoid jargon.

Placeholder text disappears when users start typing and may not be read correctly by screen readers.

Users must be able to identify required fields easily.

What to do

• Clearly mark required fields with text such as “Required”.
• Explain at the start how required fields are indicated.
• Do not rely on colour alone (for example, red text or asterisks).
• Avoid making too many fields mandatory.

Error messages should help users correct mistakes quickly.

What to do

• Clearly explain what went wrong.
• Tell users how to fix it.
• Place the error message next to the relevant field.
• Ensure errors are not shown using colour alone.
• Avoid technical language (for example "Enter a valid email address in the format name@example.com" is better than a vague messages like "Invalid input.").

Some users navigate forms using only a keyboard or assistive technology.

What to do

• Test the form using only the Tab key.
• Ensure fields follow a logical order.
• Make sure all buttons and controls can be accessed without a mouse.
• Avoid automatic time limits where possible.

If users cannot complete a form using only a keyboard, it is not fully accessible.

Poorly designed questions can create confusion or barriers.

What to do

• Keep questions short and clear.
• Use consistent response scales.
• Clearly label all answer options.
• Avoid complex matrix or grid-style questions where possible.
• Do not embed important instructions inside images.

After submission, users should know what has happened.

What to do

• Provide a clear confirmation message.
• Explain what will happen next.
• Include contact details if users need help.
• Ensure confirmation messages are easy to read and not hidden in pop-ups.

When using online form builders:

What to do

• Use built-in question types rather than manually formatting content.
• Check colour contrast if using custom themes.
• Avoid adding text inside images.
• Review the form on a mobile device before publishing.
• Use the platform’s accessibility checker if available.

Different platforms handle accessibility differently. Always test before sharing widely.

Some users may still have difficulty completing a form.

What to do

• Provide a contact email or phone number where appropriate.
• Offer alternative formats if requested.
• Avoid stating that the form is the “only way” to respond.