Echoes
Echoes
The Part of the Form That Stayed in the Office
When the HTML Working Group specified web forms in 1995, it translated the structure of paper forms with real fidelity: labeled fields, a destination, a method of delivery. What it did not translate was the institutional context that made paper forms work — who was authorized to fill one out, whether submitting it committed you to anything, what recourse you had when something went wrong. That context lived in the office, in the clerk, in the fine print on the back of the page. It was never encoded. Now automated agents are filling these same structures at scale, and the absence has started to matter.
The Part of the Form That Stayed in the Office
When the HTML Working Group specified web forms in 1995, it translated the structure of paper forms with real fidelity: labeled fields, a destination, a method of delivery. What it did not translate was the institutional context that made paper forms work — who was authorized to fill one out, whether submitting it committed you to anything, what recourse you had when something went wrong. That context lived in the office, in the clerk, in the fine print on the back of the page. It was never encoded. Now automated agents are filling these same structures at scale, and the absence has started to matter.
The Required Field
On a paper form, a blank required field started a conversation. The clerk noticed the gap, picked up the phone, asked what you meant. The asterisk marked where attention was needed, but the clerk supplied the judgment — deciding whether an answer was missing, wrong, or simply unclear.
HTML5's required attribute, finalized in 2014, kept the first check and quietly discarded the rest. Its constraint fires on exactly one condition: the field is empty. The violation is called valueMissing. Any non-empty string clears it. The institution's demand for completeness survived; its capacity to distinguish completeness from plausibility did not.
When an agent encounters a required field without a known answer, it infers one from the label and surrounding context. The form submits. The specification cannot distinguish a value that was known from one that was guessed. We automated the symbol of institutional diligence while stripping away the diligence itself — and now we're surprised that systems built to fill in blanks are very good at filling in blanks.
Two Lineages of Form Design
What the Census Form Could See
Before 2000, a census write-in of "Black-White" was assigned to Black. "White-Black" was assigned to White. The rule was consistent, defensible, and entirely invisible to the person it classified. Census categories determine which populations a country is equipped to perceive. A fifty-year-old design decision has finally been reversed. The statistical infrastructure it produced will outlast it by a decade.
The Dropdown Menu
Before the web dropdown, a clerk with a 30,000-entry index translated what you wrote into what the system could accept. The compression was lossy but intelligent — the clerk knew things about the world the index did not contain. The dropdown removed that interpreter. It worked partly because the humans on both sides understood what was being given up. What happens when the thing filling the form has no such understanding, and picks an option anyway?
Further Reading on Forms
