Tag Info

Hot answers tagged

14

Generalising between platforms I would go with the following basic guidelines, they further emphasise a disabled field with a grey background. Normal (with a value) Black text, white background, black border. Normal (with a placeholder) Grey text, white background, black border. Disabled Grey text, slightly lighter grey bg, grey border. E.g.


7

In most cases, forms are made of native elements and the look and feel is therefor (ideally) determined by the operating system. Mac OS has a different way of showing something is disabled if you compare it to windows. Here are two text fields of Windows XP and Mac OS X with native behavior: vs. I would advice you not to change this behavior for several ...


6

Some things I have seen done before in this scenario: Make placeholder text green instead of grey (user input is in black) Placeholder text is in italics (user input is in normal text) Put angle brackets around text, eg. < your name here >. (This one is somewhat "technical", i.e. something a programmer is more likely to understand) I would suggest ...


6

You should not show controls to the user if they can not interact with them. It will cause problems like frustration, doubts and may be even leaving the process altogether. If the user finds a control that he can't interact with, first is going to look for an explanation of why. Once he doesn't find that answer, he may feel that missed a step before, and ...


5

Either way is fine. Of course, replacing the text with "Nothing to Paste" is much more clear and understandable than just disabled "Paste" menu entry, which is good for UX. However it seems to be standard to leave the disabled entry unchanged, like on Windows explorer, you won't find a dynamic disabled paste entry. This way is also friendly for UX because ...


3

From WCAG 2.0, which is generally accepted as a way to be 508-compliant in your product: 1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA) Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; ...


2

There are several reasons that if your facetted search is very open, more like a network of combined selections, that you should leave empty filters visible. Consistency You are better off disabling the filters so the interface retains consistency throughout the interaction. If there are always the same set of filters then the user can learn the interface ...


2

Of your three options, I prefer the second because it adds an upgrade option, empowering the user to solve the search availability issue. Alternatively... Create a button for each concurrent search that your user's current account can perform and replace each one with a confidence animation when its search is running. Something like...


1

It depends on what your user needs to be able to do. For example, the following cases would support responsive disclosure (hiding the options that are not needed based on the earlier selection)... the administrator wants to see what options are available to the normal user a new user isn't sure whether to pick administrator or not and wants to know what ...


1

People who are flicking through navigation like that are expecting to click in the same place all the time. The simple fact is that most users don't look when they are clicking "next" on each page / screen. If you start removing items from your navigation because they don't apply for that particular page, the other navigation links will move relative to ...


1

Disable option tells you that you are not eligible to access this feature because of 1: f permissions 2: or they are dependent on another action & gets invoked after an action. You can keep them disable and give an explanation on hover[not mandatory]


1

I think if the context is easily understood, disabling without hints of why, is fine. Remember Balloon help in MacOS? Apple encouraged us to write balloon help for disabled items way back from 1991 and forward. Microsoft did not. But as said above, tool tips only work if you have the hover event, not for touch. For more complex scenarios, explanation why ...



Only top voted, non community-wiki answers of a minimum length are eligible