1

Example: When opening a menu on a user page, one can encounter the following menu items:

  • Ban
  • Delete
  • Report

Is it better practice if the menu items are as followed:

  • Ban User
  • Delete User
  • Report User

And what if the menu spans multiple contexts?

  • Ban User
  • Delete User
  • Report User
  • Report User Image
0

Clarifying things always seems like a good idea, but we need to balance it with information clatter. Look how is it done here at StackExchange or Facebook:

enter image description hereenter image description here

Google also solves it this way. Why? Because low of proximity works pretty well. People know what they are editing when they clicking it. However if I was designing for users that aren't good with computers then I will check to be sure if they know what will happen if they click it. I guessing they will know what edit in SE is for (but some of them wouldn't know that they need to click '...' to edit a comment in facebook).

So when we need a full label? When we have a bad, clatter UI. If you look on the examples in the internet, the contextual menu is always near only this one thing that it is about. However adding such clarification is crucial for blind users, although I remember there ware ways to add such clarification for screen reader only.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.