Part five takes us to page three: detailed applicant information.

At this point, user stamina is already low. The form has demanded attention, patience and emotional resilience. So naturally, page three arrives with around 30 things to do and a fresh basket of UX injuries.

Character limits appear without proper support. The house and street field has a limit, but the user is not shown how many characters remain. Spaces count, but this is not made obvious. Address fields impose constraints without helping users work within them.

Phone number fields are similarly fragile. The form serves an international audience but provides no country code selector or structured support for entering numbers. It also creates ambiguity around whether both phone and mobile numbers are required, because the field labels and tooltip do not seem to agree.

The “same address” checkbox is placed out of flow. It appears before the permanent address section, which makes it harder to understand what it refers to. If checked, it pre-fills some information but not all relevant address details, leaving the user wondering what has and has not been copied.

Then come family details, nationality dropdowns, previous nationality, marital status, spouse details, parent nationality, occupation, employer details and past occupation. Many of these fields suffer from the same pattern: long non-searchable dropdowns, unclear optionality, poorly communicated character limits, vague labels, inconsistent tooltips and unnecessary interruptions.

The more sensitive the information, the more careful the form needs to be. Marital status, family nationality, occupation, military or police history — these are not throwaway fields. They need clear language, appropriate response options, and enough context for users to answer accurately.

Key field notes

• Character limits need to be visible, reasonable and explained.

• International phone fields need structured input support.

• Optional fields should be obviously optional.

• Group related fields in context.

• If information is pre-filled, make sure it is complete and correct.

• Long dropdowns should be searchable.

• Sensitive questions need sensitive answer options and clear guidance.

Best for

Personal information forms, sensitive data collection, address UX, phone input design, dropdowns, form logic.

Background

This piece sits alongside Abi’s wider work on UX, usability and trust because it shows how small interface decisions can create large confidence failures. A complex form is not just a sequence of fields. It is a promise that the organisation can handle sensitive information clearly, safely and competently.

The India visa form is especially useful as a field note because the stakes are high. Users are not casually browsing. They are trying to complete an official task, avoid mistakes, protect personal information and understand what will happen next. Every unclear label, broken interaction, missing explanation or failed recovery path adds doubt.

It also connects to the Corpus view that trust breaks when claims, reality, proof and interface behaviour do not line up. In this case, the form itself becomes the evidence. If the experience is confusing, inaccessible, inconsistent or hard to recover from, the user learns something about the organisation long before they finish the task.

This fifth post focuses on personal information, sensitive questions, character limits, international phone inputs, family details and the repeated punishment of long non-searchable dropdowns.