I personally think this seems to be done out of habit. Many programs use red, green, and yellow in these situations. Using grey which is often used for disabled items would be useful for the "Not yet started" and "Active but paused" statuses while another color such as blue (or green) could be used to indicate "Active" and "Complete" A) an item is not in progress B) status of that progress. Using 2 distinct colors may be useful because in your case you have 2 distinct scenario. Using a monochromatic scale can help give the user a sense of completeness based on darkness/lightness but when comparing the colors to one another (such as in a grid) it is harder for users to quickly distinguish differences in shade. If the sequence doesn't indicate "good" or "bad" then before using those colors you should consider if red is used in other aspects of the application to indicate danger to the user. If it is then using some universally recognized colors like green or red may be appropriate to add when the sequence is complete. You are trying to make color associations with a sequential status (trying to indicate one thing happens after another) and something to consider is if any step in this process indicates that this status is "good" or "bad" to the user. ![]() This is just food for thought.Ĭontextual consistency helps avoid confusion (such as using red to indicate something is paused but also indicates a system has broken - one situation would be more dire than the other but would be visually equal to the user). ![]() Colors as a status are tricky and very dependent on the context of the web application and their application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |