Safety about wcag21 HOT 1 CLOSED

I question the value of this SC. Do we really think anyone that is engaged in such activity is going to think ‘gee, this violates WCAG, I really need to change this.’. If a practice is fraudulent, there are mechanisms that consumers can follow to prosecute in many jurisdictions.
If this can be written in such a way that it addressing real-world development practices as opposed to intentionally wrong business practices, then I can get onboard. But that isn’t shown here.

I believe that a better title would be “User Consent”. Some examples that I think COULD be potentially addressed in this basic space:

• Not pre-selecting checkboxes or other mechanisms which introduce a change to the user. User acceptance of new or modified settings or features should be requested after the features are explained, and must require the user’s explicit action to enable.
• The ease of steps to disengage from a system or process should be comparable to the ease of steps to initiate the process. In example, if I can sign up for a newsletter by selecting a single checkbox, I should be able to unsubscribe with the same ease.
  Although the former is potentially about ‘safety’ the latter is not. What they both share is a notion of “User Consent”

from wcag21.