| 25 | * Is the user ever expected to do something that is not obvious? (e.g. Are important features only accessible by right-clicking on a menu header, on a text box, or on an unusual GUI element?) |
| 26 | * Are there hints and tips and shortcuts that appear as the user is using the software? |
| 27 | * Should there be instructions in the manual that actually belong as contextual tips shown in the program? |
| 28 | * Is the user at a disadvantage for not knowing certain keyboard shortcuts? A user has the right to know all major and minor keyboard shortcuts and features of an application. |
| 29 | * Is the learning curve (of hints and tips) skewed towards point-and-click users rather than keyboard users? |
| 30 | * Are there any "hidden" or undocumented keyboard shortcuts, that would better be revealed in a "Keyboard Shortcuts" Help-Menu item? A strategy to prevent this "undocumented feature disconnect" is to automatically generate a list of keyboard shortcuts from their definitions in the code. |
| 31 | |
| 32 | }}} |
| 33 | Tasks that affect usability |
| 34 | * Help related tasks (help, tooltip) |
| 35 | * Keyboard related tasks (shortcuts) |
| 36 | * Tasks that will simplify GUI/feature |