When a customer cannot submit a form, the business can lose a conversation without receiving a complaint. A good form is more than attractive borders. People need to understand what is requested, use a keyboard and correct a mistake without starting again. Accessibility and conversion meet in these practical details.
Ask only for what is needed now
Separate information required for a reply from details that can be collected later. An initial enquiry does not automatically need full billing information. Explain why you need a phone number when the reason is unclear. Mark optional fields and remove questions that do not affect the next step. Fewer fields also mean less data to protect.
Keep labels visible
A placeholder can show an example, but it disappears once typing begins. Every field needs a visible, clear and programmatically associated label. Use appropriate email or telephone input types and autocomplete where suitable. Do not make customers guess a hidden format for information they already know.
Explain errors near the problem
“Invalid data” does not explain what to change. Identify the affected field and provide a concrete instruction without revealing sensitive information about others. A long form can benefit from an error summary linking to relevant fields. Preserve correct entries and do not permanently disable the button after a recoverable error. Check slow server responses too.
Test keyboard use and zoom
Complete the form without a mouse: order should be logical, focus visible and controls usable. Check checkbox labels and touch areas on a phone. Zoom in and confirm that text does not cover buttons. Do not remove focus outlines merely for a cleaner appearance; provide a visible indicator that fits the brand.
Confirm what happened
After submission, explain whether the request was recorded and what follows. Do not show success before server confirmation. Prevent duplicates while allowing a controlled retry after an error. For important actions, customers should know whether they can repeat the operation or must check its status first.
Sources and further reading
A CloudCity editorial guide informed by the documentation below. Check the official source for rules and procedures that may change.
