Safety and Deception Requirements #348
Conversation
Need to mark requirements as foundational or supplemental. Need to add assertions.
✅ Deploy Preview for wcag3 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for wcag3-howtos canceled.
|
guidelines/groups/process-and-task-completion/avoid-deception.md
Outdated
Show resolved
Hide resolved
| - no-sneaking | ||
| - no-emotionally-misleading-designs | ||
| - no-misdirection | ||
| - no-nagging | ||
| --- | ||
|
|
||
| Users do not encounter deception when completing tasks, unless essential to the task. |
There was a problem hiding this comment.
Looking back on this and thinking about this from both sides of the screen, I would like to expand on this a lot more than what it is worded as, for the current wording to me can appear as, "Well, we can deceive users and just say it is essential to the task for completion." I think what we currently have here can be exploited by organizations and/or individuals even further and they can use this as a loophole to get around using a deceptive pattern (or even an anti-pattern).
"Users do not, and should not encounter [term]deceptive patterns, [term]anti-patterns, or deception of any kind to complete a task the user has set forth for themselves or is essential to completing a task to proceed in an interaction (form submission, email signup, etc.)."
Or something similar to that effect. I think if we expand on this a bit further and close that potential loophole, this would satisfy my hesitation to proceed.
I have added both terms to the Shared Glossary and would like to see these terms somewhere in the guidelines at some point as a reference in the future for people, regarding what we have built here.
Need to mark requirements as foundational or supplemental. Need to add assertions.