Page MenuHomePhabricator

Move field for email address out of address section
Closed, DeclinedPublic

Assigned To
None
Authored By
tmletzko
Feb 28 2018, 3:00 PM
Referenced Files
F22663079: image.png
Jun 26 2018, 7:18 AM
F22663120: image.png
Jun 26 2018, 7:18 AM
F22663094: image.png
Jun 26 2018, 7:18 AM
F17611625: image.png
May 3 2018, 7:49 AM
F14195603: donation-address-form.png
Mar 1 2018, 3:59 PM

Description

We want to break out the email address field out of the address section of the donation form. It is part of the forms for both address types.

Acceptance Criteria

  • The email address field is not present in both address forms (private person, company/institution) anymore.
  • Below the address section of the form, a new section is added.
    • Its headline is "E-Mail-Adresse".
    • The new section is layed out as designed in F22663120 (see below).
    • The field's placeholder attribute is set to "E-Mail-Adresse".
  • The input validation is changed, so that users can provide their email address without providing their postal address and vice-versa.
  • All labels and messages are stored in wmde/fundraising-frontend-content.
  • The datasets are being exported as address type "person".
  • The changed behaviour is part of an a/b test. The behaviour only changes for one test group.

image.png (240×614 px, 17 KB)

Event Timeline

kai.nissen updated the task description. (Show Details)
kai.nissen added a project: WMDE-Design.

As a side note, a comment we received during recent user testing might be related.

kai.nissen triaged this task as Medium priority.Mar 1 2018, 4:06 PM

To make mail and address independent, I treated them as separate sub-sections

It takes a bit more space, but also enables us to add information of what the user gains from adding (or not adding information). If one wants to quickly fill out the form, one still can tab through with the same speed. I assume, since the connections of opt-in to data is more clear, the new structure might actually speed up the process (less misunderstandings and thus evaluation errors of "you need to add…")

image.png (793×705 px, 51 KB)

Though I have not created the mobile view yet I assume the same strategies as for the old form could be applied there (But I'd like to sync myself with a dev, here)

@kai.nissen @tmletzko

separating the email form makes totally sense. Personally, I rather have less dialogue inbetween and some other wording though. Ideally, we have a link to Datenschutz nearby (closer to this email section). The current solution could be improved in that way (but I do not see this as a must-have). I am not sure if the DSGVO has more restrictions for an email opt-in. We might need to put hands on the email section once our internal DSGVO is through with the recommendations.

I'm totally fine with the provided mock-up. @tmletzko Please keep in mind, that a link to the "privacy protection" page is a potential disruption at a very late stage of the process. I would strongly suggest not to put it there (unless DSGVO related requirements require us to do so).

I would strongly suggest not to put it there (unless DSGVO related requirements require us to do so).

I would wait for the DSGVO outcomes, then we could still iterate on the link. Since the new design is modular (2 separate parts) and has more space, I'm convinced we are not worse of and ready for possible DSGVO requirements.

Please keep in mind, that a link to the "privacy protection" page is a potential disruption at a very late stage of the process

@kai.nissen I am aware of that and I did not write it because I am in favor of adding this link. I wrote it because putting the link nearby was a proposal of JBB when we checked opt-in copy from a legal point of view a few years ago. But as I said: this is not a must-have in pre-DSGVO times.

Shall we branch off the DSGVO-link discussion in a separate ticket?

let´s do it once we have the final internal recommendations.

In our recent usability tests, we used this:

image.png (218×625 px, 13 KB)

Our design from the last sprint is this:

image.png (231×633 px, 17 KB)

If the hypothesis is that form fields should go with form fields, the easy change is this:

image.png (240×614 px, 17 KB)

If we want to know if the hypothesis can be supported, we should AB-test the last two against each other.

We need to discuss this one a little bit more.

  1. e-mail serves two aspects: generating an opt-in and to send out a transaction confirmation. Is there a way to separate these two functions in this feature. Either by having two e-mail fields in the adressform and the separated opt-in section (which somehow contradicts the effort here) or to enhance the e-Mail section with the option to receive a transaction confirmation e-mail. The first would leave the adress form as it is now (just without the opt-in copy) and does not have too much tech effort in it, while the latter might have some database or frontend behaviour implications.
  1. as seen in our analysis the position of the opt-in copy is quite relevant. Therefore, we have to consider this in the modification (as already done by Jan in his third option aboce)

To add another idea: We could also add the E-Mail form field to the anonymous section (the part on the right side which becomes visible after choosing anonym). Ok, that would be contradictory to the notion of anonymous donations. But it would come with some advantages:

  • There would not be the need for a separate E-Mail section in the donation form; The E-Mail form fields for private and corporate donations could stay where they are (more or less; they would need to move down to the end of the address section and the opt-in would be places benaeath)
  • Without seperate E-Mail section we would not risk to decrease email-rates from donors with address (private and corporate donations)

but maybe your proposed solution works already (by indicating the importance of the email for receiving the transaction confirmation)

I would not put email in the "anonymous" part, since it is a "hacky" solution and thus hard to maintain and redesign in the future

For the record: We decided to go with the solution to have a separated eMail form with opt-in text below. See:

If the hypothesis is that form fields should go with form fields, the easy change is this:

image.png (240×614 px, 17 KB)

@tmletzko Please check the copy used in the mockup.

apart from the exact copy, @kai.nissen anything FUN-ops has to do before Fun-Tech puts hand on it?

kai.nissen renamed this task from find a solution to accept email adresses only to Move field for email address out of address section.Aug 15 2018, 9:47 AM
kai.nissen updated the task description. (Show Details)