New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: improve text for anonymous donation checkbox #3911
Comments
The current line: I think we need to provide two different messages depending on whether comments are enabled. |
From a privacy perspective, I think this can serve multiple purposes and not be only dependent on the comments box. Donations and donor information can be queried in many ways and it would be the path of least resistance to consider this simply as a "consent" checkbox rather than paired only with the Comment field. |
At one point the text was more generic as shown in #3826 (comment). But then the anonymous behavior was changed so that anonymous donations would be displayed publicly by default but without name or comment. At that point the text was changed to be more specific. I'm pointing this out to show that we've already gone from generic to specific language once, and going back to more generic consent language would reintroduce the ambiguity regarding what the checkbox actually does from a donor's perspective. I think this can be solved more simply by making sure we don't mention comments if there is no comment field. |
@DevinWalker and I discussed how to clarify this language. Keeping in mind that the anonymous decision is made per donation, we decided on the following language. The tooltip will be modified based on whether comments are enabled for that form. With comment disabled
With comment enabled
|
Bug Report
User Story
As a donor I don't want to be confused by the anonymous donation checkbox if comments are disabled.
See comments are not enabled but the text mentions a "Comment":
Expected Behavior
Bug Type
2.3.0
.Possible Solution
Related
Related to #3826
Acceptance Criteria
The text was updated successfully, but these errors were encountered: