New answers tagged disable
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 ...
This layout could be seen to be confusing to your users. By using multiple choices you imply that they can be changed by interacting with them, when they cannot. So if you are not offering the functionality to change the options then I would avoid this design.
I think it depends on if this is the primary purpose of the app or not (or at least the page). If it is, then in my opinion it SHOULD be obtrusive and I vote for option #2. Regarding #3, I don't see allowing user to enter text as a "pro". You're allowing a user to think they're doing something only to present them with an error afterwards. It's wasting ...
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...
Probably not the best, but some options to improve the situation: Background and font color. Not-allowed pointer on hover. (CSS=> cursor: not-allowed;)
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; ...
Top 50 recent answers are included