Skip to main content

Is there a problem with hiding "forgot password" until it's needed? [Resolved]

Tbh I don't really see any use for the "forgot password" button/link, unless the user put in a wrong password before. In my current project we need as much space as possible and I was thinking about showing it only when needed. My colleague talked about "Accessibility"-reasons why it is not possible, but also couldn't give me a real argument.

What is your take on it?


Question Credit: hans wrust
Question Reference
Asked March 25, 2019
Posted Under: UI UX
90 views
2 Answers

Let me try to paint a picture to explain why your comment below is a huge oversight.

Tbh I don't really see any use for the "forgot password" button/link, unless the user put in a wrong password before.

Imagine a scenario where the users come to your application after a while and they don't remember the password. It means, they already know that an account exists but they haven't used it in a long time so they have definitely forgotten the password.

In this scenario, the first thing they'd do is ... ?

They will look for a password recovery option which is something in the lines of a "Forgot Password" option.

In such a condition, the user hasn't put in a wrong password yet, but they need that option

Your colleague is absolutely right about accessibility. Hiding critical actions and information selectively is a very bad practice.


credit: Shreyas Tripathy
Answered March 25, 2019

It's a very bad idea to not show the link. You should always give the user the option, even if they are likely to try a few passwords first.

How about an example - what if you have a password manager, and your credentials for this site is somehow lost/missing from your password manager?

You have no idea what the password is, as it will likely be some random combination of letters, numbers, characters, etc., and therefore will want to reset it straight away.


credit: user2397282
Answered March 25, 2019
Your Answer
D:\Adnan\Candoerz\CandoProject\vQA