The Sign In widget on the Mozilla account page includes confusing strings

[denyshon]

Description

For users who are not signed in, the widget on https://www.mozilla.org/account/ looks somewhat confusing:

• It's called Sign In.
• A string at the bottom says: Already have an account? Sign In.
• The Sign In link from the string mentioned above redirects to https://accounts.firefox.com/, where you can both sign in and sign up (with no special flow for signing in).
• When entering an email not associated with an account into the widget input field, the sign-up workflow is triggered.

To address the above, I suggest renaming the widget (e.g., Sign In or Sign Up) and removing the "Already have an account?" string.

Steps to reproduce

Go to https://www.mozilla.org/account/, not being signed in to your Mozilla account (if you use Firefox, you have to be not signed in on the profile level as well).

Expected result

It is clear that the widget allows you to both sign in and sign up without taking any additional action.

Actual result

The widget tries to create an impression that it allows only one flow, but hasn't decided which one yet.

Environment

Any?

[denyshon]

For reference: Bugzilla bug | original report.

[denyshon]

@stevejalim thank you for directing; I've moved the bug here.

[janbrasna]

Quick note: FxA is currently experimenting with their CTA wording on https://accounts.firefox.com itself, trying a few variants, and, exactly, looking into how users understand the dual-intent of the form, so this is currently being changed on their side too.

I'd advise waiting how they decide to proceed, and use the same terminology as they eventually settle on.

[janbrasna]

The original report:

When you sign in to mozilla.org at say https://www.mozilla.org/eu/account/ or https://www.mozilla.org/en-US/account/, there are two “Sign-in”s. It is weird to have a main input field for the email address and then at the bottom, in small text, the option to sign in if the user already has an account. Except.. you can’t sign in without having an account, as that would be registering/signing up. But no, both are labelled as “Sign In”.

Thus, I don’t understand the inclusion of the second “Sign-in”; it adds unnecessary complexity to the form. I understand this might not be the best place to post this issue, but I couldn’t find a Github repo for Mozilla’s website (most likely it doesn’t exist), so I am writing here.

Right, it sounds like having two sign-in flows, and no sign-up… 🙇

The issue really is… and you need some tribal knowledge for that… that the plaintext link opens the FxA login screen, that has a) more login options, like federated providers; and/or b) allows filling stored credentials from keychains for that host/domain.

So, in general, both an email form for either signup or signin flows using email as the username part, and alternatively a link to the full login screen are both relevant.

Admittedly the heading should cover both "Sign up or Sign in", and the form offer both
"Continue with email"
— or —
see more login options

(There's just some UITour hooked to these buttons to sign folks in to their desktop browser too, so there might be a reason why the form appears that cumbersome, trying to log in right away, instead of just sending folks along…)