The problem is that browser displays a cached page when you click back is purely technical. You can ask your dev to disable caching so clicking "Back" will not load cached page but get fresh version (with empty fields)
But that could be problematic as user would not get any indication.
I think that is the main problem here. Redirecting the user would be fine, most users have come to expect it now that software validates their input. It's only a problem if they don't understand what's happening.
As the very popular NN Group 10 Usability Heuristics for User Interface Design ...
Better to reveal all missing info at once. This makes it explicit right away about exactly what's missing.
Assuming you have best practices in place to avoid users skipping the required fields in the first place, the user is now in a state where they can make no progress.
Highlighting all required (but empty) fields at once gives them the scope of what they ...
I hide the honeypot field using some positioning/clipping as I suspect display: none is a clue to a spambot to avoid the field. At the least, it’s a possibility.
However, I appreciate it seems a lot for a bot to parse the HTML class and find the property value pair in the CSS itself. I wonder if class names such as hide alert the spammer? That would be a lot ...
It might be a better argument to have with your product manager about whether you should be marking fields as required at all.
The reason I say this is that asking for optional information should be avoided where possible as it slows up the user when completing a form, even if they don't enter an optional field it makes them think about whether they should ...
According to Nielsen Norman, there's a slight benefit to putting it before:
Should the asterisk precede or follow the field label? That is
unlikely to make a practical difference, but one reason to put it just
before the field description is to help the eyes easily locate which
fields are required by scanning just the left-most character of the
Typically I would agree it makes more sense grammatically to be at the end of the text, especially if you have a footnote that denotes the meaning of the asterisk. For example:
However, I would not be so adamant to say that it must be done this way. There are benefits to having the asterisk at the start. Such as that it will be the first thing the user sees ...
The important thing here is to consider the use cases.
There are a few things to consider, and I think you've hit on probably the main one, eye tracking, and in your example you've given an example with two fields.
The reason I mention this is that if you have 1000 fields and only one of them is a number, you should consider how important it is to draw ...
Option A is the default horizontal alignment in Google Sheets too, but I also see the eye tracking problem that you mention and I think it affects both web and desktop applications.
Maybe this alignment is already familiar to some users for cells without label in spreadsheets, but for fields with a label I prefer option B because it allows the user to read ...
initial answerPaul, the auto-fill is exactly the reason behind this ordering logic. The address services (available with APIs developers can use) allow the system to do the following:
auto fill other fields in the address (to improve efficiency of user input)
to validate with the user that the input was correct - to improve the tolerance
This is a ...
Use a scrolling display table with 5±1 rows visible at a time, each showing a full week and being selectable. The first column should display the ordinal week number, the following seven columns would be for the days of the week and show the day of the month in each cell. You also need to show the year and month of the majority of the rows.
In my experience, well, it depends.
in some cases the process may be improved significantly by using country + zip first.
Zip codes are useful for actually extracting most of the address fields, if you dev team has access to publicly available services.
This is even more powerful in some cases like the UK where Zip can sometimes even distinguish up to a ...
If you decouple the problem to prime factors it's not that difficult.
There are 2 roles:
In simplify according to Event Storming - the 2 basis actions are:
Request by Requester (some CTA, button or alternative)
Approved by Approver (some CTA, button or alternative)
An entity in the database with an additional boolean column isApproved (...
The rule that radio buttons require a single selection applies to a list of radio buttons, not the whole form. Your form has multiple lists (some as short as two items), so each list is a group of mutually exclusive radio buttons. Within each group of radio buttons, the user can only choose one. When the form is completed, multiple radio buttons are selected ...
If it is possible I would reduce the number of optional fields from 5 to 3, for example, but I know that is not always an option.
A possible solution for the 11 fields scenario would be to group the 5 optional fields under an expandable menu under the required fields and label this section as OPTIONAL, ADVANCED or something like that. This solution allows ...
A dropdown menu limited to the actual month would be a good solution if the users are going to select weeks around the actual date, like for example in a flight/hotel booking website.
But if the users need more flexibility maybe adding some input fields could be helpful:
You could consider using a calendar picker in which the only selection a user can make is an entire week (as opposed to a typical calendar picker where users can select specific days). This is a pretty standard web convention for dealing with user-input dates. Depending on your use case, it could also be helpful to label the weeks with numbers, and allow ...