29

The problem at hand does not seem to be a question of correct asterisk marking rules, or a literal interpretation of metaphor behind the radio button control. Rather, the conflict from your description appears to be this: While the two radio button selection instances are marked as required, the requirement is already fulfilled by pre-populated selection. ...


5

You should only mark the field as required if the user must inform something in that field. In your example, since the user is not required to change the value of the fields, you don't need to mark them.


3

Be Consistent The problem with rounding is ambiguity. You've identified this problem with your example of non-matching with filters. To solve this problem, you could always round your numbers in the same direction and indicate that to the user. For example, always round down (i.e., floor) and display 999,999,997 bits/s as "Throughput greater than 0.99 ...


2

I'd talk to your users to find out how they're used to seeing large currency totals. I think it's probably fine to truncate them, as long as the values you display are consistent, so that users can quickly and easily compare different totals. My first thought would be to include a setting or switch that allows the user to choose how they want the totals to ...


2

There is a potential problem with interpreting the requirements from the user's point of view when you make a pre-selection or default choice in a mandatory field. If none of the choices are suitable to the user and the field is mandatory then you have not allowed the user to indicate that this is the case. Normal practice would be to make mandatory only ...


1

To be clear, concise, and avoid ambiguity in documentation provides assurance and consumers of the documentation. Certainly with technical documentation, the author should strive to avoid ambiguity. I would go further and refer to a forward-slash (/) and other punctuation (e.g. full-stop (.), exclamation mark (!), etc.) containing the character between ...


1

USD (12.99) I’ve never seen the currency code inside parentheses. Outside the parentheses is more practical because it allows you to separate the currency from the value. Tables usually have a column for currency and a column for value, so the currency codes align vertically. If the table supports sorting, resizing, rearranging or hiding columns, two ...


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