Table 1 Usability evaluation checklist from the novice and expert developers’ evaluation with questions that both novel and experienced developers estimated as highly relevant depicted by criteria scores of ‘4’ or ‘5’
From: A usability design checklist for Mobile electronic data capturing forms: the validation process
No. | Usability evaluation question | Agreed % |
|---|---|---|
1. | Is it possible to get a summary of all the data the user has entered at any given time? | 94 |
2. | Are there visual differences between interaction objects (e.g., buttons) and information objects (e.g. labels, images) | 94 |
3. | Are the data entry fields which are mandatory or required clearly marked? | 94 |
4. | Does the tool make use of device information like data and time, geo-location, device number, etc. as input data? | 94 |
5. | Do data entry screens and dialog boxes indicate when fields are optional? | 93 |
6. | Does the tool show error signals and marks on the actual field that has an error and needs to be changed? | 92 |
7. | Is there some form of feedback for every user interaction? | 92 |
8. | Are the buttons in the form mostly or always visible? | 90 |
9. | Is the submit button disabled as soon as it has been clicked during submission of the form? | 90 |
10. | Is the help function visible? | 90 |
11. | Does the tool preserve the user’s work in order to correct errors by just editing their original action instead of having to do everything over again? | 90 |
12. | Can users easily switch between help and their work? | 89 |
13. | Can users move forward and backward between text fields or dialog box options? | 88 |
14. | Is the language used in the form clear, effective and appropriate for the target users? | 89 |
15. | Is navigation consistent across orientations? | 88 |
16. | Does the tool provide the user an alternate method of authentication? | 88 |
17. | Does a back button simply return the form to a previous view without loss of data? | 87 |
18. | For data entry screens with many fields can users save a partially filled form? | 87 |
19. | Are users able to interact with the form by swiping or pinching (zooming in and out) instead of only touching? | 87 |
20. | Is all the information users enter into the data forms validated and users informed if it is not in an acceptable format? | 87 |
21. | Are inactive menu items greyed out or omitted? | 87 |
22. | If pop-up windows are used to display error messages, do they allow the user to see the field in error? | 87 |
23. | Are prompts, cues, and messages placed where the eye is likely to be looking on the screen? | 87 |
24. | Is it possible to automatically save a page in the form when a user scrolls to the next page? | 87 |
25. | Does the system provide an example input for format-specific or complex information? | 87 |
26. | Is the format of a data entry value for similar data types consistent from screen to screen of a given form? | 86 |
27. | Is the user able to know where he or she is during navigation of the form? | 85 |
28. | Can users resume work where they left off after accessing help? | 85 |
29. | Have the forms been designed to recognize specific input types and adjust the input modes accordingly during data entry? | 85 |
30. | Users dislike typing, is information computed for the users where applicable? | 85 |