Example · Beginner
Contact form with an honest fallback
A labeled contact form that demonstrates native validation while clearly avoiding a false claim that messages are delivered.
- Author
- Editorial team
- Reviewer
- Publication review pending
- Review tier
- 180-day
What this demonstrates
Each control has a persistent label, useful type, stable name, and browser validation baseline.
Submission contract
The preview deliberately has no action. It does not say a message was sent. A
production version needs a same-origin or disclosed service endpoint, server
validation, abuse protection, retention terms, and accessible error recovery.
Test notes
Try submitting empty fields, an invalid email, and a complete form. The browser should identify missing information without erasing valid values.
Known limitation
Native browser error presentation differs, so a real product may add a tested error summary without removing the native baseline.