“In the age-old debate between beauty and function, parallax scrolling wins the beauty pageant, but fails miserably in terms of function.”
Parallax Scrolling: Attention Getter or Headache? by Jacqueline Kyo Thomas
Don’t use an overlay unless you have a clear, compelling case for why this content should not be presented within a regular page. Good reasons for using an overlay could include:
- The user is about to take an action that has serious consequences and is difficult to reverse.
- It’s essential to collect a small amount of information before letting users proceed to the next step in a process.
- The content in the overlay is urgent, and users are more likely to notice it in an overlay.
Kathryn Whitenton in https://www.nngroup.com/articles/overuse-of-overlays/
The total cognitive load, or amount of mental processing power needed to use your site, affects how easily users find content and complete tasks.
KATHRYN WHITENTON: http://www.nngroup.com/articles/minimize-cognitive-load/
A website’s usability is determined by the following factors:
- Efficiency: the speed that users can complete their tasks
- Effectiveness: the completeness and accuracy with which users achieve their goals
- Engagement: how satisfied the user is with their experience
- Visibility of system status The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
- Match between system and the real world The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
- User control and freedom Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
- Consistency and standards Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
- Error prevention
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
- Recognition rather than recall Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
- Flexibility and efficiency of use Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
- Aesthetic and minimalist design Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
- Help users recognize, diagnose, and recover from errors Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
- Help and documentation Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.
It doesn’t matter how many times I have to click, as long as each click is a mindless, unambiguous choice.
Steve Krug: Don’t make me think