Gravity Forms
+ Fill-in-the-Blank

Some forms read best as a sentence. A membership agreement ("I, ____, would like to join as a ____ member and will pay ____ by ____"), a consent statement, a booking request, a pledge, or a language exercise where the learner fills in the missing word. Gravity Forms puts one input under each label, so a sentence like that turns into a list of separate questions, and the person filling it in never sees the statement they are agreeing to.

The Gravity Forms Fill-in-the-Blank add-on adds a Fill in the Blank field. You write the sentence or paragraph once and put each blank in square brackets: [name], [fee:number], [email:email], [due:date] or [plan:select=Junior|Adult|Family]. On the form, the inputs appear inside the text and wrap with it on a phone. Every blank is its own sub-input with a label for screen readers, its own required flag, placeholder, width and checks: number range, a real e-mail address, a real date in a date range, one of the listed choices or a pattern of your own.

Because each blank is a proper part of the field, the rest of Gravity Forms works per blank: merge tags for the whole filled-in sentence or for one blank, conditional logic that reacts to a single blank, entry columns, the entry screen and the CSV export with one column per blank plus the full sentence. Turn on gap-fill quiz mode to mark each blank against one or more correct answers, with case and space options, points and feedback; the score per field and a total are stored on the entry for merge tags, notifications and conditional logic. Every value is checked and normalised on your server and every score is worked out there; the browser only previews the checks, and the correct answers are never sent to the page. For Gravity Forms 2.9 and newer.

The field keeps your sentence and the settings of each blank. When the form is shown, the server turns the sentence into text with an input in place of each blank, gives every input its own label and links the whole sentence to it as a description, so screen-reader users hear the statement they are completing. When the form is submitted, the server reads each blank on its own, checks it against its type and settings (a number in range, a real e-mail address, a real date, one of the listed choices, your pattern) and stores a cleaned value; a value that does not pass is refused with a message naming the blank. A small script in the page previews the same checks while the visitor types, but the server always decides. In quiz mode the server marks the stored values against your answers after the entry is saved, stores the score per field, the total and the marking per blank on the entry, and never sends the answers to the browser; anything the browser sends about a score is ignored. Each blank keeps its input number when you rewrite the sentence, so older entries stay readable. Everything runs on your own server: the add-on makes no outside request beyond the licence and update checks.