How do I label an optional marketing signup separately from a required form?
Quick answer
Keep the fields and action needed to complete the visitor’s task separate from the marketing choice. Give the marketing control its own plain-language label that says what the person is choosing, and make its optional status clear in words. Do not make it look like a required task field. W3C guidance supports clear labels and asking only for information needed for the task; it does not establish jurisdiction-specific marketing consent rules. [S1] [S2]
The question, the details, the next step.
I have a form people use to request a service update. I also want to offer email marketing signup. How should I separate the two?
Treat the service-update request as the main task and marketing as a separate choice. Put the fields needed to handle the request together, then show the marketing choice as its own control, not as another required task field. Give that control a direct label, for example: “Yes, email me occasional product news and offers (optional).” The label should identify what the person is choosing, rather than relying on a heading or nearby paragraph to explain it. W3C guidance recommends labels or instructions for form controls, including optional controls, and enough information for users to know what is expected. [S1]
What should the labels and submit button say so people don’t confuse the signup with the request?
Use one clear label per control and make the two purposes visibly distinct. For example, the task section might be headed “Request a service update,” with a button labeled “Send request.” Put the marketing choice in a separate section such as “Email updates,” with a checkbox labeled “Yes, send me occasional product news and offers (optional).” Avoid a vague checkbox like “Keep me updated”: it does not say what updates mean. Also avoid button wording such as “Submit and subscribe” if subscribing is not necessary to send the request. Keep instructions brief and place them next to the relevant control. W3C recommends identifying each form control with a label and keeping forms focused on information needed for the process. [S1] [S2]
Can you show me a complete example, including what happens if someone leaves the marketing box unchecked?
Here is a copyable wording example; adjust the bracketed details to match your actual process:
Request a service update [Fields needed to handle the request]
Email updates (optional) [ ] Yes, send me [describe the marketing emails] at [email address used for this request].
[Send request]
In this example, leaving the box unchecked means the visitor has not selected the marketing option; the button still describes the main task. Before publishing, verify that the form actually behaves that way and that the email address and email description are accurate. Do not add promises about frequency, data use, or future choices unless you have confirmed them. The cited accessibility guidance supports understandable labels and limiting questions to those needed for the process; it does not establish what marketing consent must legally include in any particular jurisdiction. [S1] [S2]
What should I check before the form goes live, especially if the form has several steps?
Review the form from the visitor’s point of view, including every step where a choice appears. Check that the task-required fields are clearly tied to the task, the marketing option is a separate control with its own label, and the button wording describes the task rather than implying that marketing signup is required. Confirm that any “optional” wording is accurate in the actual form flow, including on mobile and in confirmation messages. If you use a preselected option or describe how signup works, verify the current practice and get appropriate review for the places you operate; these sources do not settle legal requirements. A useful rule is: if a visitor can complete the task without choosing marketing, make that distinction apparent at the control, not only in fine print. W3C guidance supports clear labels and focused forms, but does not establish jurisdiction-specific marketing consent rules. [S1] [S2]
A practical checklist
Group fields needed for the main task under a task-specific heading.
Give the marketing choice its own control and explicit label describing the emails or updates.
State that the choice is optional when it is genuinely optional in the form flow.
Use button text that names the main task, not a bundled marketing action.
Test the wording and behavior across all form steps and confirm every practice described is accurate.
A few more useful answers
Is adding “optional” to the checkbox label enough?
It helps, but the surrounding layout and form behavior should also make the choice distinct from the main task. Check that the task can actually be completed without selecting marketing.
Can I use one checkbox for both a service request and marketing signup?
That can blur two different choices. Keep the task action and marketing choice separate so the marketing label does not appear to be a condition of completing the request.
Do these accessibility sources tell me exactly what consent wording the law requires?
No. They support clear form labels and focused forms, but do not establish jurisdiction-specific marketing consent requirements. Verify those separately for the relevant locations and practices.
Sources
References used for this guide.
- [S1] Understanding Success Criterion 3.3.2: Labels or Instructions w3.org · Checked
- [S2] Forms Tutorial | Web Accessibility Initiative (WAI) | W3C w3.org · Checked