A buyer forwarding an editorial brief from a phone often has to enter their name and email before the details of the campaign. A clear visible label identifies each field. A standard autocomplete value can also tell the browser the purpose of a field that collects information about the person filling it in.

W3C’s input-purpose guidance applies to fields collecting information about the user where that purpose is covered by a recognised input-purpose list and the technology supports it. For HTML, name and email are common autocomplete tokens. Keep visible labels in place and distinguish the buyer’s email from fields for a destination URL or a third-party client contact. W3C guidance.

Illustrative example. A betting campaign form asks for the buyer’s work email and the URL of the landing page. The browser may suggest the buyer’s saved email for the first field. The second keeps its own visible label and accepts a URL. Test with a saved profile on a phone and check that the filled values belong to the right fields before submitting.

Agree which details the publisher actually needs for review. Keep the initial enquiry short enough that buyers can finish it between other tasks. Shortlist suitable templates in the publisher inventory, record the checks in the placement brief and apply them to the free article video.