we've started a design review (internal google doc) of the current ux, and identified a few recommendations. we shared this with the growth team, and after this internal review we will share this with other stakeholders too.

@kostajh we listed in this google doc a series of recommendations/requirements to kick off the design exploration.. let us know what you think, and leave comments if there is anything else that should be considered as we start exploring designs and copy of this (temp account rate limit) message.. and please feel free share this doc with anyone who might have valuable feedback/input. thank you!

@kostajh we started to explore a few early ideas, and would love your feedback.. feel free to ping/add other folks to this task as needed, thank you!

given that in this specific scenario (when a person with a specific IP hits the temp account rate limit) it will be impossible for them to publish any edit as long as they don't create an account or log in, we suggest to "block" the editing experience with a modal.

we're also suggesting to use a modal to have a stronger separation of concerns between user-relevant information and article-relevant communications (like BLP notices among other things). we'd like to avoid situations like this one below where there are competing messages displayed at the same time.

our suggestion is to check whether the rate limit is hit while we load the editor.. and based on the result display (or not) the modal. we thought of two approaches where we present this modal potentially once (before the publish dialog) or twice (after the editor opens, and before the publish dialog).

show it once

show it twice

we are also exploring a much more concise copy, clearly outlining what people need to to do proceed. it's not necessary to give too much background (technical) information as it doesn't really help people move forward.

Before	After

here are some ideas/alternatives for the "why do i need an account?"explainer too..

we acknowledged that this is a temporary solution, that will probably be affected by design decisions on T407497 (in the near-/mid-term) and on T409236 (in the mid-/long-term).

For the message, I would remove the "Why do I need an account?" subheader and expander/collapser, and say something in active voice. (Also, we don't like to say "anonymous editing", as registering a user account is, if anything, more privacy-protective.)

What do you think about something smaller like:

To prevent spam, we limit editing without an account.
Creating a free account is quick, and lets you edit any time.

In T408011#11368444, @EMill-WMF wrote:

For the message, I would remove the "Why do I need an account?" subheader and expander/collapser, and say something in active voice. (Also, we don't like to say "anonymous editing", as registering a user account, is, if anything, more privacy-protective.)

What do you think about something smaller like:

To prevent spam, we limit editing without an account.
Creating a free account is quick, and lets you edit any time.

sounds good @EMill-WMF.. here are some (styling) explorations compared against the original proposal (with revised copy following your suggestion)

for context... i suggested progressively disclosing information with an accordion because:

• people tend to dismiss dialogs without reading, especially when they see long-ish text
• we want to guide their attention to the most important action (create account or log in)
• once they engage with the brief text, they can learn more by choosing to expand
• the new proposal gets very lengthy in languages like greek or malayalam

Good points on the accordion - I was not thinking at all about other languages. I defer to what you think best. Among the above visual proposals, I like the accordion version, and the rightmost version (the smallest text) the most.