User tests: Successful: Unsuccessful:
This PR rearranges the Joomla login screen for improved clarity and user experience. Previously, the login button was positioned below the alternate login options, which caused confusion for users. This change groups the "Username" and "Password" fields together, followed by the login button, and clearly separates them from the alternate login options.
The new layout includes headlines such as "Login with username and password" and an "OR" separator before the alternate login methods. This approach is consistent with login patterns observed in other services and aligns with established usability practices, ensuring users have a clear and intuitive path when logging in.
Sorry the screenshots are German but "Oder" means or and you see the Login options grouped:
Reasons for Change
Enhanced Usability: By grouping the username and password fields with the login button, users can more easily identify and complete the standard login process without distraction.
Clarity: The addition of a separator and relevant headlines distinguishes the primary login method from the alternate options, reducing confusion and improving the visual hierarchy.
Consistency with Modern Standards: Following login patterns used by popular services provides users with a familiar experience, which increases ease of use and reduces cognitive load.
Login with Username and Password:
Navigate to the admin login screen.
Enter valid credentials (username and password) and click the login button.
Verify that login is successful and that the grouping of the fields appears correctly.
Alternative Login Methods:
Enable Passkey Login if not Enabled
On the login screen, click on the available alternate login option.
Ensure the visual separation and headlines make it clear these options are alternatives to the standard login.
Disable Alternate Logins
Ensure the Alternative Login "Group" (Headline "OR" ) is not shown.
Responsive and Accessibility Testing:
Test the new layout on various screen sizes (mobile, tablet, desktop) to ensure it remains clear and functional.
Use a screen reader and keyboard navigation to verify that the new layout is accessible and navigable for users with disabilities.
Language Options
The Language Selection is now at the top, ensure it's still visible
Please select:
Documentation link for docs.joomla.org:
Maybe new Screenshots?
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Language & Strings Modules Repository NPM Change |
Labels |
Added:
Language Change
NPM Resource Changed
PR-5.3-dev
|
@coolcat-creations I've allowed myself to fix the markdown formatting of the description so the headings for actual and expected result are shown as expected in our PR template, and the check boxes for documentation are right.
Thank you for your help, Richard!
I have tested this item 🔴 unsuccessfully on 52e7bff
Didn't see anything about passwordless login on the admin login screen.
That's odd - for me it works. Did you test then with English? Are you sure the "Passkey" Plugin is enabled?
I used the prebuilt package. And I have verified that the plugin for the Passkey (~ passwordless) Login was enabled.
@dautrich And you have once edited your user and registered your passkey like described here? https://docs.joomla.org/WebAuthn_Passwordless_Login
Regarding other language than English for 5.3 so you have multi language: You can download a language pack for 5.1 (or 5.2 soon) and install it with the normal extensions installer.
@richard67 That hasn't been the problem. I'm on localhost and use Laragon. The issue was that I wasn't under https://. Now I've convinced Laragon to allow https:// and I can see the login:
@richard67 Next issue: Tried to download a German language pack from joomla.org, but only see a white screen with the word "Error".
@richard67 Next issue: Tried to download a German language pack from joomla.org, but only see a white screen with the word "Error".
@dautrich Works for me, https://downloads.joomla.org/language-packs/translations-joomla5/downloads/joomla5-german/5-1-4-1 .
Re-Arranging the screen is a great idea. But do we relly need the Text "login with your username and password"? What else could the user expect on a login screen?
@richard67 Has been a hickup on the joomla.org website, obviously.
Things are improving after I installed a German language pack and set German as the default language for frontend, backend, and content:
Two remarks:
For 1.: There is a class "visually-hidden" missing in the legend of the fieldset. If inserted, it looks like this:
Using keyboard navigation (tab key), the language selection is barely unreachable. By default, focus is on the username field, and you have to tab through all available elements (including the browser header), before you finally reach the language selector.
Would be better to give this field the initial focus.
Using keyboard navigation (tab key), the language selection is barely unreachable. By default, focus is on the username field, and you have to tab through all available elements (including the browser header), before you finally reach the language selector. Would be better to give this field the initial focus.
thats no different to the current behaviour
Re-Arranging the screen is a great idea. But do we relly need the Text "login with your username and password"? What else could the user expect on a login screen?
The first option is username and password and the other option has the headline: Or
I think if we say be, we have to say A ? What do you think ?
About the language and the focus - I wonder if we should do a second PR where the language actually changes by changing this dropdown? Because it does not and if you don't understand "Sign in with a pass key" in Chinese the dropdown is not really helpful.
The first option is username and password and the other option has the headline: Or I think if we say be, we have to say A ? What do you think ?
I'm with @chmst : Why should we need "Log in with your username and password", when immediately below there is a form asking for username and password? We could safely omit this line (which eliminates the task to translate the sentence as well).
About the language and the focus - I wonder if we should do a second PR where the language actually changes by changing this dropdown? Because it does not and if you don't understand "Sign in with a pass key" in Chinese the dropdown is not really helpful.
Maybe you're right. If you want to avoid a second PR, you might consider using something like a horizontal ruler instead of the "OR".
But the "OR" is intentional...
Doesn't fit very well to German.
Why ? My screenshots are all German and show exactly this just a HR is not enough
The first option is username and password and the other option has the headline: Or
I think if we say be, we have to say A ? What do you think ?
Correct. But as a user I don't see that these text fragments form one sentence. Suppose you are blind then the screenreander reads the first part of the sentence .. the labels, announces the input field .. then says "or" ...
What, if we start with a complete sentence: "Login with username and password or with a passkey" - then the two clearly separated blocks?
At the moment I have no good testing environment - can someone listen to the screenreader?
Why ? My screenshots are all German and show exactly this just a HR is not enough
My screenshot above is German as well, but it shows "OR", which obviously is not correct in German.
Why ? My screenshots are all German and show exactly this just a HR is not enough
My screenshot above is German as well, but it shows "OR", which obviously is not correct in German.
@dautrich A new language string added by this PR to the English file can't be available in the German translation yet :-) https://github.com/joomla/joomla-cms/pull/44228/files#diff-749c19a3bc27785f12905b9c65fe7600eedf704f0bb0093fbf838b266713fa29R11
@coolcat-creations Have you checked if there isn't already a global language string for "OR" (or "Or" or "or") which we could use here instead of creating a new string?
@coolcat-creations Have you checked if there isn't already a global language string for "OR" (or "Or" or "or") which we could use here instead of creating a new string?
There isnt and its not a good idea to add one for the reasons stated above by @chmst
@coolcat-creations Have you checked if there isn't already a global language string for "OR" (or "Or" or "or") which we could use here instead of creating a new string?
There isnt and its not a good idea to add one for the reasons stated above by @chmst
I thought maybe someone wants to override it with something else than or, it's not possible when I take the general "OR"
Otherwise all OR will be replaced with "or use one of these methods" 😅
@coolcat-creations I think this could be improved:
this text could be inside the field, as @google did with its login page (and many other services):
That actually not so good UX if in the moment you click in the Field the label disappears
@coolcat-creations also I think the or
could be between the two lines (not above the lines) as done by Amazon and in your examples above:
That actually not so good UX if in the moment you click in the Field the label disappears
this is how it works, it's very convenient, you can check it by opening a new tab in private mode:
https://accounts.google.com/ServiceLogin
That actually not so good UX if in the moment you click in the Field the label disappears
this is how it works, it's very convenient, you can check it by opening a new tab in private mode:
Yes but changing all Inputs/ Labels are not scope of this PR, if I do it here I would need to do it everywhere.
Yes but changing all Inputs/ Labels are not scope of this PR, if I do it here I would need to do it everywhere.
there's still a lot of time until version 5.3
, I think it's worth it to make the login
form better.
When you work on new login form, please make sure, that it is accessible for all. WCAG 2.2
Yes but changing all Inputs/ Labels are not scope of this PR, if I do it here I would need to do it everywhere.
there's still a lot of time until version
5.3
, I think it's worth it to make thelogin
form better.
Yes but changing Input Fields in Joomla is a bigger scope, it can't be part of this PR
When you work on new login form, please make sure, that it is accessible for all. WCAG 2.2
Was this directed to me ?
It was for @universewrld.
@coolcat-creations I agree with you that it is not in scope of this PR. Re-arranging the fields is an improvement and enough.
@dautrich how do you get the screen at #44228 (comment)?
There is always shown the Constant like in your #44228 (comment):
@coolcat-creations thanks for your work, looks very nice.
Please keep language field as it was, after the username and password field.
It is an optional input, it should not be first on the page.
Then I put it at the very end?
Not sure, but can try. We probably could even make it "hiddable" somehow, but that another topic 😃
My concern (currently) that it should not be the first input that User will see 😉
I have tested this item ✅ successfully on 52e7bff
I tested with different viewport sizes (desktop, tablet, smartphone) and using keyboard. No further issues.
@coolcat-creations I've allowed myself to fix the markdown formatting of the description so the headings for actual and expected result are shown as expected in our PR template, and the check boxes for documentation are right.