Questionnaire Markup Builder

How to use Questionnaire Markup Builder

Build a small questionnaire scaffold from structured original questions. Generated native controls receive unique internal IDs, visible labels and direct help references; radio groups use fieldsets and legends. The separate HTML artifact is a useful starting point for implementation, with no form submission, user HTML or accessibility-certification claim.

1. Author a title and 1–30 questions using the documented text, textarea, select, radio or single-checkbox profiles.
2. Give each question a distinct lowercase ASCII ID, a visible label and any original help or choices.
3. Download the scaffold and test keyboard, assistive technology, validation and eventual submission handling in your real integration.

Good to know

• At most 100,000 well-formed JSON characters, 30 questions, 20 options per choice question and 150 actual native controls. Title at most 160 characters, description 1,000, labels 200, help 500 and choice values 100. Unknown object keys and duplicate JSON members are refused. Downloaded document text refuses control characters other than tabs and line endings.
• IDs use a lowercase ASCII letter followed by at most 31 lowercase letters/digits/hyphens. They remain control names; generated internal DOM IDs use separate numeric indices to avoid help/option collisions. required must be a JSON boolean. Choice values are distinct and nonblank.
• Supported types are text, textarea, select, radio and one boolean checkbox. Only select/radio accept options. Radio required applies to its native group. This profile has no custom constraints, conditional branches, uploads, custom attributes, raw markup, scripts or external resources.
• The artifact uses a section rather than a form, and contains no action, submit control or handler. It does not collect or transmit responses. Native controls are editable locally, but storage/submission/error handling and complete accessibility behavior require a separate tested implementation. No WCAG conformance or legal compliance is certified.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.