Confirmation message
Show an accurate, accessible result after a submission is stored.
Describe the result that is known
After a 202 response, say that the request was received or stored. Do not claim that an email was delivered or promise a response time that is not operationally supported.
Make the result accessible
Move focus or announce the status through a live region, preserve the message long enough to read, and provide a retry path after errors.
Treat thank-you downloads as separate assets
Do not expose private files through a public confirmation URL. Use a deliberately public asset or a separately authorized download.
Documentation reviewed on October 20, 2026Suggest an improvement →