Page MenuHomePhabricator

Design: Determine UX for Enabling/Disabling Password Reset Update via Preferences
Closed, ResolvedPublic

Description

As a PM, I want to know the location and design requirements for the password reset button (in Preferences), so that I can write a ticket for engineers to implement this change.

Acceptance Criteria:
• Provide a mock-up that specifically locates where the password reset option should be located in Preferences
• Include the suggested wording for users (regarding this preference)
• Provide a visual display of the preference when it is both enabled and disabled

Event Timeline

ifried renamed this task from Design: Determine UX for Enabling/Disabling Password Reset Update to Design: Determine UX for Enabling/Disabling Password Reset Update via Preferences.Aug 29 2019, 4:27 PM

The way to enable/disable this preference would be a checkbox in Special:Preferences. It'll only show up if the user has confirmed their email. I can think of two places where this setting could be:

Basic InformationEmail Options
Screenshot 2019-09-09 at 9.47.21 PM.png (908×1 px, 346 KB)
Screenshot 2019-09-09 at 9.47.30 PM.png (906×1 px, 397 KB)

We could run a small usability test to see where users tend to look for it.

@Prtksxna Thanks for presenting examples of these two options! Yes, I think we could potentially run a usability test. I agree that it can be small in scale. If we were to run a test, how do you suggest we do this/organize this? We can also discuss this in our meeting.

Note that the existing messages include a help paragraph underneath (or in a popup/hover, in some skins I think):

requireemail.png (107×741 px, 11 KB)
Is this to be removed?

Note that the existing messages include a help paragraph underneath (or in a popup/hover, in some skins I think)

Thanks for sharing this @Samwilson, but, I don't follow, where this is from 😅Why is this message already part of system? Has this been implemented before?

Is this to be removed?

No, not yet. We're running some usability tests to figure out what position and messaging makes sense, and I think having help text might be useful 😊

It was added in T231495, and is only visible if the feature flag $wgAllowRequiringEmailForResets is true (i.e. it's never visible, and doesn't do anything).

Ah, that makes sense. I think lets keep it as is for now and figure out what needs to be done once we have results back from the usability tests.

Through the usability tests, we found that this preference should probably be turned on/off in the Password section (rather than the Email Settings section). This was because users found it easier to locate in this section. When you get a chance, @Prtksxna, it would be great if we could get a mock-up by Estimation on Thursday.

Based on the usability tests and feedback from the design team we've decided to keep this setting as the first checkbox in the Email Options section. We might add some text in the Basic Information section but from what I understand we'll have to check if that is possible.

Provide a mock-up that specifically locates where the password reset option should be located in Preferences

See F30282774 for position (not wording)

Include the suggested wording for users (regarding this preference)

TextRequire both email address and username to reset password.
Sub-textIf checked, the password reset email for this account will be sent only when both email address and username are provided in the reset form.

Provide a visual display of the preference when it is both enabled and disabled

(this would be a normal checkbox, like all others on the prefs page)

Thanks, @Prtksxna! Can you provide an explanation of the sub-text? When/how do you propose that it is displayed? I have also started writing a basic ticket here: T234537

Thanks, @Prtksxna! Can you provide an explanation of the sub-text? When/how do you propose that it is displayed? I have also started writing a basic ticket here: T234537

IIRC this is a standard OOUI element, a help text, that is being shown inline.