Detailed answer
HTML defines controls and a submission request.
A server endpoint or service must process it, validate data, prevent abuse, and produce success or error feedback. Configure action and method deliberately. A mailto action depends on a local mail client and is not a reliable substitute for backend processing.
Example
<form action="/contact" method="post"><label for="message">Message</label><textarea id="message" name="message" required></textarea><button>Send</button></form>
Understanding the behavior
An HTML form collects and submits data to a destination; email delivery requires a server or trusted form service. The action URL must implement that process, including validation, abuse prevention and understandable success or failure responses.
Practical implementation notes
Test delivery to a real controlled inbox after deployment. A success screen alone does not prove that mail arrived, and mailto-based forms depend on the visitor's mail application rather than reliable server delivery.
How to check it
Inspect the real request and backend result, including error cases.
Expected result
Success feedback corresponds to actual processing rather than a timed animation.
Watch out: A frontend success animation does not prove message delivery.
Read the reference ↗