eaon
commented
2 years ago Because the design changes were just merged, we now have an (optional) "declarative" for flash messages as proposed in this issue. It looks better and feels friendlier but changing the language is a crucial part to making good use of it.
We have 3 categories of flash messages:
- :information_source: : Notification (light yellow background, blue/white information icon, black declarative)
- :x: Error (light red background, red exclamation point icon, red declarative)
- :white_check_mark: Success (light green background, green check icon, green declarative)
Below is the entire list of flash messages possible in the current source interface and the rough context in which they happen (if it isn't self-evident). I hope this makes it easier for us to discuss and propose different options.
(Legend: [Type] Declarative - Message (more context in italic))
Session / account related
- :information_source:
None- You were redirected because you are already logged in. If you want to create a new account, you should log out first. - :information_source:
None- You are already logged in. Please verify your codename as it may differ from the one displayed on the previous page. - :x:
None- There was a temporary problem creating your account. Please try again. - :x:
None- Your connection is not anonymous right now! (Tor2web warning page) - :x: Important - You were logged out due to inactivity. Click the
{broom icon}New Identity button in your Tor Browser's toolbar before moving on. This will clear your Tor Browser activity data on this device. (Index page)
Login form validation
- :x:
None- This field is required. - :x:
None- Field must between 1 and {} characters long. - :x:
None- Invalid input. (if it contains characters other than A-Z, a-z, and 0-9)
Submission form bad input
- :x:
None- Message text too long. - :x:
None- Message text too long. Large blocks of text must be uploaded as a file, not copied and pasted. - :x:
None- You must enter a message or choose a file to submit. - :x:
None- You must enter a message. (document upload not allowed) - :x:
None- Your first message must be at least {} characters long. (message has minimum length set) - :x:
None- Please do not submit your codename! Keep your codename secret, and use it to log in later to "check for replies.
Successful submissions
- :white_check_mark: Success! - Thank you for sending this information to us. Please check back later for replies.
- :white_check_mark: Success! - Thanks! We received your message.
- :white_check_mark: Success! - Thanks! We received your document.
- :white_check_mark: Success! - Thanks! We received your message and document.
Reply deletion
- :white_check_mark: Success! - Reply deleted
- :white_check_mark: Success! - All replies have been deleted
Failed login
- :x:
None- Sorry, that is not a recognized codename.
Problem
When a Source submits the page without any selected files or entered message text, they get the below as an error message. The text itself reads in both a robotic and a policing tone.
#acabAlso, in the soon-to-implement Inverted Flow design direction, all error/success messaging must begin with a declarative statement to follow the new design—which is also a generalized best-practice. The declarative should tell the user What just happened (eg, what the error is).
Solution
Tell the user what "the problem" is, first. Don't trigger them to first think "What'd I do?" Then instruct them how to rectify, as briefly as possible. "Please" is always a bad word to begin any messaging with, yet is also always good to include in messaging when it doesn't bloat the sentences. Because the user had just hit the "Submit" button and is receiving this message in response to that, it feels safe to leave "...before you hit "Submit" (or "Send," as I'm experimenting with in the below Figma) as an implied statement, in the interest of brevity.
User Stories
I am a whistleblower, and am anxious in my process submitting a tip to New York World that could ruin my career. I had butterfingers and hit "Submit" before selecting my file to upload. When I get an error in return, it would be great if that error could not further stoke my anxiety by sounding bossy or robotic, with instructing me how to rectify the problem.