Thanks for all the inputs.
Let’s try to summarize.
- We have a general agreement that basic actions should not be colored.
- We also have a general agreement that there is a risk of color inconsistency (e.g., two distinct actions using the same color)
- I would even add that most actions should not be colored (i.e., only outstanding actions should have colors, for a definition of “outstanding to be defined”).
- we did not get any complaints regarding the colors missing when migrating from LT to LD (spanning at least a full LTS cycle).
- we don’t have a clear agreement on a general rule to decide which actions must be colored
-
@mflorea argues for making delete action colored even when there are several steps before the actual deletion, while @vmassol and I argue the opposite. There is also no agreement for the lock/unlock colors.
-
@surli argues for using colors to illustrate the most common actions, which is a quite different axis
-
@amilica argues that colors might hurt readability by forcing bring the eye to secondary elements (note: the “Colour on icon (the acceptable version)” is the one proposed in the discussion)
So in summary, I think we have two options:
Option 1: No colors
The fact that nobody complained about missing colors could be interpreted as a sign that colors are not important. But, that’s also not a proof that having colors wouldn’t improve the UX of actions.
Option 2: A few colors
In this case we need to agree on a rule. Note that based on my current search, we will be able to define guidelines, but it’s likely that we define a rule with no ambiguity (i.e., it’s likely we’ll need to debate again for some actions in the future).
Closed set of colors:
- warning: to be used for dangerous actions with a possibility of revert (e.g., locking a user)
- success: to be used for the action reverting a warning action
- danger: to be used for dangerous actions with no possibility of revert
Definition of dangerous: any action that is leading to the least one user losing access to resources. Either by disappearance of the resource (i.e., delete), or by a user not being allowed to access the resource anymore (e.g., rights change, user locking…)
Option 2.1: Colors based on the final outcome of performing the action
In this case, an action would get a color based on the final outcome of performing the action. For instance, if clicking on the delete action leads to a new form before actually removing the entity, the action would be colored nonetheless.
Option 2.2: Colors based on the direct outcome of performing the action
In this case, an action would get a color based on the direct outcome of performing the action. For instance, if clicking on the delete action leads to a new form before actually removing the entity, the action would be not be colored as that click itself is not dangerous, only finalizing the form is.
Conclusion
I’m +1 for option 1 as we did not identify a strong usability pain related to LD actions.
I’m +0 for option 2.(1/2) with the current rules as I fear the complexity of the rules outweigh the potential usability benefits.