Mobile Form and Keyboard Audit
Check that phone users can complete long forms.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit a long form on mobile. Fields with their types and labels: [FORM_FIELDS]. Steps and progress indication: [STEPS]. Where users drop off if known: [DROP_OFF]. Check input types and keyboards, autocomplete, label position, error timing, field sizes, date pickers, file uploads, progress indication and saving. Compare each field with whether it is needed. Suggest changes that reduce typing. Return a table with Field, Problem, Mobile fix and Priority, a score from 1 to 10 for effort required, clarity and error recovery, and a test plan using five real phones. Remind me to avoid asking for sensitive data that is not needed [VERIFY]. Add a version of the form with the minimum possible fields. Also check progress saving, the behaviour of the back button, and whether the form can be completed in one hand on a bus. Suggest an alternative path for visitors who prefer to call or message, and where it should appear on the page.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Claude, Gemini, ChatGPT or another assistant.