Make a fillable document online that returns answers, not files

A fillable document is a document with places to type: blanks, checkboxes, dates and a signature line. On paper that was one thing. Online it has split into two. A fillable PDF is a file with interactive fields layered over a fixed page; each person fills and returns their own copy. A document-style form is a web page where the text and the input fields are part of the same flowing page; each person submits, and their answers land in one shared table.

The difference matters most after the fiftieth response. Fifty filled PDFs are fifty files to open. Fifty form responses are fifty rows you can filter by date, export to CSV, or push to a spreadsheet as they arrive.

A document form builder lets you write the page the way you would write a document, then drop questions into it. In Zunoform's document layout, the page is a list of blocks: paragraphs, three heading levels, quotes, callouts, dividers and question blocks. Any question type can be a block. Short ones (text, email, number, URL, phone, date and dropdown) can also sit inside a sentence, which gives you fill-in-the-blank forms: "I, [full name], agree to the terms above on [date]."

Conditional logic still works: a question can appear only when an earlier answer calls for it, and hidden questions are skipped. The whole page has one submit button and no welcome or ending pages, because a document is read top to bottom rather than one screen at a time.

Illustration: a climbing gym's one-page waiver has a title, four paragraphs of terms, a name line, a date of birth line, an emergency contact and a signature. As a document form, the title becomes a heading, each paragraph stays a paragraph, and the first line becomes "I, [full name], born [date of birth], have read and accept these terms." with both blanks as inline fields. A yes/no question asks whether the participant is under 18, and logic reveals a parent or guardian name only when the answer is yes. The emergency contact and signature follow as full question blocks. Every submission becomes one row with a timestamp, instead of a scanned page in a folder.

It can be, with care. WCAG 2.2 success criterion 3.3.2 (Level A) requires labels or instructions when content requires user input. In a normal question block the label is visible. An inline blank has no visible label, because the sentence around it acts as the instruction, so give every inline field a clear label in the editor: Zunoform uses it as the field's accessible name, which is what a screen reader announces.

Structure helps too. Document headings are published as real HTML headings and quotes as blockquotes, so screen reader users can jump between sections. Keep inline blanks for short, obvious answers; put anything that needs explanation, such as a medical history question, in its own block with the instruction beside it rather than in a placeholder.

Zunoform fits when you want a readable page with the questions in place and the answers as data: the document layout, inline fields, logic and 500 responses a month are on the free plan, and signature fields need Pro at $14.99 a month.

It is the wrong tool if the PDF itself is the deliverable, for example a government form with a mandated layout; use a PDF form editor. It does not import a PDF and keep its layout, does not generate a signed PDF of the whole document per response, and is not a collaborative word processor. It also does not offer HIPAA agreements, so do not use it for protected health information in the US.