Fixing Enquiry and Booking Forms That AI Agents Cannot Fill

How an agent decides what a field is for

An agent looking at a form has to answer two questions for every control: what is this, and what should go in it? Browser-driving agents answer mainly from the accessibility tree, which the browser builds from your HTML. For each element it records a role (text box, checkbox, combo box, button), an accessible name (the label), a value and a state (required, invalid, checked, expanded). A screenshot helps the agent, but the tree is where it gets names it can rely on.

The accessible name comes from, in rough order of priority:

1. aria-labelledby, pointing at other text on the page;
2. aria-label, a name written into an attribute;
3. a label element linked by for and id, or wrapping the input;
4. the title attribute, and in some cases the placeholder, as a weak last resort.

If none of these exist, the field has no name. The agent may guess from nearby text on the screenshot, and it will sometimes guess wrongly: putting a phone number in the postcode box, or a message in the name field. Fetch-based tools that read the HTML directly use the same signals plus the name attribute and the input type.

Form patterns that trip agents up

Many of these come from form builders and page builder widgets rather than hand-written code, so check the output HTML rather than the settings screen.

A well-built booking enquiry form

Here is a short enquiry form for a fictional dog grooming salon. It uses nothing unusual, which is the point: plain HTML elements carry everything an agent needs.

<form action="/enquiry" method="post" novalidate>
  <p id="req-note">Fields marked "required" must be filled in.</p>

  <label for="enq-name">Your name (required)</label>
  <input id="enq-name" name="name" autocomplete="name" required aria-describedby="req-note">

  <label for="enq-email">Email address (required)</label>
  <input id="enq-email" name="email" type="email" autocomplete="email" required>

  <label for="enq-dog-size">Size of dog</label>
  <select id="enq-dog-size" name="dog_size">
    <option value="">Choose a size</option>
    <option value="small">Small (under 10 kg)</option>
    <option value="medium">Medium (10 to 25 kg)</option>
    <option value="large">Large (over 25 kg)</option>
  </select>

  <fieldset>
    <legend>Which service do you need?</legend>
    <input type="radio" id="svc-full" name="service" value="full-groom">
    <label for="svc-full">Full groom</label>
    <input type="radio" id="svc-bath" name="service" value="bath-and-brush">
    <label for="svc-bath">Bath and brush</label>
  </fieldset>

  <label for="enq-date">Preferred date</label>
  <input id="enq-date" name="preferred_date" type="date" min="2026-10-01">

  <label for="enq-msg">Anything we should know?</label>
  <textarea id="enq-msg" name="message" rows="4"></textarea>

  <button type="submit">Send enquiry</button>
</form>

Every field has a visible, linked label. The radio buttons sit in a fieldset whose legend is the question, so "Full groom" is understood as an answer to "Which service do you need?". The date uses the native date input, which accepts typed dates and exposes a proper value. The novalidate attribute lets your own error messages, described below, replace the browser's default bubbles; leave it out if you rely on browser validation.

The fix, step by step

Spam protection that does not punish agents

Forms need protection, but some common techniques block exactly the visitors you want. Weigh each one:

• Visible CAPTCHAs. Agents built by reputable providers will not solve them and will hand the task back to the person. That can be acceptable on a form that is attacked constantly, but it should not be the first line of defence on a simple enquiry form.
• Invisible scoring services, such as reCAPTCHA v3 or Cloudflare Turnstile in its non-interactive modes, judge behaviour in the background. Set a sensible threshold and send low-scoring submissions to a review folder instead of rejecting them outright, so you can see if genuine enquiries are being caught.
• Honeypots work well if the field is removed from the accessibility tree as well as from view. A honeypot that screen readers and agents can "see" catches people as well as bots.
• Time-to-submit checks assume that humans are slow. Agents are not, and neither are password managers that fill a form in one go.
• Server-side rate limits per IP address or per email address stop floods without troubling anyone who sends one enquiry.
• Content filtering of the message itself, for example flagging messages full of links, catches a lot of spam after submission without adding any barrier at all.

Form builders and platforms

WordPress form plugins

Contact Form 7, Gravity Forms, WPForms, Fluent Forms and Ninja Forms all produce labelled fields when used as intended, but settings can undo it. Look for options that hide labels and show placeholders instead, "conversational" layouts that show one question at a time, and bundled anti-spam settings with time checks. Gravity Forms and others offer an option to use a native select instead of an enhanced dropdown library; choose the native one where you can.

Shopify

The theme's built-in contact form is usually fine. Problems come from form apps that load inside an iframe from another domain, from product option apps that replace selects with swatches, and from pop-up sign-up forms that cover the page. Check each app's output with the Accessibility pane rather than trusting the app listing.

Embedded third-party forms

Booking systems, CRM forms and survey tools are often embedded in an iframe. Agents can usually work inside an iframe in a browser, but the form's quality is then out of your hands, and fetch-based tools will not see it at all. Where the provider allows it, use their direct link or an embed that renders on your own page, and give the iframe a title that says what it contains.

Stopping regressions

• Test the form with the keyboard alone whenever the form, theme or builder plugin is updated.
• Add an automated accessibility check, such as axe in your test suite or a browser extension, which flags unlabelled fields and missing names.
• Send yourself a test enquiry every month and confirm it arrives, so silent spam filtering is caught quickly.
• Keep a list of field names that your CRM or email integration depends on, so a redesign does not rename them.