New answers tagged wording
as far as i understand, even if there are no severe consequences, yellow is not really enough, so I would use one positive and two negative states. Yellow is a poor/decent state, red a complete disaster. depending on the domain, find something like healtyh / sick / deadly injuried fast / slow / motionless fresh / moldy / rotten (english is not my ...
You could try something entirely visual, by displaying one of these bars, along with a question that identifies what is being scored.
Try mediocre, middling, below average, suboptimal, needs work, or go ask on English.SE for more synonyms. You could also use graphics instead of text, which could be emoticons (smile/frown/meh), arrows (up/down/right), thumbs (up/down/nothing), etc. Just make sure you don't only rely on color. That's a major accessibility violation.
The frame of reference should be the user. So when you're bringing data into the app you're currently using, it's Importing. When you move data out of the app you're using, it should be Exporting. If I understand your situation, I'd call it Export since I'm sending data out of the app. Of course, you could change the verbiage for clarity. "View in Excel" ...
I would definitively call it Export. From a user perspective, the website is at a remote place, but who will execute the action of migrating the data is the server that will prepare a package and send it to the user. Since its the server that executes the action, it'll export the data and not import. Using your analogy of a foreign car, if you contact a ...
It looks like the area code mismatch is NOT an error which should halt and prevent the user from saving. I would propose you change the flow a little (see below) Changes: Allow the user save if area code does not match the state. Show a notification (not an error) under field(s) in question. Such approach will not force the user to save twice and ...
Top 50 recent answers are included