By Zach Wennstedt, founder of Eye To Ad Media · 2026-09-29
An agent-ready form is a web form that AI agents and assistive technology can understand and complete: every field has a programmatic label, contact fields use standard autocomplete values, buttons have clear names, errors are described in text, and nothing depends on hover or visual-only cues.
Picture your next customer telling an assistant: "Find a roofer who can inspect hail damage this week and book me a time." The agent visits three sites. Two have forms it cannot figure out. One does.
Guess who gets the appointment.
How agents see a form
Agents read the page structure. For each input they look for a label, a name, a type and hints. For each button, they look for text that says what it does. A field with only placeholder text, or a button that is just an icon, is a guess. Agents, like screen readers, do badly with guesses.
The checklist
- Label every field. Use a real <label> element tied to the input, or wrap the input in its label. Placeholder text is not a label.
- Use autocomplete values.
autocomplete="name","tel","email","postal-code"tell software exactly what goes where. - Use the right input types.
type="tel"andtype="email"help both phones and agents. - Name your buttons. "Request a callback" beats a paper-plane icon.
- Write errors in words. "Enter a 10-digit phone number" beats a red outline.
- Ask for less. Every extra field is another chance to fail, for humans and agents alike.
- Keep bots out without locking agents out. Honeypot fields and timing checks stop spam without puzzles that block legitimate assistants.
Good for everyone
Nothing here is new. It is accessibility best practice from WCAG, and it helps people using screen readers, voice control and autofill. Agents just made it urgent.
Paste your page into the machine-readability analyzer: it checks labels, autocomplete hints and button names automatically.