One thing to consider is whether your users are currently blind to that second column or not. Maybe it has been there for a long time and has become a learned behavior to check. Try to get some data on this first.
It seems like the second column wouldn't necessarily violate the F pattern since it's well within the top of the page / top of the F. Furthermore, ...
Why is everything rejected by default? No error has been made. The default should be "not approved" which has no visual cue and a approved state in green.
Also there are 2 journey the one from the "user" and the "approver". The first one's job is to fill out the form, so he only sees the form and if it has been approved (e.g. a ...
Thanks for the question.
The first image showing the list of 3 question is pretty straight forward and well structured. I would suggest to keep it.
When you are in edit mode to it the current solustions seems fair enough. Good to have avoided solutions like pop ups for edit mode.
Understanding the behavior of your user, since you have placed an explicit ...
A modal-based form doesn't seem too unreasonable for a simpler form, however one generally thinks of modals as being smaller in size than the underlying application, so appropriate for a smaller (simpler) form. And one generally thinks of modals as not having scrollbars.
So if the form is large or complex and you require a very large modal, you might as ...
Address form design differs for the country you are designing it for which will influence how you arrange the fields.
In certain countries like the UK and Japan, the postcode will be the first in the list. User will key in postcode and it will autofill other address fields.
Each field has different width. Street address is normally ...
Is an evaluation test type.
The matching test item format provides a way for learners to connect a word, sentence or phrase in one column to a corresponding word, sentence or phrase in a second column. The items in the first column are called premises and the answers in the second column are the responses. The convention is for learners ...
I think the biggest failure in that YouTube video is leaving out the link to [the article the video is based on]. The article details "7 main reasons why placeholders should not be used as replacements for field labels".
There are a number of references used in the body of the article. A couple studies are referred to including this statement:
eye question. (top or bottom)
when passw is dots next to it'd put an 'open eye'icon,
when passw is visible, i'd put an 'eye crossed with a line'icon
//in my mind indicating the action is how it should work (opposed to showing status) thus when open eye is clicked them pw becomes visible ..
what do you think?
Group the cards or charts in a proper manner with callout for each card which can hightlight the top finding. A search on the page is MUST which will show the related cards.
We had a similar requirement for one of the product but we have 120 different metric to show... we categories all the 120 cards into logical group and added a NLP driven search which ...
Interview the executives/stakeholders to understand:
When and how are they using this information?
What do they need to know quickly?
What is less important but still might need to be accessed?
Once you have that information, categorize and cluster the important fields to make them easily accessible (you could use a card sorting exercise for this), and ...
If the content of that section is simply to show all 60 forms, I don't see any inconvenience in listing them all on the page.
This is an example of an online radio DI.FM with 96 different channels including name, current song, author, picture and a play button. The biggest job will be creating each form thumbnail.
For me Auto-save works. This is my scenario and my reasons for implementing it.
Our app has long form with lots of data input, some of that free text comments.
We have more than 100 users with different quality of connection
We have lots of validation rules that depend on multiple fields
When the form is complete and valid it goes to next step ...
The first example you show is probably ok (it is hard to tell with a static image as we can't test contrast easily).
The second example is almost certainly not in accordance with WCAG.
The third example is probably not ok either, but yet again hard to tell "at a glance".
There is a guideline that inputs and controls should have a contrast ratio of ...
Here is a previous post about it with some more points of consideration - Is it a "Natural language" form a good practice?
Can be very hard to deal with the lot of culture and languages.
Harder to design help and error message
It's hard to represent optional inputs, because it leads to empty sentences
Can be hard to parse fast by the user
Not good ...
Natural language forms are much suited in short queries. Like i would like to book a ticket to "Choose Destination" on "Choose Date". These are much intuitive and direct. You can check out Luke's post on mad-libs form to learn more. But when it comes to long forms, it can increase the load on the user.
Standard forms are lot easier when ...