In T377399#10259713, @Sgs wrote:

In T377399#10238191, @Amire80 wrote:

The value label is already separated from the label by color, font size, and font weight, but it's not perfect. I'm not a real designer, but I could think of some naïve ideas to improve it further:

• Putting the label above the value. It makes sense to me and to how I am accustomed to seeing dashboards and forms, but maybe it makes more sense in some cultures to put them below. (I think that putting the label above is good for forms and dashboards, and below is good for captions of art and photographs, but again, maybe this is just the way to which I'm accustomed.)
• If it's above, then adding a colon, although it must be customizable by language (some languages put a space before it, some languages don't use it at all, etc.)
• Making sure that it works well for blind and color-blind people.

These seem on-point suggestions, before turning them into requirements, let's loop in @RHo who was the original designer and has experience with UIs across languages. What do you think about the label flip and other suggestions?

In T377590#10259253, @Jdlrobson wrote:

In T377590#10258766, @ovasileva wrote:

We would need events for:

• Log-in
• Exit session

This is not quite right. The issue isnt about adding events for clicks it is about distinguishing temporary accounts from logged in accounts.

The elements are tracked but events will appear with isAnon=false. While this allows us to identify the log in link (as no login link is shown to logged in users) it doesnt alllow us to distinguish "exit session" - as an event for that click will look identical to an event for "logout" for a logged in user.

If we only care about that link, yes we should change its event but that would likely need some other changes - they share code for good reasons. I wouldnt recommend this path.

However this goes deeper than those links - all events for temporary users will look like events for a logged in user so if you want information such as click through rate for temporary account or to compare clicks to say the random button (from s logged in vs temporary account user) you cant get that without an additional schema field.

hi @JTweed-WMF and welcome! I believe this would be for someone from Design as part of UX review work for SUL that I believe +@mwilliams is leading on as a new hypothesis for this quarter.

In T375712#10239815, @Jdlrobson wrote:

@RHo the mobile site behaves exactly like desktop (there was a bug) - please make sure when testing the workflow you are looking at https://en.m.wikipedia.beta.wmflabs.org/ which reflects the current state of code.

In T375712#10235069, @Jdlrobson wrote:

(b) advise if a task needs to be added to add the same confirmation dialog on Desktop as is currently in place on Minerva?

I think there is a bug here in the implementation. Just to clarify you are saying that mobile or desktop has the right behaviour/

Desktop currently has the chosen behaviour here - it has code that automatically logs out the user via JavaScrip. This was intentionally added by @Dreamy_Jazz in ab89fff6338 as part of T374519. There is no confirmation step - I just get logged out automatically without confirmation? Is that the desired behaviour?
That code is meant to also apply to mobile, but is broken because #pt-logout a[data-mw="interface"] doesn't . We should have a fix for that in next train.

thanks for the ping @Niharika. Option 1 is easiest (adding the standard "x"), though if possible preference would be that the user doesn't have to click on an explicit "x: to make dismiss everytime, but that it follows the 'toast' type notification messages similar to the post-edit message where the notification times out after 5sec, or if it is part of it (that is not a link) is selected:

In T375712#10227589, @Niharika wrote:

The reason for keeping Login and Create account together is consistency with the logged out user CTAs. I think replacing "Log in" with "End session" is a good idea, though part of the reason for having "Exit session" in the user menu was concerns that having "Exit session" too prominent would make it easier to abuse, which is the reason for the confirmation step -- if Desktop doesn't have this it should be filed as a bug and the confirmation should be there as well.
I would suggest keeping Log in for the initial pilots to monitor how many people arrive here and bounce vs actually logging in. If there is a high bounce rate then we can remove the "Log in" button from the banner as a first step, and potentially elevate "Exit session" to the banner again pending info from piloting as to whether good faith users are having issues knowing how to exit the temp session.

@RHo Can you confirm if the Web team is instrumenting the bounce rate from the Login page and the use of exit session? We are not instrumenting them on our end as of yet.

Hi @kostajh - I'm the main person on design who worked on the unregistered flow so can hope provide some answers:

1. We display prominently "You are using a temporary account". But right next to that, we have a button that says "Create account". I think this ("you are using a temporary account" and "create account" mentioned in the same line) is going to be confusing for people who don't already know the distinction between temporary and named accounts.
Suggestion: Change "Create account" to "Register"
This helps avoid the existing ambiguity of "temporary account"/"account" while also hopefully providing a meaningful entrypoint to users who want a permanent, named account.

It is important to keep the consistency in the CTA for temp account as it is for a non-logged in person, hence keeping Create account and Log in.

screenshot showing the same CTA text for someone not logged in

The reason for this sentence "You are using a temporary account" is to clearly identify this is a different, "not permanent or real" account to one they can create, as from testing (when we added the grey banner text and the new name format, testers were helped in their understanding that temp accounts are different.

Untagging design projects since this seems like a bug where some internal links are being marked as external.

hiya @AAlhazwani-WMF - is this backlogged/in progress/done?

@JFernandez-WMF can you please provide the figma link and google form links?
Also, please consider updating the figma link so that it can be more self guided prototype for people to be able to walk-through on their own mobile device.

Hiya @FNavas-foundation and @AAlhazwani-WMF - would you still like to share something for testing/survey feedback at the UX/Design research booth at WIkimania? If so, please provide a link or materials for me asap.

In T371334#10040168, @JFernandez-WMF wrote:

Thanks @RHo for the question here! I think we just mainly need some loose feedback from participants since we are still on early stages of the project, so they're only 1-2 questions. I've changed the description a little to make it clearer, let me know if that works for you or if you need any extra materials. Thanks so much!

Hi @JFernandez-WMF - how would you like thi testing to be done? Is there going to be a link to userlytics or is the expectation this requires me to run as a guerilla test? If the latter please supply a test protocol and template/doc link for capturing user feedback.

FYI @DTorsani-WMF and @cmadeo - when this work is started, there will be some sepia and black theme colour tokens that DST/Design need to determine how to incorporate (upstreaming directly and/or with some changes to specific colours colours)...

moved out of Research/Design research post-conversation with @leila as this will be more of a content strategist need.

Thanks Leila, sgtm!

thanks @Jdlrobson - the style of the notice being incorrectly a warning was already flagged and being addressed in T366127: Change 'Wikipedia is made by people like you' warning to a Notice message by the Growth team. Adding @JFernandez-WMF @KStoller-WMF in case they want to merge to ensure fix can be done on the same ticket.

OK thanks for confirming! Please add relevant links/tags/details as you see fit.

@AAlhazwani-WMF - is this completed?