Table of Contents Revision History Date Version Description Authored/Revised by April 2, 2012 1.0 Initial draft Dan Willis April 4, 2012 2.0 removed, criteria/not criteria tables added Dan Willis April 5, 2012 2.1 More criteria added Dan Willis April 10, 2012 2.2 Fine-tuned criteria and cleaned up sources Dan Willis 11, 2012 3.0 Revised approach after stakeholder review Dan Willis April 17, 2012 3.1 More revisions, graphics and sections Dan Willis 30, 2012 4.0 New section added Dan Willis May 9, 2012 4.1 Edits based on working group feedback Huffaker May 14, 2012 4.2 Incorporated comments from Nancy Wilck Diana Huffaker
13. Does each title of each modal screen identify the task that required the screen to exist? Modal tasks G 14. Does every screen have a clear path to the next step in the activity or, when appropriate, access to other relevant activities? Frequent interactions I 15. Are all icons appropriate to the platform where they appear? (Example: iOS' right-pointing carets would be inappropriate in an Android app) Platform consistency F 16. Are all menu items short enough to avoid truncation when displayed on the application’s target device? Readability n/a 17. Is the application’s screen display name 11 characters or less? Readability n/a Application screens have limited space for the names that appear under icons. Criteria Category Source Response YES NO 18. Is all text large enough to be easily read? Readability n/a 19. Is each menu screen clearly separated from its list items? Readability C 20. Is each scroll bar clearly separated from its background image? Readability C 21. Is there high contrast between the color of all text and the color of the background behind it? Readability n/a 22. When a user stops the application (by pressing the device’s physical “home” button, opening a different application, or using device features like the phone), is the current location saved (the current scroll position, for example)? Saving data G 23. When sound is called for, can the user control volume levels based on their preferences? Sound C
24. Are “about” screens and splash screens avoided at application launch? Startup experience G 25. Does the application appropriately use activity indicators and progress views (an activity indicator when it’s essential to reassure the user that a process has not stalled; a progress view when it’s essential to set the user’s expectations for process completion)? System response C 26. Does the application respond immediately when the user activates any navigational device? System response C 27. Is it obvious that each selected item has been selected? System response C 28. Are all tappable areas 44 x 44 points or larger? User input H 29. Is the current input location displayed everywhere a user enters text? User input C 30. Is it possible for the user to enter all data with one hand? User input C 31. Are all options visible for each required task? User tasks I Criteria Category Source Response YES NO 32. Is all terminology used consistently, including online and offline documentation and help instructions? Consistency K 33. Has the application undergone the appropriate level of usability testing? Usability testing n/a
Recommended Rollout phase: Criteria that create a foundation for usability U1: Access – native accessibility features U4: Errors – plain language U8: Functional consistency – screen movements and scrolling U9: Gestures – consistent functionality U11: Modal tasks – safe exit U12: Modal tasks – action sheets U14: Frequent interactions – dead ends U16: Readability – truncated menu items U17: Readability – screen display length U18: Readability – text size U21: Readability – text contrast U22: Saving data – location captured U24: Startup experience – splash screens U26: System response – immediate response U27: System response – obvious selection U28: User input – tappable areas U29: User input – cursor U32: Consistency – terminology Second phase: Criteria that build on the foundation of usability introduced in the first phase U3: Device orientation U5: Frequent interactions – clearly displayed U10: Modal tasks – staying within modal U13: Modal tasks – informative titles U19: Readability – titles clearly separated U20: Readability – scroll bars U23: – volume control U25: System response – indicators U30: User input – one-handed entry U31: User tasks – obvious options Third phase: Criteria that ensure consistency across VHA applications U2: Controls – standards U6: Functional consistency – navigation bar U7: Functional consistency – progress bar U33: Usability testing